Reorder the landing page and rebuild the feature grid around the platform - #121
Merged
Merged
Conversation
…he platform Page order. The provider table leads now, directly under the hero, followed by the feature grid. The community layer — forum topics, community profiles and the blog — moves to the bottom of the page, above the CTA: it is social proof for someone already interested, not the opening pitch. Bench highlights stays high, split out of that block. Feature grid. The six cards were /v1/*, lifecycle, dispatcher, probe, update and stacks — plumbing, and all six already appear in the "what 1.0 delivers" rows further down. They are replaced with what actually distinguishes the product: agents, the MCP tool catalog, memory, voice, image generation, and the fact that all of it comes up wired together. Heading and standfirst rewritten to match. The slot-lifecycle diagram moves up to sit under the provider table, where the engines it describes now live. Provider table. The version sat inline beside the provider name in a 140px column, which is what wrapped "Kokoro / Qwen3-TTS" across four lines. The name now stacks over its version, the endpoint list renders as chips instead of a run-on string, rows highlight on hover, and the columns are rebalanced. Agents section. "Meet Hermes" becomes "agents, tools + memory" and gains three tiles beneath the foil card: - hal0-brain, hal0's own resident operator — reachable from the dashboard's Agent Chat or `hal0 chat --brain`, with 147 of the 180 admin tools surfaced and 85 runnable under the shipped read-only default. - The MCP catalog, with the per-category tool counts and the approval floor: 54 destructive tools queue for a human, 9 of which no config can un-gate. - Memory, led on the property that matters — the engine runs embedded and loopback-only with local embeddings, so recall reaches no one. Removed the recommended-loadouts section and its now-dead data, CSS and tab script. Claims here were verified against the product repo first, and two drafts were corrected before they shipped: the memory card claimed graph retrieval, which the provider rejects at runtime (only vector mode is reachable), and the MCP card claimed hal0 composes your external MCP servers, which it cannot — it records and previews them, but there is no production wire-level client and start/stop is a 501 stub. Also: "what people are working on" → "what users are talking about", "shared configs" → "community profiles", and its heading → "optimized model & hardware recipes from the community". Dropped the gendered pronoun and "fully AFK" from the Hermes card's ability text. 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: |
e93c53c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0ca75ef2.hal0-web.pages.dev |
| Branch Preview URL: | https://site-1-0-page-order.hal0-web.pages.dev |
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.
Follow-up to #120, from a read-through of the live page.
Page order
Provider table leads, directly under the hero, then the feature grid. The community layer — forum topics, community profiles, blog — drops to the bottom of the page above the CTA; it's social proof for someone already interested, not the opening pitch. Bench highlights stays high, split out of that block.
Feature grid
The six cards were
/v1/*, lifecycle, dispatcher, probe, update, stacks — plumbing, and all six already appear in the "what 1.0 delivers" rows further down. Replaced with what actually distinguishes the product: agents, MCP, memory, voice, image generation, and the fact that it all comes up wired together. Heading and standfirst rewritten to match. The slot-lifecycle diagram moves up under the provider table, where the engines it describes now live.Provider table
The version string sat inline beside the provider name in a 140px column — that's what wrapped
Kokoro / Qwen3-TTSacross four lines. Name now stacks over version, endpoints render as chips instead of a run-on string, rows highlight on hover, columns rebalanced.Agents section
"Meet Hermes" becomes "agents, tools + memory" and gains three tiles under the foil card:
hal0 chat --brain. 147 of the 180 admin tools surfaced, 85 runnable under the shipped read-only default.Removed the recommended-loadouts section and its now-dead data, CSS and tab script.
Two claims corrected before they shipped
Both were in my own drafts, caught by verifying against the product repo:
_reject_moderaises for any mode other thanvector; theModeenum is unreachable from both MCP and REST, and there is no graph tool in the 26-tool catalog. Graph data is REST-admin-only.state="stopped", and start/stop/restart is a 501 stub.Related things the copy deliberately does not say, for whoever edits this next: the approval queue is not a security control (
approvals.py:47-48— the approve/deny endpoints are unauthenticated by design, LAN-only), it is in-memory and lost on restart, and the brain has no memory of its own despite its persona and system prompt implying otherwise.Also
what people are working on→what users are talking about;shared configs→community profiles; its heading →optimized model & hardware recipes from the community. Dropped the gendered pronoun and "fully AFK" from the Hermes card's ability text.Build green, 260/260 tests pass. Screenshotted at 1440px before and after.
🤖 Generated with Claude Code
https://claude.ai/code/session_014ey1mRLXy2ECVAiUbTqsuj