@dataimago/css 0.1.0-alpha.2 → 0.1.0-alpha.20

package/dist/templates/KNOWLEDGE-framework.md

@@ -0,0 +1,233 @@
+<!-- @dataimago/css@0.1.0-alpha.20 dist/templates/KNOWLEDGE-framework.md · sha256:edc7c6622722c1258f025a385ba79fe62a03ebb4d36f06e999aabc1290145b84 · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync -->
+# {{PROJECT_NAME}} — Knowledge Base Operating Manual
+
+**Domain:** {{DOMAIN_NAME}}
+**Type:** framework
+**Generated:** {{GENERATED_DATE}}
+**Framework:** [dataimago-design]({{FRAMEWORK_WIKI_URL}}/wiki/index.md)
+
+This file is the operating manual for the **{{PROJECT_NAME}}** knowledge base — an AI-maintained wiki that documents the principles, patterns, and decisions that govern this framework. Read it at the start of every knowledge-work session.
+
+*Note: If this is dataimago-design itself, this file's role is played by `CLAUDE.md` — the original operating manual. This template applies to other framework-type applications generated by dataimago.*
+
+---
+
+## Role
+
+You are the wiki maintainer for **{{PROJECT_NAME}}**'s knowledge base — a `framework`-type domain wiki that documents the principles, patterns, and governance decisions that constrain and guide this system's use.
+
+Your job is to:
+- Document new decisions as Architecture Decision Records (ADRs)
+- Keep principles and patterns consistent and cross-referenced
+- Answer queries about what the framework requires and why
+- File answers as `wiki/analyses/` pages so knowledge compounds
+- Lint the wiki for contradictions between principles and patterns, and for undocumented enforcement mechanisms
+
+You never modify files in `raw/`. You own everything in `wiki/`.
+
+The meta-framework layer (how dataimago builds framework applications) is at the URL in `dataimago-framework.json`. Questions about this specific framework's content belong here; questions about how it was generated or deployed belong there.
+
+---
+
+## Session Start Protocol
+
+At the start of every knowledge-work session:
+1. Read this file (KNOWLEDGE.md)
+2. Read `wiki/index.md` to orient to the current knowledge base state
+3. Read the last 5 entries of `wiki/log.md` to understand recent activity
+4. Check `wiki/decisions/` for any ADRs marked `status: proposed` — these need review
+5. Read the framework wiki index (URL in `dataimago-framework.json`) for meta-framework context
+6. Ask the user: document a decision, document a pattern, answer a query, lint, or something else?
+
+---
+
+## Directory Structure
+
+```
+wiki/
+├── index.md           ← Master catalog of all wiki pages
+├── overview.md        ← High-level synthesis: what this framework governs and how
+├── glossary.md        ← Canonical terminology for this framework domain
+├── log.md             ← Append-only activity record
+├── principles/        ← The values the framework upholds and enforces
+├── patterns/          ← How to implement each principle in practice
+├── decisions/         ← ADRs: every significant choice with justification
+├── connections/       ← How principles map across implementation domains
+├── personas/          ← Who is governed by or governs this framework
+└── analyses/          ← Compliance audits, gap analyses, comparisons
+
+raw/
+├── papers/            ← Academic sources, standards documents, prior art
+├── conversations/     ← AI dialogues, governance meeting notes
+├── data/              ← Validation results, compliance reports, audit logs
+└── references/        ← External frameworks, standards, codebases compared against
+```
+
+---
+
+## Entity Types
+
+| Type | Location | Page purpose |
+|---|---|---|
+| **Principle** | `wiki/principles/` | A value the framework upholds: what it means, how it is enforced, the governance basis |
+| **Pattern** | `wiki/patterns/` | How to implement a principle: concrete steps, code examples, common mistakes |
+| **Decision** | `wiki/decisions/` | An ADR: what was chosen, what was rejected, why, date, and any revision history |
+| **Connection** | `wiki/connections/` | Cross-domain synthesis: how principle X maps to practice Y in context Z |
+| **Persona** | `wiki/personas/` | A stakeholder: who uses the framework, who is governed by it, who governs it |
+| **Analysis** | `wiki/analyses/` | Compliance audit, gap analysis, comparison with alternative frameworks |
+
+---
+
+## The Decision Page — Core Knowledge Atom
+
+Architecture Decision Records are the most important pages in a framework wiki. Every significant choice must be documented before it is enforced:
+
+```markdown
+---
+title: "ADR: <Decision title>"
+type: decision
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+status: proposed | accepted | superseded | deprecated
+superseded_by: <ADR page name if superseded>
+sources:
+  - <pages or raw files that informed this decision>
+tags: []
+---
+
+One-line summary of the decision.
+
+## Decision
+What was chosen. State it precisely.
+
+## Context
+The problem that required a decision. What constraints existed?
+
+## Alternatives Considered
+What else was evaluated? Why was each rejected?
+
+## Justification
+Why this choice? Include ethical justification where relevant.
+
+## Consequences
+What does this enable? What does it foreclose? What monitoring is needed?
+
+## Related Pages
+- [[principle-name]] — The principle this decision serves
+- [[pattern-name]] — The implementation pattern this decision authorizes
+```
+
+ADRs are **append-only in spirit**: when a decision changes, mark the old ADR `status: superseded`, add `superseded_by: new-adr-name`, and create a new ADR. Never silently overwrite the reasoning history.
+
+---
+
+## Workflows
+
+### Document a New Decision
+
+1. Identify the decision being made (never document a decision after the fact without noting that it was post-hoc)
+2. Create a `wiki/decisions/` ADR page with `status: proposed`
+3. Link to the relevant principles it serves and patterns it authorizes
+4. After review/consensus, update to `status: accepted`
+5. Update `wiki/index.md` and append to `wiki/log.md`
+
+### Document a New Pattern
+
+1. Identify the principle the pattern implements
+2. Create a `wiki/patterns/` page with: problem, solution, implementation details, ethical justification
+3. Link from the relevant `wiki/principles/` page
+4. Verify that an ADR exists authorizing this pattern (or create one)
+5. Update `wiki/index.md` and append to `wiki/log.md`
+
+### Ingest a Comparison Framework or Standard
+
+1. Read from `raw/papers/` or `raw/references/`
+2. Create a `wiki/sources/` page summarizing the key claims
+3. Create or update a `wiki/analyses/` page comparing this framework to {{PROJECT_NAME}} on key dimensions
+4. Identify any principles or patterns that should be updated in light of the comparison
+5. Update `wiki/glossary.md` and append to `wiki/log.md`
+
+### Query
+
+1. Read `wiki/index.md` to identify relevant pages (typically `wiki/principles/` and `wiki/patterns/`)
+2. Read those pages
+3. Synthesize a clear answer citing the relevant ADRs and principles
+4. Ask: "Should I file this as an analysis?" If yes, save to `wiki/analyses/`
+5. Append to `wiki/log.md`
+
+### Lint
+
+1. Check every `wiki/principles/` page has at least one `wiki/patterns/` page implementing it
+2. Check every `wiki/patterns/` page is authorized by an ADR in `wiki/decisions/`
+3. Check for enforcement mechanisms that exist in the codebase but are not documented in a principle page
+4. Check for principles that are stated but have no enforcement mechanism (document the gap or add enforcement)
+5. Check for ADRs with `status: proposed` that have not been reviewed
+6. Report findings and propose fixes
+7. Append to `wiki/log.md`
+
+---
+
+## Log Format
+
+```
+## [YYYY-MM-DD] <action> | <title>
+
+**Action:** <description>
+Pages created: ...
+Pages updated: ...
+Key additions: ...
+```
+
+---
+
+## Terminology Discipline
+
+- Check `wiki/glossary.md` before using any framework term
+- Canonical terms must be used consistently — never paraphrase a principle's name
+- ADR titles must be unique and stable (they are referenced by other pages)
+- Key terms for this domain: [populated by domain expert — add canonical terms here as the wiki develops]
+
+---
+
+## R Functions in This Application
+
+The following R functions implement validation and generation capabilities for {{PROJECT_NAME}}:
+
+{{EXPORTED_FUNCTIONS}}
+
+**Standard framework function pattern:**
+- `validate_*()` functions check compliance and return violations with severity
+- `scaffold_*()` functions generate new instances conforming to the framework
+- `get_*_status()` functions report system health
+- `get_validation_rules()` returns all rules with descriptions (discovery endpoint)
+
+---
+
+## Principle Documentation Standard
+
+Every principle must meet these standards before it can be enforced:
+
+1. **Named** — A canonical name in the glossary
+2. **Defined** — A `wiki/principles/` page with precise definition
+3. **Justified** — The ethical or practical basis is documented (who authorized this and on what grounds)
+4. **Implemented** — At least one `wiki/patterns/` page shows how to comply
+5. **Enforced** — An automated check exists OR the absence of automation is noted and justified
+6. **Governed** — The process for changing this principle is documented
+
+Principles that lack justification or governance documentation should be marked `status: draft` and flagged in the next lint pass.
+
+---
+
+## Connection to the Meta-Framework Layer
+
+This wiki documents **what {{PROJECT_NAME}} requires** and **why**. The dataimago-design wiki documents **how framework-type applications are built**. The connection:
+
+```
+wiki/principles/my-principle.md
+  → implemented by wiki/patterns/my-pattern.md
+    → enforced by validate_my_rule() in R
+      → exposed at POST /validate
+        → documented in dataimago-design/wiki/patterns/rest-api-from-r.md
+```
+
+Do not duplicate dataimago-design's framework documentation here. Reference it.

