feat: bring back last-updated metadata and add filtered git history

[rudigier]

What changed

• bring back Last updated metadata (date + author) for each page.
• Added expandable commit history for each page.
• Linked commit messages directly to their GitHub commit pages.
• Filtered out non-relevant commits via an exclusion list.
• Limited visible history to relevant commits from the last 5 years.
• Centralised repository URL in config.js (repoUrl).
• Refactored git history logic out of gulp/html.js into gulp/helpers/git-metadata.js.

Why

• Make page maintenance history transparent and useful for contributors.
• Reduce noise by hiding technical/maintenance-only commits.

[netlify]

✅ Deploy Preview for accessibility-developer-guide ready!

Name	Link
🔨 Latest commit	a4c8d82
🔍 Latest deploy log	https://app.netlify.com/projects/accessibility-developer-guide/deploys/6a06d360f2250000083ab58f
😎 Deploy Preview	https://deploy-preview-478--accessibility-developer-guide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[backflip]

I like it!

The main challenge is probably filtering irrelevant commits. Example: https://deploy-preview-478--accessibility-developer-guide.netlify.app/knowledge/colours-and-contrast/ and https://deploy-preview-478--accessibility-developer-guide.netlify.app/knowledge/keyboard-only/ both show not too relevant commits in Show recent relevant commits for this page. I think I would remove that feature as the View full history on GitHub is probably helpful enough. WDYT?

[rudigier]

@backflip What I adjusted:

Most changes are not visible on normal guide pages they support developers and maintenance.

• Reverted changes in page meta (removed author and history).
• git and frontmatter helpers for updates, merges, and page lists.
• New components / pages:
  • Page updates (public): Curated component that highlights the latest page updates. The configuration is stored in config/recent-pages.js.
  • Recent changes (developer view only): Shows which pages changed in each merge to main. Includes a simple configurator for updating config/recent-pages.js.
  • Page revisions (developer view only): Table of all pages with the date of the last meaningful update, helping identify pages that need a refresh.
• Cleanup of unused code.

[rudigier]

Page updates

Developer Menu

Recent changes

Page revisions

[backflip]

@rudigier, these look great! However, I'm not sure what problem we are trying to solve with Developer Menu, Recent changes and Page revisions. I'm somewhat afraid of introducing so much code to the build system to – unless I'm misunderstanding – rebuild parts of GitHub's history UI within our porject.

[rudigier]

@backflip Fair point! We’re not rebuilding (the complete) GitHub history ;)

The idea was to make our work on the guide visible, show that ADG is actively maintained, and give maintainers an overview of content that may need a refresh soon because it’s potentially outdated. If you have a better idea or a less code involved solution, let me know.

[backflip]

@rudigier, would it be an option for you to separate the dev mode? I would feel confident that we can maintain the recent changes addition (to see the relevant changes, if have extracted that part in #492). This would allow us to discuss the solution to give maintainers an overview of content that may need a refresh soon separately.

[rudigier]

@backflip Sure, let's do this. Would you like to review the changes?