BathAfrica:Documentation authoring
This guide is for documentation authors across BathAfrica products.
Shared page templates
- Template:BathAfrica Command — command identifiers, examples, output, errors, limitations, and verification evidence.
- Template:BathAfrica Feature — behavior, source-reported status, units, hosts, licensing, and evidence.
- Template:BathAfrica Tutorial — prerequisites, steps, expected result, and limitations.
- Template:BathAfrica Workbench — tools, commands, and limitations.
- BathAfrica:Template examples — fictional rendering demonstrations.
Use the optional review parameter to display a review notice. A historical “verified” label is not evidence that the current build was tested.
Inline formatting
- Keyboard key: Ctrl
- Button label:
- Menu path: File → Save
See Template:BathAfrica Key, Template:BathAfrica Button, and Template:BathAfrica Menu for usage.
Existing SiteMasterDoc template audit
The old template inventory remains available. The following source templates were inspected on 29 October 2026:
- GuiCommand: uses ParserFunctions, optional command images, old ct/fcinfobox CSS, LabRPS Phenomena terminology, and category assignments. Adapt before reuse.
- TutorialInfo: requires labrps.svg, old infobox CSS, and an RPSVersion field. Adapt before reuse.
- Docnav: requires arrow and LabRPS images, old navigation targets, and ParserFunctions. Adapt before reuse.
- Code: requires SyntaxHighlight and contains LabRPS-specific examples. Do not assume that extension is installed here.
- KEY, Button, MenuCommand: small inline formatting helpers; their documentation invokes VeryImportantMessage. New dependency-free BathAfrica equivalents are provided above.
No old articles, images, users, or database content were imported. If copying substantial old template code later, retain source links, contributor history and applicable attribution/license information; the original FreeCAD provenance has not yet been fully traced.
OpenSite source review
The uploaded Cursor documentation contains 27 article sources and four template authoring guides. Those guides were not executable rendering templates. The shared templates above implement their fields.
The article sources contain historical claims that need checking against the current repository and build, including GUI availability, expression support, file format version, console availability, and toolchain requirements. Do not publish those claims as current product instructions until checked. The 27 historical articles have not been published as current help.
Use product subpage titles such as OpenSite/Getting started and SiteMaster/Getting started. Keep verified functionality separate from planned features. Record the tested version and reproducible evidence when claiming verification.