[Docs] Give the alpha one findable page saying what it is not yet #610

Closed
opened 2026-07-22 16:19:54 +00:00 by brenno · 1 comment
Owner

Found in the pre-publication product review.

Evidence: docs/FAQ.md:277-283 is the only roadmap, and it is stale: it lists "Additional chart visualizations and data types" as planned while README.md already enumerates thirteen chart types, and "Improved performance for large presentations" without saying what currently goes wrong. There is no ROADMAP.md and no KNOWN_ISSUES.md.

The honesty that does exist is scattered across five files: the translation gaps in the README feature line, export accessibility in docs/ACCESSIBILITY.md, web limitations in docs/HOSTING.md §5, "nothing to download yet" in docs/FAQ.md:36.

Why this matters now: expectation management that a reader has to assemble from five files does not work. A critic finds the gaps first and presents them as a discovery rather than as your openness. For a 0.1.0 alpha, "what is broken" is a feature, not an embarrassment — this project is unusually good at that kind of candour and gets no credit for it because the candour is not in one place.

Proposal: one KNOWN_LIMITATIONS.md of at most one screen that gathers the five existing admissions with a pointer to each source, plus a line at the top of the README. Replace the stale roadmap section in docs/FAQ.md with a link to it — a roadmap you do not maintain is worse than none.

Found in the pre-publication product review. **Evidence:** `docs/FAQ.md:277-283` is the only roadmap, and it is stale: it lists "Additional chart visualizations and data types" as planned while `README.md` already enumerates thirteen chart types, and "Improved performance for large presentations" without saying what currently goes wrong. There is no `ROADMAP.md` and no `KNOWN_ISSUES.md`. The honesty that does exist is scattered across five files: the translation gaps in the README feature line, export accessibility in `docs/ACCESSIBILITY.md`, web limitations in `docs/HOSTING.md` §5, "nothing to download yet" in `docs/FAQ.md:36`. **Why this matters now:** expectation management that a reader has to assemble from five files does not work. A critic finds the gaps first and presents them as a discovery rather than as your openness. For a 0.1.0 alpha, "what is broken" is a *feature*, not an embarrassment — this project is unusually good at that kind of candour and gets no credit for it because the candour is not in one place. **Proposal:** one `KNOWN_LIMITATIONS.md` of at most one screen that gathers the five existing admissions with a pointer to each source, plus a line at the top of the README. Replace the stale roadmap section in `docs/FAQ.md` with a link to it — a roadmap you do not maintain is worse than none.
Author
Owner

Opgelost in #656 (gemerged). make check groen op de gerebasede kop.

Opgelost in #656 (gemerged). `make check` groen op de gerebasede kop.
brenno 2026-07-22 17:30:05 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
LibreKAT/Ocideck#610
No description provided.