Skip to content

docs: add the registry as a product section on the hub (PROT-50)#1

Draft
BlakeHastings wants to merge 1 commit into
mainfrom
docs/PROT-50-registry-on-hub
Draft

docs: add the registry as a product section on the hub (PROT-50)#1
BlakeHastings wants to merge 1 commit into
mainfrom
docs/PROT-50-registry-on-hub

Conversation

@BlakeHastings
Copy link
Copy Markdown
Member

Add the Registry as a product section on the docs hub (PROT-50)

Part of the PROT-50 documentation pass (epic PROT-49). Draft — content review pending, do not mark ready yet.

What changed

  • docs.manifest.json — add protostar-registry as a product, so it renders as its own "Registry" navbar section (route /registry), lifted from the registry repo's docs/ at build time.
  • docs-hub/intro.md — add the Registry to the documentation map alongside the CLI.

Notes

  • The Registry section only renders in CI/production once the registry repo's docs are on its main (the hub fetches remote in CI; locally it lifts from the sibling checkout). See the companion registry PR.
  • npm run build passes locally with both products lifted in (onBrokenLinks: throw).

Add protostar-registry to docs.manifest.json so it renders as its own
"Registry" navbar section, and list it in the hub overview's documentation
map alongside the CLI.

Part of PROT-50 (docs how-to pass under epic PROT-49).
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