Site Change Log
A chronological record of structural, design, and learning-experience decisions across the site. Entries are ordered newest first.
16 January 2026 — v0.4
What changed
- Removed all browser alert-based feedback from Self-Check interactions
- Stabilised quiz interaction model with inline, per-question feedback
- Standardised Self-Check visual hierarchy across all topic pages
- Simplified CSS to eliminate overlapping visual state conflicts
Why
- Alerts disrupted reading flow and reduced perceived credibility
- Inline feedback better reflects audit and advisory discussions
- Consistency across topics improves cognitive trust
- Stability prioritised over decorative UX
15 January 2026 — v0.3
What changed
- Refined flashcard interaction to remove dead-end states
- Introduced consistent question → answer → continuation flow
- Clearly separated Flashcards and Self-Check as learning modes
Why
- Prevent user confusion during answer reveal
- Align interactions with reflective, executive reading behaviour
- Avoid LMS-style testing metaphors
2 January 2026 — v0.2
What changed
- Introduced accordion-based sections across topic pages
- Added contextual imagery to support visual scanning
- Improved separation between conceptual sections
- Introduced
/thinking.htmlas a long-form reflection space - Published the Thinking page without navigation or homepage linkage
Why
- Reduce cognitive load on long-form content
- Support progressive disclosure for senior readers
- Improve page structure without visual noise
- Create a low-noise space for reflective governance thinking
- Allow interest in long-form reflections to emerge organically
1 January 2026 — v0.1 (Public baseline)
What changed
- Public baseline of the site established
- Core positioning, focus areas, and knowledge structure frozen
Why
- Mark the transition from pilot to public reference site
- Create a stable baseline for controlled iteration
22 December 2025 — Pilot completion
What changed
- Initial site design and content completed
- Navigation, focus areas, and knowledge sections drafted
- Site shared privately for early feedback
Why
- Validate structure and tone before public release
- Incorporate trusted peer feedback early
- Identify UX and clarity gaps prior to baseline freeze