>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3582889. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Blocked by: </strong>[#XXXXXX] (New issues on new lines)<br> <strong>Additional Collaborators: </strong> @username1, @username2<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We want to be able to leverage context from external sites or subsections of sites that may have hundreds of pages. We don't want to just copy that context into CCC.</p> <p>This issue is to discuss architectural approaches before starting any type of implementation.</p> <p>Note that this feature would be part of 1.1 (or later) and not 1.0, but it would be good to get this done before Rotterdam.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>I have worked with cursor/opus to discuss this in the context of the CCC roadmap and making sure this is an approach that is scalable and extensible.</p> <p><em>I have not refined this plan, but wanted to get the ball rolling here anyway.</em></p> <p><a href="https://www.drupal.org/files/issues/2026-04-02/external_context_sources_architecture_plan.pdf">Plan (PDF)</a><br> <a href="https://www.drupal.org/files/issues/2026-04-02/external_context_sources_architecture_2f22a3e5.plan_.md">Plan (MD)</a></p> <p><em>Disclosure: Given that I'm a part owner of QuantCDN and we have a crawler, static site hosting, VDB, etc, I plan to create a reference integration with Quant once we sort out the architecture. This would allow me to easily test and tweak things on both sides as needed. Of course, I would make sure that there is no vendor lock in or any Quant dependency in CCC. I'm disclosing this because Quant is mentioned in the plan above. I find that it's easier to have a concrete reference integration implementation in mind when building out such features. If anyone has concerns about this approach, I welcome you to DM me to discuss.</em></p> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <p>April 2026</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Discuss and refine</li> <li>Settle on a robust architecture</li> <li>Figure out the timeline for building this</li> <li>Create follow-up issue for implementation</li> </ul> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[x] AI Assisted Issue<br> This issue was generated with AI assistance, but was reviewed and refined by the creator.</p> <p>[ ] AI Assisted Code<br> This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p> <p>[ ] AI Generated Code<br> This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p> <p>[ ] Vibe Coded<br> This code was generated by an AI and has only been functionally tested.</p>