package/dist/templates/KNOWLEDGE-research.md

@@ -0,0 +1,201 @@
+<!-- @dataimago/css@0.1.0-alpha.20 dist/templates/KNOWLEDGE-research.md · sha256:ef0a6748731b61840e8e8da1142db5981948da4dec78888f40f471c2a3d3300f · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync -->
+# {{PROJECT_NAME}} — Knowledge Base Operating Manual
+
+**Domain:** {{DOMAIN_NAME}}
+**Type:** research
+**Generated:** {{GENERATED_DATE}}
+**Framework:** [dataimago-design]({{FRAMEWORK_WIKI_URL}}/wiki/index.md)
+
+This file is the operating manual for the **{{PROJECT_NAME}}** knowledge base — an AI-maintained wiki that documents the ideas, evidence, methods, and arguments that this application embodies. Read it at the start of every knowledge-work session.
+
+---
+
+## Role
+
+You are the wiki maintainer for **{{PROJECT_NAME}}**'s knowledge base — a `research`-type domain wiki that synthesizes the evidence, methods, and arguments behind the application's analytical claims.
+
+Your job is to:
+- Ingest source materials and extract knowledge into structured wiki pages
+- Keep pages consistent, cross-referenced, and up to date
+- Answer queries by reading the wiki (not re-deriving from scratch)
+- File good answers back as `wiki/analyses/` pages so knowledge compounds
+- Periodically lint the wiki for contradictions, stale content, and orphan pages
+
+You never modify files in `raw/`. You own everything in `wiki/`.
+
+The framework layer (how this application is built) is documented in the dataimago-design wiki (see `dataimago-framework.json` for the URL). Domain knowledge questions belong here; build and architecture questions belong there.
+
+---
+
+## Session Start Protocol
+
+At the start of every knowledge-work session:
+1. Read this file (KNOWLEDGE.md)
+2. Read `wiki/index.md` to orient to the current knowledge base state
+3. Read the last 5 entries of `wiki/log.md` to understand recent activity
+4. Read the framework wiki index (URL in `dataimago-framework.json`) for framework context (optional unless architecture is relevant)
+5. Ask the user: ingest, query, lint, or something else?
+
+---
+
+## Directory Structure
+
+```
+wiki/
+├── index.md         ← Master catalog of all wiki pages
+├── overview.md      ← High-level synthesis of the knowledge base
+├── glossary.md      ← Canonical terminology for this domain
+├── log.md           ← Append-only activity record
+├── sources/         ← Summaries of papers, datasets, conversations
+├── theories/        ← Theoretical frameworks the research uses
+├── methods/         ← Methodological choices and their justifications
+├── findings/        ← Specific results with interpretation
+├── arguments/       ← Central claims and their evidence chains
+├── personas/        ← Who uses this application and what they need
+└── analyses/        ← Synthesized outputs, comparisons, strategic insights
+
+raw/
+├── papers/          ← PDFs, journal articles, preprints
+├── conversations/   ← AI dialogues, meeting notes, transcripts
+├── data/            ← Datasets, R output files, analysis exports
+└── references/      ← External codebases, specs, documentation
+```
+
+---
+
+## Entity Types
+
+| Type | Location | Page purpose |
+|---|---|---|
+| **Source** | `wiki/sources/` | Summary of a raw document: key claims, quotes, metadata |
+| **Theory** | `wiki/theories/` | A theoretical framework: definition, key thinkers, application here |
+| **Method** | `wiki/methods/` | A methodological choice: what was done, why, limitations |
+| **Finding** | `wiki/findings/` | A specific result: statistical context, interpretation, R function reference |
+| **Argument** | `wiki/arguments/` | A central claim: what it asserts, what evidence supports it, what challenges it |
+| **Persona** | `wiki/personas/` | A user type: goals, what they need from this application |
+| **Analysis** | `wiki/analyses/` | A synthesized output: comparison, gap analysis, strategic insight |
+
+---
+
+## Page Format
+
+Every wiki page must have this YAML frontmatter:
+
+```yaml
+---
+title: <page title>
+type: source | theory | method | finding | argument | persona | analysis
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+sources:
+  - <raw/ filenames or wiki pages that informed this>
+tags:
+  - <relevant tags>
+---
+```
+
+Followed by: one-line summary, body with headers and tables, and a **Related pages** section at the bottom using `[[page-name]]` links.
+
+---
+
+## Workflows
+
+### Ingest a Paper or Article
+
+1. Read the source file from `raw/papers/` or `raw/references/`
+2. Discuss key takeaways (ask 1-3 clarifying questions if needed)
+3. Create a summary page in `wiki/sources/`
+4. Identify which theories, methods, or arguments it supports or challenges — update those pages
+5. Create new entity pages as warranted (new theory, new method, etc.)
+6. Update `wiki/glossary.md` with new domain terms
+7. Update `wiki/index.md` and `wiki/overview.md` if the source shifts the big picture
+8. Append to `wiki/log.md`
+
+### Ingest an R Analysis Output
+
+1. Read the output from `raw/data/`
+2. Identify what R function produced it and with what parameters
+3. Create or update a `wiki/findings/` page documenting the result
+4. Link the finding to the argument(s) it supports in `wiki/arguments/`
+5. Note the R function and parameters in the finding page (makes it verifiable and updatable)
+6. Update `wiki/index.md` and append to `wiki/log.md`
+
+### Ingest a Conversation
+
+1. Read the transcript from `raw/conversations/`
+2. Extract: key decisions made, questions raised, terminology clarified, arguments refined
+3. Update affected wiki pages (typically `wiki/arguments/`, `wiki/methods/`, `wiki/analyses/`)
+4. Create new pages if new concepts emerged
+5. Update `wiki/glossary.md` and append to `wiki/log.md`
+
+### Query
+
+1. Read `wiki/index.md` to identify relevant pages
+2. Read those pages
+3. Synthesize a clear answer with citations to wiki pages
+4. Ask: "Should I file this as a wiki page?" If yes, save to `wiki/analyses/`
+5. Append to `wiki/log.md`
+
+### Lint
+
+1. Read all pages in the wiki
+2. Report: contradictions between pages, stale claims, orphan pages, missing cross-references, inconsistent terminology
+3. Propose fixes and ask which ones to apply
+4. Append to `wiki/log.md`
+
+---
+
+## Log Format
+
+```
+## [YYYY-MM-DD] <action> | <title>
+
+**Action:** <description>
+Pages created: ...
+Pages updated: ...
+Key additions: ...
+```
+
+---
+
+## Terminology Discipline
+
+- Check `wiki/glossary.md` before using any domain term
+- If a new term appears in a source, add it to the glossary before using it elsewhere
+- If a term conflicts with an existing entry, flag it explicitly before updating
+- Key terms for this domain: [populated by domain expert — add canonical terms here as the wiki develops]
+
+---
+
+## R Functions in This Application
+
+The following R functions are the analytical backbone of {{PROJECT_NAME}}. Each exported function should have a corresponding wiki entry linking its output to `wiki/findings/` pages:
+
+{{EXPORTED_FUNCTIONS}}
+
+When ingesting an R analysis output, always record:
+- Which function produced it
+- The parameter values used
+- The date it was run
+- What finding page documents it
+
+---
+
+## Philosophical Alignment
+
+Every wiki page is evaluated against the question: does this serve the application's purpose of making research accessible to its intended audiences? Knowledge that exists only in academic prose has a single audience. Knowledge filed in this wiki serves general readers (via the web app), data analysts (via the API), AI agents (via MCP tools), and the domain expert themselves (via this wiki).
+
+---
+
+## Connection to the Framework Layer
+
+This wiki documents **what** this application knows. The dataimago-design wiki documents **how** the application is built. When a finding page references an R function, that function's API exposure is documented in the framework layer. The connection is:
+
+```
+wiki/findings/my-finding.md
+  → references HelloWorld::my_function()
+    → exposed at GET /my-endpoint
+      → documented in dataimago-design/wiki/patterns/rest-api-from-r.md
+```
+
+Do not duplicate framework documentation here. Reference it.

