Feature: Changelog Site UI and Content Collection

[decepulis]

Note

Triage estimate — cycle priority and story points were assigned during an AI-assisted planning pass and are rough first guesses. Confirm or adjust when you pick this up.

Parent: #462

Build the changelog pages on the docs site.

Content collection

Add a changelog collection to content.config.ts with the schema from #462:

• description (optional string) — narrative summary from LLM
• date (date)
• version (string)
• prerelease (boolean)
• breaking (boolean, default false)
• compareUrl (optional URL string)

Site pages

• Render changelog entries at videojs.org/changelog or videojs.org/docs/changelog
• Use the same markdown formatting as blog and docs
• Index page listing releases (newest first), with version, date, and description

Open question

Clarify the relationship between release blog posts, migration guides, and changelog entries. Do we need all three? How do they link to each other?

[github-actions]

Planning recommendations

• Blocked by Feature: Formatted Changelog #462 — the actions pipeline sub-issue (Phase 1) must land first to populate site/src/content/changelog/. The content collection schema is defined there; this issue can't progress until that frontmatter/content shape is stable.
• Related issues to plan alongside: The open question in the body (relationship between changelog entries, release blog posts, and migration guides) overlaps with Docs: Reconsider "Getting Started" Category Name and Boundary with Concepts #1105 (Reconsider "Getting Started" category) and any future release blog infrastructure. Worth resolving that question before investing in the index page layout.
• Priority: P2 — useful polish for GA, but not blocking core functionality.
• Milestone: Consider targeting 26.3 [GA] so the changelog is present at launch, but only after Phase 1 of Feature: Formatted Changelog #462 is complete.
• Roadmap: Recommend adding to the roadmap once Feature: Formatted Changelog #462's pipeline sub-issue is in progress, to avoid building the UI before the content format is finalized.