Skip to content

Add landing page data: homepage.yaml and per-product homepage placement - #7234

Open
josh-heyer wants to merge 2 commits into
developfrom
homepage-registry
Open

josh-heyer wants to merge 2 commits into
developfrom
homepage-registry

Conversation

@josh-heyer

Copy link
Copy Markdown
Contributor

The Docusaurus build's landing page was a hand-copied port of the Gatsby page, so new products (EDB Vector Plus most recently) never appeared on it. This moves the page's content into data so it can be generated.

  • Each product's .registry.yaml gets a homepage: entry: either false, or a placement (group, optional section, label, subtitle, href, and a sparse order). New products now have to say whether they belong on the landing page.
  • A new homepage.yaml at the repo root holds everything that isn't a product's root page: the banner, the groups and their sections, links to hub pages, deep pages and external sites, the "What's new" cards, and the footer links.
  • The page's current layout and links are reproduced as they are today. The one addition is EDB Vector Plus, under Agentic AI after Agent Governance.

Gatsby's filesystem sources don't include the repo root, so homepage.yaml isn't published as content. This changes no docs content and no URLs.

Open question for reviewers: pg_textsearch is a registered extension that isn't on today's page. It's homepage: false for now; say if it should be listed under Extensions.

🤖 Generated with Claude Code

… entries

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant