Preliminary docs tidy for 2026.3

[seanbudd]

Summary of the issue:

We started performing rough grouping of changelog items around 2023.
Turning these subgroupings into subheadings would help with navigation.
Performing the review/update for the changelog for each release involves shuffling and often indenting items.
This makes it hard to review.
We could consider adding regular subheadings to our template when creating each new releases changelog sections.
This would make many changelog entries ordered from when they are first merged, making the beta docs review simpler.

Description of user facing changes:

Restructure changelog sections

Description of developer facing changes:

Description of development approach:

Testing strategy:

Known issues with pull request:

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.