Skip to content

Reverse Chronological Ordering for Activity Reports

Ticket #135: Reverse Chronological Ordering for Activity Reports
Type: Documentation / Navigation Improvement / Quality Gate
Affected Component: docs/activity_report/index.md, docs/fr/activity_report/index.md, mkdocs.yml, tests/test_docs_config.py

1. Context

The activity report overview pages originally listed reports from the oldest to the newest. This made the navigation less practical because the latest interventions were buried at the bottom of the page and deep in the MkDocs navigation menu.

2. Objective

The goal was to make activity reports immediately readable in reverse chronological order, with the newest report shown first everywhere users browse them:

  • on the English overview page
  • on the French overview page
  • in the MkDocs navigation menu for both languages

3. Implemented Changes

3.1 - Reverse ordering in overview pages
The report cards in both overview pages were reordered so the most recent interventions appear first.

3.2 - Reverse ordering in MkDocs navigation
The Activity Reports and Rapports d'activité sections in mkdocs.yml were updated to use the same reverse chronological sequence.

3.3 - Automated regression protection
A dedicated documentation test was added to ensure the activity reports stay ordered from newest to oldest in:

  • docs/activity_report/index.md
  • docs/fr/activity_report/index.md
  • mkdocs.yml

This turns the expected ordering into an explicit quality gate.

4. Verification

  • The two overview pages now announce the reverse chronology in their introduction text.
  • The newest report is displayed first in both languages.
  • The MkDocs navigation mirrors the same order.
  • The automated documentation test fails if a future edit reintroduces an older-first listing.

5. Result

The activity report section is now easier to scan and better aligned with how users typically consume operational history: recent work first, archive last.