Repository navigation
Add the Agentbox landing page - #56
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
A single static Astro page under site/, deployed on Vercel with site/ as the project root. It presents the install path, a real `agentbox info` transcript, the release manifest, the release flow, the default versus --workspace-only access boundary, and the command reference. Release facts are never hardcoded: the build reads the version served by the Homebrew tap, that release's provenance record, and release-inputs.json at its source commit, validating each, and falls back to a committed snapshot (and says so on the page) when any of that is unavailable. CI gains a site lane that type-checks and builds the page, and the Docker build context excludes site/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The hero settles in reading order (headline, lede, install, transcript) before the transcript plays, as one load sequence. - The release flow's track draws step by step as it scrolls into view and lands on Activate. Scroll-driven CSS, decoration only; the text never hides, and browsers without scroll timelines show it drawn. - The release seal swings on its hole when pointed at. - Outbound links carry an arrow that nudges on hover. - Smooth in-page scrolling. Everything is CSS on transform and opacity and is skipped under reduced motion. The scroll timeline uses longhands because minifiers fold `animation` + `animation-timeline` into a shorthand browsers reject. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zurfyx
force-pushed
the
site/landing-page
branch
from
October 27, 2026 16:55
6bc2976 to
cb3a2cc
Compare
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
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.
What
A landing page for Agentbox under
site/. It's a single static Astro page, deployed on Vercel. The Vercel projectagentboxis Git-linked to this repo with root directorysite. PRs get preview deployments, and merging tomainpublishes to production (currentlyagentbox-swart.vercel.app).The page covers:
brew trust+brew installcommands with a copy button, and the realagentbox infooutput from a fresh install.--workspace-only, followed by a plain "it isn't a sandbox" section, asAGENTS.mdanddocs/security.mdrequire.Every claim was checked against
README.mdanddocs/. Theinfotranscript keeps the exact formatlibexec/host.shprints. I confirmed it by running the real v0.1.34 release in a throwaway Homebrew-shaped prefix.Release data is never hardcoded
At build time,
site/src/lib/release.tsreads three sources:provenance.json,release-inputs.jsonat the release's source commit.None of these use the rate-limited GitHub API. Every field is validated. If any of it fails, the build uses
site/src/data/release-snapshot.jsonand the page says it's a snapshot, rather than breaking the build or claiming to be current.npm run snapshotrefreshes the snapshot.Design
I followed impeccable.style's guidance and avoided the usual dev-tool look. The concept is a container with a declared manifest:
Other changes
ci.yml: newsitelane (type-check and build) added torequired. Actions are pinned by SHA, per the static test..dockerignore: excludessite/from the runtime image's build context.AGENTS.md: the website joins the "keep in sync" list.The release archive is allowlist-based, and the shell lint and format checks don't match anything in
site/, so neither is affected.Verification
astro check: 0 errors. The build passes locally, on Vercel, and offline with forced network failure (falls back to the snapshot).npx impeccable detecton the built page: no findings.npm test: identical tomainon my Mac (the 13 failures there need Bash 5); CI is authoritative.Follow-ups (not in this PR)
release.ymlwould refresh it on every release. It needs a repo secret, so I left it out.agentbox.rovira.shneeds a CNAME in Cloudflare. After that, the Formulahomepageand README could link to the site.🤖 Generated with Claude Code