package/dist/templates/quarto_website/README.md

@@ -0,0 +1,48 @@
+<!-- @dataimago/css@0.1.0-alpha.20 dist/templates/quarto_website/README.md · sha256:19a8e30db9c7fc15e62e7bebb573041947b31be886d2e32d75b217236b0ab421 · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync -->
+# Quarto Website Template
+
+Canonical template for Quarto-powered R package websites built with the dataimago framework.
+
+## Usage
+
+This template is consumed by `dataimago::create_quarto_documentation()` when `scaffold_full_site = TRUE`. It can also be used manually by copying the template files and replacing placeholders.
+
+## Placeholders
+
+All `.template` files use Mustache-style `{{PLACEHOLDER}}` syntax:
+
+| Placeholder | Source | Description |
+|---|---|---|
+| `{{PACKAGE_NAME}}` | DESCRIPTION `Package` field | R package name |
+| `{{PACKAGE_TITLE}}` | DESCRIPTION `Title` field | Full package title |
+| `{{PACKAGE_DESCRIPTION}}` | DESCRIPTION `Description` field | Package description |
+| `{{PACKAGE_AUTHOR}}` | DESCRIPTION `Authors@R` field | Author information |
+| `{{PACKAGE_LICENSE}}` | DESCRIPTION `License` field | License type |
+| `{{SITE_URL}}` | DESCRIPTION `URL` field | GitHub Pages URL |
+| `{{REPO_URL}}` | DESCRIPTION `BugReports` (minus `/issues`) | GitHub repo URL |
+
+## Template Files
+
+- `_quarto.yml.template` -- Site configuration with navbar, sidebar, footer, and theme
+- `index.qmd.template` -- Homepage with hero section and feature cards
+- `ethics.qmd.template` -- Ethical AI principles from dataimago-design wiki
+- `about.qmd.template` -- Package about page
+
+## Static Assets (no templating)
+
+- `assets/js/scroll.js` -- Sticky header shrink on scroll
+- `assets/js/custom-anchors.js` -- Left-placed anchor links on headings
+- `assets/js/logo-switch.js` -- Theme-aware logo hover effects (uses `{{SITE_URL}}`)
+
+## Features Included
+
+- Sticky navbar that shrinks on scroll
+- Custom anchor links on all headings
+- Theme-aware logo switching (dark/light mode)
+- Lenis smooth scrolling
+- Accessibility layer (reduced motion, high contrast, skip links)
+- Ethics-first content pages sourced from dataimago-design wiki
+- Documents and presentations content scaffolding
+- News/changelog page
+- Custom 404 page
+- Open Graph and Twitter Card metadata

