Feedback from user chat with Rhian

As noted by @Nat-Stephenson. This is just the raw user stories and actions. Not prioritised (yet).

Should (to be moved into sub-issues)

• Prominent IDs: Prototype a consistent formatting style for functional area IDs and other key searchable identifiers, such as outlined boxes or code style labels.
• Visual hierarchy: Add lightweight visual breaks, icons, separators, or boxed IDs to reduce dense text and improve scanning.

Could

• Landing page structure: Draft a documentation landing page that separates high level orientation from detailed technical reference.
• Output first journey: Map the user journey from capacity output in the flat file to the relevant assumptions, classification logic, and conversion formula.
• Functional area catalogue: Create or redesign a searchable linked catalogue of functional areas, grouped by beds, rooms, spaces, theatres, and other natural categories.
• Search reliability: Test search using flat file IDs and document mismatches where the wrong page or subheading appears first.
• Terminology review: Rename or explain unclear labels such as classification register, routing logic, cohort definitions, workload assumptions, and FRM (formula?)
• Abbreviations page: Create an alphabetised abbreviations page with plain English descriptions and searchable terms. Potentially a table....
• GitHub linking pattern: Define when documentation should link to GitHub discussions or full technical registers.