Skip to content

fix(landing): bento tile, mobile nav, hero acronym, visual polish #499

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jackgranatowski merged 11 commits into from
Jul 3, 2026
Merged

fix(landing): bento tile, mobile nav, hero acronym, visual polish #499

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
f76bfdf
docs: rewrite README and landing page as first-contact copy
claude Jul 2, 2026
70adcd5
docs: move proposed README/landing copy to copy-wip for review
claude Jul 2, 2026
38e7ac2
fix: exclude copy-wip drafts from the GitHub Pages build
claude Jul 2, 2026
f1c6c8c
feat: rebuild landing page draft on the framework's own CSS
claude Jul 2, 2026
36c88d8
docs: surface the SLASHED acronym and philosophy in the marketing drafts
claude Jul 2, 2026
cd72069
feat: redesign landing draft around the manifesto hero
claude Jul 2, 2026
35bb8f2
fix: guard theme-toggle localStorage access on the landing draft
claude Jul 2, 2026
39d0ce0
feat: load the framework CSS from the jsDelivr CDN on the landing draft
claude Jul 2, 2026
d7f453a
fix: stabilise the hero hover and harden the dark band for mobile
claude Jul 2, 2026
60d14af
Merge remote-tracking branch 'origin/claude/bricks-builder-marketing-…
claude Jul 2, 2026
09026ce
fix(landing): fix bento tile, mobile nav, hero acronym; polish visuals
claude Jul 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions _config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ plugins:

exclude:
- node_modules
- copy-wip
- configurator
- configurator-archive
- core
Comment on lines 8 to 13

@qodo-code-review qodo-code-review Bot Jul 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Docs rewrite not published 🐞 Bug ≡ Correctness

This PR adds the rewritten landing page/README under copy-wip/ but also excludes copy-wip from
the Jekyll build, so the deployed Pages site will not include the new content. The published
homepage (index.md) therefore continues to ship stale facts (v0.6.19, 840 tokens, sixteen layers)
and the wrong npm package link.
Agent Prompt 
## Issue description
The PR adds updated “first-contact” copy as `copy-wip/github-pages-index.html` and `copy-wip/github-readme.md`, but `_config.yml` excludes `copy-wip` from the Jekyll build. The Pages deployment workflow builds the site via Jekyll using this config, so `copy-wip/` content will not be present in `_site/`.

As a result, `index.md` remains the deployed homepage and continues to contain stale/incorrect facts (token count, layer count, hardcoded release version, and the npm link).

## Issue Context
- GitHub Pages is built by `.github/workflows/deploy-configurator.yml` using `actions/jekyll-build-pages@v1`, which honors `_config.yml` exclusions.
- The new copy is currently only present under `copy-wip/`.

## Fix Focus Areas
- _config.yml[8-18]
- .github/workflows/deploy-configurator.yml[67-93]
- index.md[123-244]
- copy-wip/github-pages-index.html[1-40]
- copy-wip/github-readme.md[1-40]

## Suggested fix
- Move/port the rewritten landing page content into the actual published homepage (`index.md`), or otherwise update the Pages build so the new landing page is generated at `/`.
- Apply the rewritten README content to the repository’s actual `README.md` (or add an explicit build step that replaces it), instead of leaving it only in `copy-wip/`.
- If `copy-wip/` is intended to be published for review, remove it from `_config.yml` `exclude:` (or add an `include:`/copy step) and ensure the desired route is linked/served.

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

Expand Down
Loading