Restructure homepage and navigation for v0.6.16

[jackgranatowski]

Summary

Reorganized the homepage (index.md) and navigation (_layouts/default.html) to improve information architecture, add version visibility, and introduce the new Configurator v2 alongside the archived v1.

Changes

• Homepage restructure: Replaced brief tagline with expanded acronym definition (SLASHED = Standalone, Lean, Agnostic, Structured, Hybrid, Explicit, Deterministic) and added version badge with links to changelog, GitHub, and npm
• Navigation reorganization: Split documentation into logical sections:
  • Configurators (v2 and archived v1)
  • Demo & test pages (with individual test coverage pages now listed)
  • Installation (with bundle comparison table and CDN links)
  • Documentation (guides, reference, developer/meta sections)
  • Project files (changelog, contributing, configurator docs, CI status)
• Navigation update: Added "Configurator v1" link to header nav alongside new "Configurator v2" label
• Test coverage expansion: Added direct links to individual test coverage pages (colors, typography, layout, macros/states, forms/features, token reference)
• Bundle documentation: Added table explaining the four CDN bundle variants (optimal, optimal-components, optimal-utilities, full)
• Documentation expansion: Added new reference pages (Token Index, Classes, API Index, LLM Guide, Source Comment Policy) and reorganized existing docs into Guides, Reference, and Developer & meta categories

Notes

• Version number v0.6.16 is now visible on the homepage
• Configurator v1 is preserved as an archive link for users on older versions
• All new documentation links point to existing or planned pages
• No version number changes required (already at v0.6.16 in package.json)

https://claude.ai/code/session_01LLZRDVYEpvL5JFXbzACfLS

Summary by CodeRabbit

• New Features

  • Updated the homepage with a clearer headline and reorganized links into dedicated sections for configurators, demo/test pages, and documentation.
  • Added separate navigation links for Configurator v2 and Configurator v1 for easier access to both versions.

• Documentation

  • Expanded the homepage documentation area with clearer grouping for guides, reference material, developer notes, CDN bundles, and project files.

[coderabbitai]

Warning

Review limit reached

@jackgranatowski, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 41 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 867737f2-2796-4ead-938a-6e4063e9913e

📥 Commits

Reviewing files that changed from the base of the PR and between 6cad436 and 746d9dd.

📒 Files selected for processing (3)

• _config.yml
• _layouts/default.html
• index.md

📝 Walkthrough

Walkthrough

The home page now uses a new tagline and reorganized link sections for configurators, demos, documentation, and project resources. The site header also splits the configurator navigation into versioned v2 and v1 links.

Changes

Site links updates

Layer / File(s)	Summary
Homepage hero and link sections index.md	Replaces the intro and quick-links block with a hero tagline and separate configurator and demo/test link sections.
Homepage documentation sections index.md	Replaces the documentation list with CDN bundle entries, grouped docs subsections, and an expanded project files list.
Configurator nav links _layouts/default.html	Splits the configurator navbar entry into versioned v2 and v1 links with separate targets.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: restructuring the homepage and navigation for v0.6.16.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/slashed-hub-update-w70tez

---

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.}

[qodo-code-review]

PR Summary by Qodo

Restructure homepage and nav for v0.6.16 hub index
📝 Documentation ✨ Enhancement 🕐 20-40 Minutes

Description

• Rebuild homepage as a versioned hub index with grouped docs and project links.
• Split configurator navigation into v2 and archived v1 entry points.
• Expand install docs with CDN bundle variants and direct coverage page links.

Diagram

graph TD
  U([User]) --> S["Jekyll site"] --> L["Layout: default.html"] --> N["Header nav"]
  S --> H["Homepage: index.md"] --> IA["Hub sections"]
  N --> V2["Configurator v2"] --> P["Docs/pages"]
  N --> V1["Configurator v1 archive"]
  IA --> V2
  IA --> P

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Data-driven nav via Jekyll `_data` + includes

• ➕ Single source of truth for nav/hub links; fewer manual edits as docs grow
• ➕ Enables consistent ordering/grouping across header and homepage
• ➖ Adds indirection and a small amount of templating complexity
• ➖ May be overkill if link structure is still in flux

2. Use Jekyll collections for docs/demo/coverage discovery

• ➕ Automatic nav generation from frontmatter/collection metadata
• ➕ Reduces risk of broken/missing links as pages move or expand
• ➖ Requires refactoring docs into collections and maintaining metadata
• ➖ More structural change than this PR’s lightweight content reorg

Recommendation: The current explicit link tables are a good fit for a small, fast-moving docs IA refresh. If the number of hub links continues to grow (especially test-coverage subpages and reference indices), consider migrating link definitions into _data and rendering via includes to keep header and homepage navigation consistent and easier to maintain.

Files changed (2) +77 / -18

Documentation (2) +77 / -18

default.htmlSplit configurator header nav into v2 and archived v1 links +2/-1