package/dist/templates/quarto_website/_quarto.yml.template

@@ -0,0 +1,141 @@
+# @dataimago/css@0.1.0-alpha.20 dist/templates/quarto_website/_quarto.yml.template · sha256:d28f9f49ba75df94183a074bcab94399ea10368ddfd538055f6b421d8194af91 · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync
+project:
+  type: website
+  title: "{{PACKAGE_TITLE}}"
+  output-dir: ../../docs
+  render:
+   - "*.qmd"
+   - "!content/presentations/**"
+   - "content/documents/**"
+
+execute:
+  freeze: auto
+
+extensions:
+  - dataimago/ai-native
+
+filters:
+  - svg-inline
+
+references:
+  - type: r
+    title: "Function Reference"
+    source: "../../man"
+
+website:
+  site-url: "{{SITE_URL}}"
+  repo-url: "{{REPO_URL}}"
+  title: "{{PACKAGE_TITLE}}"
+  description: "{{PACKAGE_DESCRIPTION}}"
+  favicon: /assets/img/ai_monogram_supreme_favicon.png
+  repo-actions: none
+  page-navigation: false
+  bread-crumbs: false
+
+  navbar:
+    title: "{{PACKAGE_NAME}}"
+    logo: /assets/img/ai_monogram.svg
+    logo-alt: "{{PACKAGE_NAME}}"
+    logo-href: "{{SITE_URL}}"
+    title-href: "{{SITE_URL}}"
+    search: false
+    pinned: true
+    left:
+      - href: index.qmd
+        text: Home
+      - href: r_package.qmd
+        text: R Package
+      - text: Ethics
+        menu:
+          - href: ethics.qmd
+            text: Ethical AI Principles
+          - href: design_system.qmd
+            text: Design System
+          - href: governance.qmd
+            text: Democratic Governance
+      - text: Foundation
+        menu:
+          - href: mission.qmd
+            text: Mission & Vision
+          - href: philosophy.qmd
+            text: Philosophy
+      - text: Resources
+        menu:
+          - href: documents.qmd
+            text: Documents
+          - href: presentations.qmd
+            text: Presentations
+      - href: news.qmd
+        text: News
+    right:
+      - text: "<img src='/assets/img/github_logo.svg' class='navbar-github-logo' title='GitHub' alt='GitHub' style='height:32px; vertical-align:middle; padding-right: 2px; margin-top: 0px;'/>"
+        menu:
+          - href: "{{REPO_URL}}"
+            text: Source Code
+          - href: "{{REPO_URL}}/issues"
+            text: Report a Bug
+          - href: "{{REPO_URL}}/discussions"
+            text: Request a Feature
+        target: _blank
+
+  sidebar:
+    style: "docked"
+    search: true
+    contents:
+       - section: "Getting Started"
+         contents:
+           - r_package.qmd
+       - section: "Ethics & Design"
+         contents:
+           - ethics.qmd
+           - design_system.qmd
+           - governance.qmd
+       - section: "Foundation"
+         contents:
+           - mission.qmd
+           - philosophy.qmd
+       - section: "Resources"
+         contents:
+           - documents.qmd
+           - presentations.qmd
+           - news.qmd
+
+  page-footer:
+    left:
+      - text: "<img src='/assets/img/quarto_logo.svg' class='footer-quarto-logo inline-svg' title='quarto.org' alt='quarto.org' style='width:28px; height:28px; vertical-align:middle; padding-right: 4px; margin-top: 6px;'/>"
+        href: https://quarto.org/
+        target: _blank
+    center:
+      - text: "<img src='/assets/img/ai_monogram.svg' class='footer-ai-monogram-logo inline-svg' title='dataimago.ai' alt='dataimago.ai' style='height:28px; vertical-align:middle; padding-right: 4px; margin-top: 6px;'/>"
+        href: https://dataimago.ai/
+        target: _blank
+      - text: "<img src='/assets/img/package_hex_logo.svg' class='footer-package-hex-logo inline-svg' title='{{PACKAGE_NAME}} R Package' alt='{{PACKAGE_NAME}} R Package' style='height: 32px; margin-top: 3px;'/>"
+        href: "{{SITE_URL}}"
+
+metadata:
+  image: /assets/img/ai_monogram_supreme_COLOR.png
+  open-graph: true
+  twitter-card:
+    image: /assets/img/ai_monogram_supreme_COLOR.png
+    card-style: summary_large_image
+
+format:
+  html:
+    theme:
+      light: _extensions/dataimago/ai-native/assets/css/dataimago-light.scss
+      dark: _extensions/dataimago/ai-native/assets/css/dataimago-dark.scss
+    toc: true
+    toc-depth: 3
+    code-copy: true
+    code-overflow: wrap
+    include-after: |
+      <link rel="preconnect" href="https://fonts.googleapis.com">
+      <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+      <link href="https://fonts.googleapis.com/css2?family=Josefin+Sans:wght@200;300;400;500;600;700&family=Noto+Sans:wdth,wght@100..125,300..800&family=Noto+Sans+Math&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
+      <script src="https://unpkg.com/lenis@1.3.8/dist/lenis.min.js"></script>
+      <script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>
+      <script type="text/javascript" src="/assets/js/scroll.js"></script>
+      <script type="text/javascript" src="/assets/js/logo-switch.js"></script>
+      <script type="text/javascript" src="/assets/js/lenis-integration.js"></script>
+      <script type="text/javascript" src="/assets/js/custom-anchors.js"></script>
+      <script type="text/javascript" src="/assets/js/accessibility.js"></script>

package/dist/templates/quarto_website/about.qmd.template

@@ -0,0 +1,36 @@
+<!-- @dataimago/css@0.1.0-alpha.20 dist/templates/quarto_website/about.qmd.template · sha256:5f896d14240e32c56a8711cbc458e8d3726cf8bcebac154aa62ead41f49af185 · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync -->
+---
+title: "About {{PACKAGE_NAME}}"
+format:
+  html:
+    toc: true
+    toc-depth: 2
+---
+
+## Overview
+
+{{PACKAGE_DESCRIPTION}}
+
+## Built with dataimago
+
+{{PACKAGE_NAME}} is built using the [dataimago](https://dataimago.ai) framework --- an AI-native application development framework for data science. dataimago provides:
+
+- Complete design system compilation from tokens to production-ready assets
+- Multi-platform deployment (Quarto, Shiny, Next.js)
+- MCP-compatible tooling for AI agent integration
+- Ethical AI build-time validation
+- R-first workflows with modern web tools
+
+## Author
+
+{{PACKAGE_AUTHOR}}
+
+## License
+
+{{PACKAGE_LICENSE}}
+
+## Links
+
+- [GitHub Repository]({{REPO_URL}})
+- [Bug Reports]({{REPO_URL}}/issues)
+- [dataimago Framework](https://dataimago.ai)

package/dist/templates/quarto_website/assets/js/custom-anchors.js

@@ -0,0 +1,6 @@
+// @dataimago/css@0.1.0-alpha.20 dist/templates/quarto_website/assets/js/custom-anchors.js · sha256:9b0f2d567a86e90431cc1470a6542f4e0549245dfda7b1b05b94119bddab0cb9 · generated from tokens; do not edit · restore: npx -p @dataimago/css@0.1.0-alpha.20 dataimago-sync
+anchors.options = {
+  placement: 'left',
+  visible: 'hover'
+};
+anchors.add('h1, h2, h3, h4, h5, h6');