You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Surface package registries in docs home
* Show package table with live versions on docs home and landing
The docs home only listed package names as bullets at the very bottom,
with no version info. Surface every gem and npm package prominently with
its current version.
- Render a single Package | Version | Registry | Description table on the
docs home, replacing the plain bulleted list (still before "Need more
help?").
- Versions come from live shields.io badges, so they stay current with no
manual updates.
- Add a Packages section to the landing page right after Quick Start.
- Introduce prototypes/docusaurus/src/data/packages.json as the single
source of truth shared by the docs-home transform and the landing page.
- Update prepare-docs tests for the table + badge output.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* Move package version badges from home page to footer
The full "Gems and npm packages" table was too heavy for the marketing
home page. Replace it with a slender, always-visible reference in the
site footer.
- Remove the PackagesSection (and its table CSS) from the landing page.
- Add a "Packages" column to the footer with one live shields.io version
badge per package, each labeled with both the name and registry
(e.g. "react_on_rails (gem) 16.6.0"), linking to its registry page.
- Footer badges are generated from the shared packages.json, the same
source as the docs-home Packages table, so the two never drift.
The detailed Package | Version | Registry | Description table stays on
the docs home, unchanged.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* Format footer packages as aligned name + version rows
The first footer pass rendered each package as one wide combined badge, so
the version pills landed at ragged, inconsistent positions and the longest
name overflowed the column.
- Split each row into a left-aligned monospace name (with a muted gem/npm
tag) and a right-aligned live version pill, so the pills line up in a
tidy column.
- Use flat-square shields badges for a cleaner look.
- Size the Packages footer column to its content so the longest name
(react-on-rails-pro-node-renderer) and its pill never clip and all pills
share one right edge.
Verified in light mode, dark mode, and mobile.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Production deployments require a paid license. See [Pro pricing and sign up](https://pro.reactonrails.com/) for current options. If your organization is budget-constrained, [contact us](mailto:justin@shakacode.com) about free or low-cost licenses.
0 commit comments