Split configurator header nav into v2 and archived v1 links

• Renames the existing Configurator link to “Configurator v2” and adds a new header nav entry for the archived “Configurator v1” page. Keeps Demo/Coverage/GitHub links unchanged.

_layouts/default.html

index.mdRebuild homepage as a versioned hub with grouped docs, tools, and install info +75/-17

Rebuild homepage as a versioned hub with grouped docs, tools, and install info

• Replaces the short tagline/quick links with an expanded SLASHED acronym header and a visible v0.6.16 version line linking to changelog/GitHub/npm. Adds structured sections for Configurators, Demo & test coverage pages (including direct coverage subpages), install bundle variants table, reorganized documentation categories, and project file links.

index.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 5 rules

1. Broken configurator v1 link ✓ Resolved 🐞 Bug ≡ Correctness

Description

The new /configurator-archive/ links resolve to configurator-archive/index.html, which loads its
entry module from the site root ("/src/main.js"), so the app will fail to start when served under
/configurator-archive/. Additionally, the Pages deploy workflow only builds/injects configurator v2,
not configurator-archive, so the archive will be published as unbuilt source files.

Code

_layouts/default.html[R26-27]

+    <a href="/configurator/">Configurator v2</a>
+    <a href="/configurator-archive/">Configurator v1</a>

Relevance

⭐⭐⭐ High

They fix deploy/path breakages in Pages/docs (demo CSS link fix accepted; workflow staging work
shows sensitivity).

PR-#415
PR-#296
PR-#290

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The PR adds a new link to /configurator-archive/ in the global nav and homepage, but the archived
app’s index.html loads a root-absolute module (/src/main.js). The only main.js in that archive
is under configurator-archive/src/main.js, so serving the archive at /configurator-archive/ will
request a non-existent root path. The Pages deploy workflow also shows it injects only
configurator/dist into _site/configurator/ and has no build/copy step for
configurator-archive, meaning the archive won’t be deployed as a built SPA.

_layouts/default.html[24-31]
index.md[15-21]
configurator-archive/index.html[34-37]
configurator-archive/src/main.js[1-12]
.github/workflows/deploy-configurator.yml[3-10]
.github/workflows/deploy-configurator.yml[87-94]
_config.yml[8-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The site now links to `/configurator-archive/`, but `configurator-archive/index.html` is not a production build and references a root-absolute entry module (`/src/main.js`). When served under `/configurator-archive/`, the browser will request `https://<site>/src/main.js` (site root) instead of `/configurator-archive/src/main.js`, and the app won’t load.

## Issue Context
- The GitHub Pages workflow currently builds and injects only the v2 configurator output (`configurator/dist`) into `_site/configurator/`.
- `configurator-archive/` is not built/injected, so Pages will publish its raw source tree.

## Fix Focus Areas
- Build and inject the archived configurator during Pages deploy (mirroring the v2 steps), copying `configurator-archive/dist/.` into `_site/configurator-archive/`.
- Consider excluding `configurator-archive/` from Jekyll processing/copy (like `configurator/`) to avoid publishing the unbuilt source tree.
- If you don’t intend to publish a runnable archived app, change the new links to point to a stable external location (e.g., a tagged release, an artifact, or a GitHub tree), rather than `/configurator-archive/`.

### Fix Focus Areas (code pointers)
- .github/workflows/deploy-configurator.yml[64-94]
- _config.yml[8-16]
- configurator-archive/index.html[34-37]
- _layouts/default.html[24-28]
- index.md[15-21]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. index.md uses v0.6.16 ✓ Resolved 📘 Rule violation § Compliance

Description

The homepage now hard-codes Current version: **v0.6.16**, which does not match the root
package.json version string exactly (0.6.16). This can cause doc/version drift and violates the
requirement that documented versions match the root manifest exactly.

Code

index.md[11]

+Current version: **v0.6.16** · [Changelog](/CHANGELOG) · [GitHub](https://github.com/codeslash-dev/SLASHED) · [npm](https://www.npmjs.com/package/slashed)

Relevance

⭐⭐ Medium

Strong version-sync enforcement for manifests, but no prior evidence they require doc strings to
match exactly (no 'v').

PR-#365
PR-#55

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The compliance rule requires version strings in docs to match the root package.json version
exactly. The root version is 0.6.16, but the newly added homepage version string is v0.6.16,
which is not an exact match.

Rule 1353202: Keep version numbers consistent across package manifests, docs, and built CSS headers
package.json[4-4]
index.md[11-11]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`index.md` hard-codes a version string (`v0.6.16`) that does not exactly match the root `package.json` version (`0.6.16`). The compliance rule requires exact matches.

## Issue Context
Root `package.json` is the single source of truth for the version. Any doc-visible version string should match it exactly (no prefixes/suffixes) to prevent drift.

## Fix Focus Areas
- index.md[11-11]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---