[josh-heyer]

What Changed?

Adds a .registry.yaml file to each top-level content directory, and one in each directory that holds a nested product, such as advocacy_docs/pg_extensions/pg_squeeze/. Each file says what the product in its directory is: whether it's a product or a section, its display names, its aliases, its icon and which subdirectories are versions. For example, product_docs/docs/pgd/.registry.yaml:

kind: product
names:
  name: EDB Postgres Distributed (PGD)
  shortName: EDB Postgres Distributed
  abbreviation: PGD
icon: default/HighAvailability
versions: all

These definitions are for the Docusaurus build. The Gatsby build doesn't read them, and gatsby-config.js now tells its filesystem sources to ignore them. Without that, Gatsby would publish each file to the site, because it copies every .yaml file it sources into public/.

edb-postgres-ai is split across both content roots. Its one definition is in product_docs/docs/edb-postgres-ai/, where its version directories are.

The expression-replacement demo

The playground's expression-replacement page moves to expression-replacement/index.mdx (same URL), with its own .registry.yaml holding the names src/constants/products.js gives "Expression Replacement". In the Docusaurus build that name was an alias on the playground section, which has no short name, so the page's "Scope of" heading rendered an error. The Gatsby build is unchanged: the page's product: and version: frontmatter still map to products.js.

For writers, once the Docusaurus build reads these files: adding a new top-level product directory, or a new version of edb-postgres-ai, needs a matching change to its .registry.yaml in the same PR. Most versioned products use versions: all, so adding a version to them needs no change.

🤖 Generated with Claude Code

Tip

Draft deployment: https://deploy-preview-7233--edb-docs-staging.netlify.app/docs/