Give the use-case cards a header and section rhythm - #122
Merged
Merged
Conversation
The use-case row used to sit directly under the hero, which supplied both its spacing (padding was 4px 0 20px) and its context. Since the reorder it follows the feature grid, so it read as a second, unexplained row of cards separated from the first by a void. It now carries its own section header — eyebrow, title, standfirst — and uses the standard .section .section-tight rhythm like every other section, so the space between the two card rows reads as a section break rather than a layout bug. Also drops the last "graph memory" phrasing from the page: the meta description, the JSON-LD description, the SEO keywords, the RAG use-case card, the console section and the memory roadmap item. Retrieval is vector-only at runtime — the provider raises for any other mode and the Mode enum is unreachable from both MCP and REST — so "graph memory" reads as a retrieval claim the code refuses. The opt-in, per-agent-scoped and audited facts all stand and are unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ey1mRLXy2ECVAiUbTqsuj
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying hal0-web with
|
| Latest commit: |
726a2e6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://758f797d.hal0-web.pages.dev |
| Branch Preview URL: | https://site-usecases-spacing.hal0-web.pages.dev |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The use-case row used to sit directly under the hero, which supplied both its spacing (
padding: 4px 0 20px) and its context. Since the reorder in #121 it follows the feature grid, so it read as a second, unexplained row of cards separated from the first by a void.It now carries its own section header — eyebrow, title, standfirst — and uses the standard
.section .section-tightrhythm like every other section, so the space between the two card rows reads as a section break rather than a layout bug.Also drops the last "graph memory" phrasing from the page: meta description, JSON-LD description, SEO keywords, the RAG use-case card, the console section, and the memory roadmap item. Retrieval is vector-only at runtime —
_reject_moderaises for any other mode and theModeenum is unreachable from both MCP and REST — so "graph memory" reads as a retrieval claim the code refuses. The opt-in, per-agent-scoped and audited facts are unchanged, and the roadmap item gains the embedded/loopback-only detail.Build green, 260/260 tests pass. Verified the gap visually at 1440px before and after.
🤖 Generated with Claude Code
https://claude.ai/code/session_014ey1mRLXy2ECVAiUbTqsuj