Skip to content

feat: generate the hero's Browse buttons from ecosystems.toml - #132

Merged
si618 merged 1 commit into
mainfrom
feat/ecosystem-buttons
Oct 25, 2026
Merged

si618 merged 1 commit into
mainfrom
feat/ecosystem-buttons

Conversation

@si618

@si618 si618 commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

What changed

The home page hero's Browse buttons come from ecosystems.toml. pages/index.md has an <!-- ecosystem-buttons --> marker after How it works, and write_buttons in scripts/stage.py replaces it with a Browse button for each live ecosystem, in file order. A soon ecosystem gets no button, because it has no pages to browse. The stage fails if the marker is missing or appears twice, as it does for the cards.

Checked with just check and just build: the built hero shows Browse .NET and Browse Rust, as before. With rust set to soon locally, the hero shows only Browse .NET, and the Rust card shows as coming next.

Why

The buttons are hard-coded, so each new ecosystem needs one added by hand. Rust went live in #91, which made its card a link, but the hero kept only Browse .NET until #129.

Closes: #131

@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c77ea495-8d64-43f1-b127-238debd9b0a1
Commits

Reviewing files that changed from the base of the PR and between 1eb36ee and 873c081.

Files selected for processing: 2
  • pages/index.md
  • scripts/stage.py

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

Walkthrough

Staging now generates the homepage hero’s Browse buttons from ecosystems.toml. It adds links for live ecosystems in registry order, omits coming-soon ecosystems, and records an error if the page does not contain exactly one marker.

Changes: Homepage Browse buttons

Layer / File(s) Summary
Marker-driven button generation
pages/index.md, scripts/stage.py
The homepage replaces hard-coded Browse links with a marker. Staging replaces that marker with escaped links for live ecosystems in registry order. It records an error and leaves the page unchanged if the marker does not occur exactly once.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant Registry as ecosystems.toml
  participant Stage as scripts/stage.py
  participant Page as pages/index.md
  Stage->>Registry: Read ecosystem entries
  Stage->>Page: Replace hero marker with links for live ecosystems
Loading

Possibly related PRs

Merge Risk: Minimal · up to 873c0

The homepage Browse links are generated from live registry entries, and staging reports an error if the marker is missing or duplicated. No concrete merge-blocking risk is established.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 1 files. (1 skipped: 1… Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed Passed checks: 4 passed
Check name Status Explanation
Description check Passed The description explains the change: the hero's Browse buttons now come from ecosystems.toml through a new marker and write_buttons in scripts/stage.py. It covers the live/s…
Linked Issues check Passed Issue #131 requires generated Browse links in the hero, after “How it works”, for live ecosystems in ecosystems.toml order. pages/index.md contains the single <!-- ecosystem-buttons --> marker i…
Out of Scope Changes check Passed The changes are limited to the home-page marker and the staging code that generates its buttons. The documentation update describes this same staging behaviour. No unrelated change is shown in the rev…
Title check Passed The title states the main change: the hero's Browse buttons are now generated from ecosystems.toml instead of being maintained by hand. The raw summary and PR objectives confirm this. A new marker in …
Full details: Description check

Explanation

The description explains the change: the hero's Browse buttons now come from ecosystems.toml through a new <!-- ecosystem-buttons --> marker and write_buttons in scripts/stage.py. It covers the live/soon handling, the failure on a missing or duplicate marker, and the verification steps. It also gives the motivation and links issue #131. It matches the raw summary and the objectives.

Full details: Linked Issues check

Explanation

Issue #131 requires generated Browse links in the hero, after “How it works”, for live ecosystems in ecosystems.toml order. pages/index.md contains the single &lt;!-- ecosystem-buttons --&gt; marker in that position. write_buttons replaces it with &lt;a class="ah-btn" href="&lt;id&gt;/"&gt;Browse &lt;name&gt;&lt;/a&gt; links, filters for live, preserves registry() order, and HTML-escapes names. It records an error when the marker does not occur exactly once, so staging fails for a missing or duplicate marker. No separate automated-test requirement is stated in #131.

Full details: Out of Scope Changes check

Explanation

The changes are limited to the home-page marker and the staging code that generates its buttons. The documentation update describes this same staging behaviour. No unrelated change is shown in the reviewed diff.

Full details: Title check

Explanation

The title states the main change: the hero's Browse buttons are now generated from ecosystems.toml instead of being maintained by hand. The raw summary and PR objectives confirm this. A new marker in pages/index.md is replaced by write_buttons in scripts/stage.py, with one button per live ecosystem in file order. The title is specific and matches the changeset and the linked issue #131.

Full details: Docstring Coverage

Explanation

Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 1 files. (1 skipped: 1 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

Finishing Touches: 💡 2
📝 Generate docstrings: 💡
  • Commit to this branch
  • Create a new PR
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@si618 si618 changed the title feat: generate the home page's Browse buttons from ecosystems.toml feat: generate the hero's Browse buttons from ecosystems.toml Oct 25, 2026
@si618
si618 merged commit 73997c2 into main Oct 25, 2026
7 of 8 checks passed
@si618
si618 deleted the feat/ecosystem-buttons branch October 25, 2026 00:07

This branch was successfully deployed

1 active deployment
preview — 873c081f Deployed Oct 24, 2026 by si618 via deploy / deploy #420
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.

feat: generate the home page's Browse buttons from ecosystems.toml

1 participant