Maintain

How to update this wiki

Keep the wiki in sync with the product. Markdown in docs/ remains the contract; HTML here is for local reading.

On this page When to write Add a page Log a change Style and language

When to write

You did this	Update
Shipped a user-visible behavior	Product + Changelog + matching `docs/`
Defined a clinic workflow for web and mobile	A page under `wiki/functional/` and `docs/functional/`
Made a hard-to-reverse system decision	Architecture and `docs/architecture/`
Changed sequencing	Roadmap and `docs/roadmap/`
Changed how to run the apps	Setup and the app README

Add a page

Copy an existing HTML file in wiki/ (or wiki/functional/).
Set data-page to a unique id and data-base to . (root pages) or .. (pages in a subdirectory).
Put content inside <article class="wiki-article">.
Register the page in wiki/assets/wiki.js inside the nav array (id, title, path, keywords).
Link it from Home or a related page.

file:// only Do not fetch other HTML files at runtime. Each page must be a complete document. Shared CSS/JS via relative href/src is fine.

Log a change

Add a .timeline-item at the top of Changelog:

<div class="timeline-item">
  <time datetime="2026-08-27">27 August 2026</time>
  <h3>Short title</h3>
  <ul>
    <li>What changed and why it matters.</li>
  </ul>
  <p>Related: <a href="…">Page</a></p>
</div>

Style and language

Documentation is English (UI may still be en/es).
Status words follow Architecture → Status vocabulary: enable/disable, active, available. Do not mix them.
Use badges: shipped, next, later, intended.
Callouts: default, .warn, .danger.
Never put passwords, keys, or credential values in the wiki.
Prefer tables and short bullets over long prose.