feat: surface blog posts higher on landing page (one approach — thoughts?)#20
feat: surface blog posts higher on landing page (one approach — thoughts?)#20planetf1 wants to merge 10 commits intogenerative-computing:mainfrom
Conversation
Feature strip (Unit/100%/Typed/Any) is redundant with the hero text and feature cards. Removing it saves vertical space near the top of the page. Blog section moved above "See it in action" so recent posts are visible before the code deep-dive, matching the issue generative-computing#19 proposal. Assisted-by: Claude Code
Blog grid now appears immediately after the hero section (before How it works), with the GitHub stats widget anchored below the cards — matching the intended layout from issue generative-computing#19. Assisted-by: Claude Code
- InstallCommand moved from hero to below GitHub stats in the blog section — visitors read content before seeing the install CTA - Hero padding reduced (6rem/5rem → 3.5rem/2.5rem) - Logo shrunk (max 420px → 280px, mobile 220px → 180px) - hero-subtitle margin-bottom cleared (nothing follows it in hero now) Assisted-by: Claude Code
- Drop 'From the blog' heading and 'All posts →' link — redundant with the Blog nav link in the header - Reduce top padding on blog section (4rem → 1.5rem) to close the gap between hero and first blog card - Add 1.5rem separator between blog grid and GitHub stats widget Assisted-by: Claude Code
Assisted-by: Claude Code
Remove 'Get Started' and 'Read the blog' buttons — both destinations are already reachable from the nav. Install command is now just the pill with version badge and copy button. Wrap InstallCommand in a block-level div with explicit margin-top to prevent the inline-flex line-height gap above it. Assisted-by: Claude Code
… padding useGitHubStats was not checking r.ok on the repo fetch — a 403 rate-limit response was parsed as JSON and repo.stargazers_count came back undefined, coercing to 0 via the ?? fallback. Now throws on non-ok so the error state is set and '—' is displayed. Also reduce blog section paddingBottom (4rem → 2rem) to close the grey space below the install command. Assisted-by: Claude Code
Standalone install pill below GitHub stats looked orphaned. Hero is the natural home for an install CTA — subtitle leads directly into it. Restore hero-subtitle margin-bottom to 1.5rem. Assisted-by: Claude Code
Move InstallCommand out of the hero into a two-tile row next to GitHubStats — both are developer-detail elements and belong together. Hero is now pure messaging: eyebrow + title + subtitle + logo. On mobile the row stacks vertically. Install tile matches the stats card border style and includes an 'Install' label for context. Assisted-by: Claude Code
planetf1
changed the title
- 'Get Started' CTA moved from hero to nav header — update selector
to page.getByRole('banner') scope
- GitHub stats moved out of hero — remove hero scoping from stats test
- Feature strip removed — delete feature strip test entirely
- 'From the blog' heading removed — drop that assertion from blog test
Assisted-by: Claude Code
|
Is the proposal that we do not have a separate news/highlight section, backed by dedicated content (e.g., 3 predefined md files, that when updated the highlights update), but instead move up the latest blog posts and make them the highlights? What if we want to call attention to an event, a new release, a new major capability... it'll be nice to have a way to call attention to things other than blogs. |
|
@serjikibm Correct - it's a simple proposal, partly as otherwise I wonder if we'll be wondering how to categorize what content. Alternatives could include
But it really came down to - they're all items we want someone to read. a new release? A reference to a third party post? something we write? Do you have specific examples where you think it is sufficiently different? |
|
I left comments on the issue, but I'll paraphrase here
|
I like these
it LGTM
I like the idea of moving the blog section up, but I think we leave the "header" in that specifys them as blog posts and links to the blog (I don't see it in the screenshot), maybe it should stay the way it is but just move above how it works
I like the idea, but the install card looks weird with the copiable command just in the middle of an empty card |
4 participants
What is this?
One approach to making the landing page feel less static and surfacing recent content earlier. Opening as a draft to get feedback on the layout choices before merging.
Changes
Questions
Screenshot
Closes #19