Skip to content

docs: add automated what's new highlights - #25729

Open
dvdksn wants to merge 8 commits into
docker:mainfrom
dvdksn:codex/whats-new-stub
Open

docs: add automated what's new highlights#25729
dvdksn wants to merge 8 commits into
docker:mainfrom
dvdksn:codex/whats-new-stub

Conversation

@dvdksn

@dvdksn dvdksn commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Replace the static Featured topics homepage section with a data-driven What's new feed. Add a daily Claude Sonnet 5 curator with strict inclusion criteria, a seven-day sliding window, deterministic validation, and bot-managed pull requests.

The seed data is a curation of merged documentation from August 3 through August 9, 2026. It contains seven qualifying highlights across Docker Sandboxes, Docker AI Governance, Docker Desktop, and Docker Engine.

@netlify /

Homepage preview

Generated by Codex

@netlify

netlify Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 7e3119a
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a797b9f77d83c000802b284
😎 Deploy Preview https://deploy-preview-25729--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@github-actions github-actions Bot added area/release Relates to CI or deployment hugo Updates related to hugo ci ci updates labels Aug 6, 2026

@docker-agent docker-agent left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

The What's new pipeline looks solid. The homepage layout correctly renders the section once via the layout partial (not via .Content), validation logic is sound, and the workflow's error handling is appropriate given GitHub Actions' bash -eo pipefail default. One minor suggestion on the duplicate-detection logic.

Comment thread hack/validate-whats-new.mjs Outdated
@dvdksn
dvdksn force-pushed the codex/whats-new-stub branch from d72b47a to f287b70 Compare August 6, 2026 15:08
dvdksn added 8 commits August 10, 2026 07:17
The homepage featured topics were static and did not surface newly released Docker capabilities. Add data-driven highlights, a strict curation agent, validation, and a weekly pull request workflow.
The initial automation reviewed a fixed Monday-to-Sunday period only once per week. Run it daily over the previous seven complete UTC days, preserve pending proposals, and avoid pull requests for metadata-only window changes.
The curator copied an arbitrary 8192-token cap and an outdated schema modeline from the nightly scanner. Use Claude Sonnet 5, set a task-sized 4096-token response cap, and point YAML tooling at agent-schema.json.
The initial two-item seed used an older publication window and did not demonstrate release-note or multi-PR highlights. Curate the latest seven-day window into four qualifying launches and permit substantive features found in vendored syncs.
@dvdksn
dvdksn force-pushed the codex/whats-new-stub branch from 35f5200 to 7e3119a Compare August 10, 2026 07:19
@dvdksn
dvdksn requested a review from a team August 10, 2026 07:27
@dvdksn
dvdksn marked this pull request as ready for review August 10, 2026 07:27

@docker-agent docker-agent left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

The PR introduces a data-driven "What's New" feed on the Docker docs homepage, replacing the static "Featured topics" section. The implementation is well-structured: the Hugo partial correctly reads from hugo.Data, the workflow has sensible guards (agent scope check, prettier formatting, custom validator), and the validator script covers the key correctness invariants (required fields, ISO date format, sort order, title and URL uniqueness).

No high or medium severity issues found. Specifically:

  • No AI-isms or hedge words in any user-facing content
  • No missing front matter (no .md content pages added)
  • No missing redirects (the removed "Featured topics" section was inline HTML with no routable URL)
  • No vendored/generated files modified
  • Hugo template syntax and shortcode usage are valid
  • data/whats-new.json is hand-authored root-level JSON and correctly reviewed as such

@docker-agent docker-agent left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

The PR replaces the static "Featured topics" homepage section with a data-driven What's new feed. All eight changed files were reviewed:

  • .github/workflows/update-whats-new.yml — CI workflow (infrastructure, not documentation prose)
  • hack/validate-whats-new.mjs — validation script with deterministic checks (not documentation prose)
  • layouts/_partials/whats-new.html — Hugo partial with correct semantic HTML (<time>, <ol>, <li>, aria-hidden on decorative span)
  • layouts/home.html — removes static section, replaces with partial call
  • content/_index.md — homepage content; no style or accuracy issues
  • data/whats-new.json — seed data with seven entries; descriptions are factual, direct, and free of hedge words or marketing language
  • .github/agents/whats-new.yaml — agent instructions; clear inclusion criteria and deterministic constraints
  • layouts/_shortcodes/whats-new.markdown.md — shortcode template; no prose issues

No documentation issues found in the changed lines. Good work!

@aevesdocker aevesdocker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Curious where the request to have this came from?

Will we get analytics on this to see if users follow these 'What's new' links?

@dvdksn

dvdksn commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

@aevesdocker I've been thinking about it for a while but it was most recently brought up by @ajeetraina in our devrel sync last week - he was asking if there's a good way to find out about new product changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Relates to CI or deployment ci ci updates hugo Updates related to hugo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants