Generate the ecosystem catalogs from the docs instead of hardcoding them

[ReneWerner87]

What does this PR change?

The homepage ecosystem cards listed middleware, storage drivers, template engines and contrib packages from hardcoded arrays with rounded counts (30+ drivers, 20+ packages), so every new package needed a manual edit in src/components/home/Ecosystem.tsx.

scripts/generate-catalogs.js now reads the four catalogs from the docs/ folder and writes src/data/catalogs.json — per package its id, its display name (front matter title, else the first heading) and its doc path. A package is one page directly below a catalog root, the same rule the landscape used before, so nested pages like contrib/socketio/legacy stay part of their package. The middleware catalog is taken from the docs version served at the site root (newest entry of versions.json).

The generated file is not tracked in git. docusaurus.config.ts calls the generator on load, which covers start, build, build:home, build:docs and a bare npx docusaurus call in one place, long before webpack resolves the import — a new script cannot forget it. Only typecheck generates on its own, since tsc never loads the config. The script needs no dependencies, only rewrites the file when its content changed, and is excluded from the spell check (that job installs dependencies, so the file exists there).

Both surfaces read that one file:

• Homepage (Ecosystem.tsx): exact badge counts and every package of a catalog as chips. The curated item lists and the + many more chip are gone; the file now only carries the wording of a card (icon, title, description, CTA).
• Ecosystem landscape (fiber-landscape/index.tsx): drops ~55 lines of docs-plugin global data plumbing and URL regexes for the same JSON. Chips now show proper display names (Redis, BasicAuth) instead of raw doc ids, and the hardcoded 30+ Middleware core chip derives its count as well. Middleware links keep the version prefix of the page the reader is on (/next/middleware/… on the Next docs).

The homepage build ships without any docs plugin, which is why the data comes from a generated file rather than the docs plugin global data the landscape used before.

Current numbers: 32 middleware, 34 storage drivers, 9 template engines, 22 contrib packages. Storage includes mockstorage and testhelpers, exactly as the landscape counted them before.

Also switches the storage, template and contrib card links from the /next/ redirects to the canonical URLs.

Verified with a deleted catalogs.json that npm run check (typecheck, matcher tests, both builds) regenerates it and passes, and by rendering the homepage and the ecosystem page from the production build.

[Copilot]

Pull request overview

This PR replaces hardcoded ecosystem package lists/counts with a single generated data source derived from the docs/ tree. It centralizes catalog metadata in src/data/catalogs.json so both the homepage ecosystem cards and the ecosystem landscape render accurate package names and counts without manual updates.

Changes:

• Add a Node-only generator script (scripts/generate-catalogs.mjs) that builds src/data/catalogs.json from the docs directories (and versioned middleware docs).
• Update the homepage ecosystem cards (Ecosystem.tsx) to render counts and chips from catalogs.json, removing curated lists and “+ many more”.
• Update the ecosystem landscape (fiber-landscape/index.tsx) to use the generated catalogs and keep version-prefixed middleware links; wire generation into npm lifecycle hooks and exclude the generated JSON from spellcheck.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/types/catalogs.ts	Adds TypeScript types for the generated catalogs JSON shape.
src/data/catalogs.json	Adds the generated, committed catalog data consumed by UI components.
src/components/home/Ecosystem.tsx	Switches homepage ecosystem cards to render counts/chips from generated catalogs.
src/components/home/Ecosystem.module.scss	Removes styling for the deleted “+ many more” chip variant.
src/components/fiber-landscape/index.tsx	Replaces docs-plugin global-data catalog plumbing with the generated catalogs JSON and version-aware middleware linking.
scripts/generate-catalogs.mjs	New generator that reads docs directories/front matter/headings and writes src/data/catalogs.json only when changed.
package.json	Runs catalog generation during install/start/build flows via pre* hooks and a dedicated script.
.cspell.json	Ignores the generated src/data/catalogs.json file for spellchecking.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR adds a catalog generator that discovers package documentation and writes typed catalog data. The ecosystem cards and fiber landscape consume this data for package labels, counts, and version-aware links.

Changes

Catalog integration

Layer / File(s)	Summary
Catalog generation and data contract src/types/catalogs.ts, scripts/generate-catalogs.mjs, .gitignore	The generator discovers package documentation, extracts labels, sorts entries, validates catalogs, and writes src/data/catalogs.json only when content changes. TypeScript types define the generated structure, and Git ignores the generated file.
Ecosystem catalog rendering src/components/home/Ecosystem.tsx, src/components/home/Ecosystem.module.scss	Ecosystem cards use generated catalog keys, labels, nouns, and exact counts. Static item lists, “many more” labels, and the .chipMore style were removed.
Fiber landscape catalog links src/components/fiber-landscape/index.tsx	The fiber landscape uses generated catalogs, displays current catalog counts, and resolves middleware links with the active documentation version.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Documentation
  participant generate_catalogs.mjs
  participant catalogs.json
  participant Ecosystem
  participant FiberLandscape
  Documentation->>generate_catalogs.mjs: provide package documents and version metadata
  generate_catalogs.mjs->>catalogs.json: generate sorted catalog data
  catalogs.json->>Ecosystem: provide entries and counts
  catalogs.json->>FiberLandscape: provide entries and counts
  FiberLandscape->>FiberLandscape: resolve version-aware catalog links

Loading

Poem

A rabbit hops through docs so bright,
And sorts each package left to right.
Catalogs bloom in JSON rows,
Counts appear where each card goes.
Versioned paths guide every leap,
While carrots rest beside the heap.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: generating ecosystem catalogs from documentation instead of hardcoded data.
Description check	✅ Passed	The description uses the required section and provides detailed scope, implementation, behavior, counts, links, and verification results.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/homepage-dynamic-display-sf1pe2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}