## Problem/motivation _**Note that if we at least get the code with one draft example merged in for beta4 that we can add the additional sample context in rc1 since it would be "documentation" in a sense.**_ Follow-up to: - #3586335 - #3586279 A new Context Control Center (CCC) installation is empty. People unfamiliar with CCC terminology and structure cannot easily see how source content, context items, scopes and consumer subscriptions work together. Provide realistic, optional demo data that lets people explore a complete CCC workflow before configuring it for their own organisation. ## Proposed resolution Create demo context items containing 1 to 3 complete examples: 1. **Government:** Based on the GOV.UK guidance for writing with the right tone. 2. **Healthcare:** Based on the NHS service manual content guidance. 3. **Higher education:** Based on the University of Edinburgh editorial style guide. Each example should include: - Sample source content that can be reviewed or rewritten. - One concise context item derived from the relevant guidance. - Appropriate scopes, tags or use cases. - Instructions explaining how to enable the example and run it. - A description of the expected changes, without relying on deterministic AI output. - Source, license, and attribution information. Ideally, the examples should demonstrate different organisational contexts while using the same underlying CCC concepts. ## Implementation Provide the examples through an optional recipe or demo submodule rather than installing them automatically with `ai_context`. The implementation should: - Keep sample context items disabled or unpublished until explicitly enabled. - Clearly prefix or label every sample entity so it cannot be confused with production configuration. - Avoid creating active subscriptions on existing consumers. - Provide a documented way to remove the sample data. - Package the required example data locally rather than fetching external content during installation. - Keep context items concise enough to work with CCC’s default token allowance. - Use existing CCC entity types and configuration rather than creating a parallel demonstration system. ## Demo examples ### 1. Government content Use or adapt the GOV.UK guidance: https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/right-tone/ Include: - A short public-service content example. - Tone and voice guidance. - Plain-English and reader-focused instructions. - A consumer subscription showing when the government context applies. ### 2. Healthcare content Use or adapt the NHS service manual guidance: https://service-manual.nhs.uk/content Include: - A short patient-facing service or health-information example. - Clear, accessible and reassuring writing guidance. - Instructions covering terminology, readability and avoiding unsupported claims. - A consumer subscription showing when the healthcare context applies. ### 3. Higher-education content Use or adapt the University of Edinburgh editorial style guide: https://information-services.ed.ac.uk/editorial-style-guide Include: - A short student-facing course, service or campus-information example. - Editorial style, terminology and formatting guidance. - A consumer subscription showing when the university context applies. ## Licensing and attribution Open access does not necessarily grant permission to redistribute or adapt content. Before adding any material: - Confirm that its license permits redistribution and adaptation in a GPL-compatible Drupal project. - Record the source URL, license, and required attribution. - Prefer concise adaptations over copying complete guides. - Replace any source that cannot be redistributed with an original example informed by general principles. ## Documentation Document: 1. How to install the samples (if not auto-installed). 2. What each sample contains. 3. How to duplicate and adapt a sample. 4. How to disable and remove all sample data. 5. Which parts are illustrative and should not be used unchanged in production. ## Acceptance criteria - Government, (consider) healthcare and (consider) higher-education examples are provided. - Each sample includes a source context item with scope settings. - No sample context affects production behavior unless explicitly enabled. - Sample entities are clearly identified and unpublished by default. - Every included sample has verified redistribution rights and attribution. - Installation and removal are documented. - Automated coverage verifies that the samples entities install with the expected status, disclaimers, and licensing info. - The examples can be duplicated and edited without modifying the originals. ## Out of scope - A general-purpose library or marketplace for contributed context items. - Automatically importing arbitrary external style guides. - The proposed fill-in-the-blanks context-item authoring experience. See #3586340+s. # Original summary Follow up to: - #3586335+s - #3586279+s The CCC may be tricky for new users to understand as they may not be familiar with the naming conventions and structure. Demo content could improve understanding of how everything fits together. Action: create some demo content and use pre-existing context items openly available to load into CCC to show how it works. Make this content available to users who want a demo of the CCC before they make it work for them. - Public sector use case - using Gov.uk and NHS context items available on open access: - https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/right-tone/ - https://service-manual.nhs.uk/content - University use case - using an open-access university style guide: https://information-services.ed.ac.uk/editorial-style-guide