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: [Save]
• Menu path: File → Save

See Template:BathAfrica Key, Template:BathAfrica Button, and Template:BathAfrica Menu for usage.

Existing SiteMasterDoc template migration

All 75 existing source templates and their 150 historical revisions have now been imported. Shared compatibility styles and extension fallbacks are installed. See BathAfrica:Template migration for the complete status and BathAfrica:Legacy template tests for the rendering gallery.

All 159 static dependency images have been recovered and preserved, including 155 recovered upstream because they were absent from SiteMasterDoc. All 159 are now installed and registered on this wiki. See BathAfrica:Image migration tests for the complete image gallery. All 159 images render after enabling native SVG rendering with a 256 KB size limit. The current imported templates use BathAfrica branding; original source histories and attribution are retained.

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.