Documentation Stack & Nuxt Upgrade

Overview of the Docus-powered documentation site, current package versions, AI integrations, and maintenance steps.

Stack Overview

Framework: Docus 5.2.1 running on Nuxt 4.2.1 (see docs/package.json).
Content source: Markdown pages under docs/content/ with Docus front matter blocks.
Styling & theme: Docus defaults extended via app.config in docs/nuxt.config.ts.
Hosting: GitHub Pages (https://nuetzliches.github.io/xtraq/) with a configurable baseURL.

File	Purpose
`docs/nuxt.config.ts`	Extends the Docus preset, registers ESLint, configures the built-in LLM experience, head metadata, and pre-render routes.
`docs/content.config.ts`	Centralises navigation structure and Markdown processing options.
`docs/app/components`	Vue components available to Markdown via MDC slots (tabs, callouts, etc.).
`docs/public/`	Static assets served verbatim (favicons, logos).

Docus ships with an llms block that enables the AI navigation assistant.

Configuration lives in docs/nuxt.config.ts under the llms section.
Update the domain, title, and description fields when the public URL changes.
To plug in a provider (OpenAI, Mistral, Azure OpenAI):
- Set provider credentials via environment variables documented at https://docus.dev/integrations/llms.
- Add the provider module to modules in nuxt.config.ts if required (e.g. @nuxtjs/openai).
- Store secrets in GitHub Actions environments; never commit API keys.
For local experiments, create a .env file in docs/ with NUXT_OPENAI_API_KEY (or equivalent) and run npx nuxt dev.

When new Docus/Nuxt releases become available:

From docs/, run npm install docus@latest nuxt@latest.
Apply necessary codemods noted in the Docus release notes and Nuxt migration guide.
Verify ESLint compatibility (npm update @nuxt/eslint eslint).
Execute npm run lint and npm run build to validate the upgrade.
Run npm run generate and smoke-test the generated site under .output/public or dist/.
Update this page with the new version numbers and add a changelog entry under docs/content/5.roadmap/index.md if user-visible behaviour changes.

cd docs
npm install
npm run dev

The GitHub Pages workflow runs npm run generate and deploys the static output.
Ensure favicons and logos exist in docs/public/ (referenced via baseURL helper in nuxt.config.ts).
Keep compatibilityDate in nuxt.config.ts current when upgrading Nuxt.