> 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/docs/evidence/community-content-refresh/factcheck.md).

# Community Docsify content refresh — evidence

Date: 2026-09-17\
Branch: `docs/community-content-refresh`

## Theme (Playwright, 1280×900)

Served from `docs/` via `python3 -m http.server 8765`. Shared CSS: `docs/shared/docsify-klassapp.css`.

| Check                    | Result                                                         |
| ------------------------ | -------------------------------------------------------------- |
| `--d-canvas`             | `#fafaf5` on all 8 pages                                       |
| `--d-green` / `--d-blue` | present (`#22c55e` / `#1e6fd9`)                                |
| Theme stylesheet linked  | yes                                                            |
| Uganda-first body copy   | none (`\bUganda\b` false on all pages)                         |
| `$30` Growth price       | none                                                           |
| `$35` where plans listed | overview, for-schools, school-onboarding, book-onboarding, faq |

Screenshots: `01-overview.png` … `08-roadmap-deprecated.png`.

## Fact-check vs shipped product

| Claim area                                       | Source of truth                               | Docs status                                                  |
| ------------------------------------------------ | --------------------------------------------- | ------------------------------------------------------------ |
| Global positioning (hardest constraints first)   | README                                        | Aligned                                                      |
| Four-surface design shipped                      | `docs/roadmap.md`                             | Stated on for-schools / ecosystem                            |
| WhatsApp = Meta Cloud API live                   | README / Verified Stack                       | Stated; Evolution not mentioned                              |
| Drive / Slack UI model, not live API clients     | README                                        | Stated                                                       |
| Toshi guided live; free-form gated               | roadmap                                       | Stated                                                       |
| Plans Freemium / Growth **$35** / Premium custom | `PlansTableSeeder` (`amount` 0 / 35 / custom) | Corrected (was $30 in school-onboarding)                     |
| Roadmap content                                  | `docs/roadmap.md`                             | Cross-linked; community `roadmap.md` remains deprecated stub |
| Book onboarding form → fake API                  | was posting to `/api/onboarding/book`         | Replaced with mailto `community@klassapp.xyz`                |

## Pages refreshed

`README.md`, `for-schools.md`, `for-parents.md`, `faq.md`, `school-onboarding.md`, `ecosystem.md`, `book-onboarding.md`. Sidebar already pointed at hub roadmap.


---

# 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/docs/evidence/community-content-refresh/factcheck.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.