> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-09-29-docs.md).

# KlassApp · Task D v2: one VitePress site for all docs, plus brand materials (2026-09-29)

* **Designed from:** `main @ 9f3297546d8c`.
* **HANDOFF.md:** five phased PRs: P1 scaffold and theme, P2 Help, P3 Community migration and redirects, P4 GitBook migration and retirement, P5 search and checks.
* **MIGRATION.md:** every Docsify and GitBook page, with its new URL, what merges or is dropped, and the redirects needed.
* **vitepress/docs-site/:** config, theme tokens, 13 Vue components, and page templates for 6 Help and 6 Community page types. **Never installed or built.**
* **CANVA-SPECS.md:** social templates and the pitch deck.
* **design-system/:** the updated design system and the Task D concepts. The social media kit is `concepts/social/kit.html`: 6 content types × 8 formats, 60 artboards at real size.

**Concept:** `design-system/concepts/docs/site.html` is the VitePress-style shell: the docs home with two doors, a Help/Community switch, a search dialog opened with Ctrl K that covers both sections, 6 Help templates and 6 Community templates. `index.html` shows every page at 1280 and 375.

**Not browser-measured:** contrast ratios (calculated from hex), print output, Canva, and the VitePress build and performance budgets.

**Update 2026-10-02:** HANDOFF P6 adds **Blog and Events** (concept `design-system/concepts/docs/blog/index.html`; Vue components `PreviewLabel`, `PostList`, `PostMeta`, `EventList`, `EventTime`, `AddToCalendar`; first post "KlassApp opens to founding schools"). The voice guide and readme carry the agreed positioning.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-09-29-docs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.