feat(site): /deploy/render/ page + homepage surface (closes #42) - #44
Merged
Conversation
…ough Adds the public-facing Render self-host surface promised by #42 and the v0.6 deploy arc. Hero + Deploy-to-Render button, "what you get" framing, six numbered walkthrough steps (deploy → wait → open URL → first-boot wizard → install modules → connect Claude Code), custom-domain section, cost transparency, limitations, links onward to /install/ and the v0.6 design note. Voice and structure match install.njk — sectioned with "Why this step" / "What you should see" framing, code-inline blocks for commands, upgrade-callout for the "set PARACHUTE_HUB_ORIGIN once" caveat. Button links to render.com/deploy?repo=parachute-hub, which reads the render.yaml shipped in hub#258. Refs #42. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds a "One-click deploy to Render" entry to install.njk's "Running it somewhere other than your laptop" section. Lands directly above the Parachute Cloud waitlist and the BYO-VPS path — the natural place for people reading install docs to discover the always-on hosted path. Chose the install-page addition over a homepage hero modification: less disruptive to the landing page, and people who want one-click deploy are likely already on /install/ deciding which install shape they want. Refs #42. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Surgical addition to roadmap.njk's "Here now" list — surfaces the v0.6 Render self-host path as just-shipped, links to /deploy/render/ and the v0.6 architecture note. Bumps the "Updated" date. Refs #42. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds the 2026-05-18 v0.6 deploy architecture note to the design-notes index, on-site (the file builds to /design/.../ via design.11tydata.json). Drops the launch-window date framing now that we have a post-launch note. Adds a one-line clarification to the cloud-offering-sketch excerpt distinguishing it from the v0.6 self-host shape. Refs #42. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…nk Render pricing
Reviewer caught three drift points between the walkthrough and what the
hub wizard actually renders today. Two were copy-the-command-and-it-401s
class problems; one was a pricing claim we couldn't independently verify.
Fixes:
1. Wizard's MCP command does NOT include an auth header or token. The
wizard renders `claude mcp add --transport http parachute-${vault}
${hubOrigin}/vault/${vault}/mcp` and directs to /admin/tokens for
token mint. Rewrote step 6 as a two-step pattern: copy the wizard's
command, mint a token from /admin/tokens, re-run with --header. The
example block now shows both forms — bare first, then the full
Bearer-bearing form — in the order a visitor encounters them.
Updated step 4's "What you should see" to drop the "freshly minted
token" claim; says what the wizard actually does.
2. Done screen renders two tiles ("Open the admin UI" → /admin/vaults
and "Connect Claude Code (MCP)") — not direct Notes/Scribe install
links. Rewrote step 4's Done bullet to describe the actual tiles.
Updated step 5's intro to reflect the navigation path:
done → /admin/vaults → /admin/modules.
3. Hardcoded $0.25/GB disk pricing replaced with a link to
render.com/pricing — couldn't verify the per-GB number from public
sources, and pricing drift would silently break our page. Kept the
$7 Starter mention since that's well-documented. Updated the
expected-total line accordingly.
A hub follow-up (mint a token on the wizard done screen + direct
Notes/Scribe install buttons) would be better UX but lives outside this
site PR.
Refs #42.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
9 tasks
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.
Summary
Closes #42 — public-facing one-click deploy surface for the v0.6 Render self-host arc. Last item gating the v0.6 milestone per hub#257.
What's added
/deploy/render/page (deploy/render.njk→/deploy/render/). Voice + structure matchinstall.njk: sectioned with "Why this step" / "What you should see" framing,code-inlinefor commands,upgrade-calloutfor caveats. Sections in order:https://render.com/deploy?repo=https://github.com/ParachuteComputer/parachute-hub./parachute, modules installed at runtime via admin SPA. Links to the v0.6 architecture note./admin/modules→ connect Claude Code via theclaude mcp addline.PARACHUTE_HUB_ORIGINenv var, with anupgrade-calloutwarning not to churn the origin (invalidates issued OAuth tokens).Install-page surface (
install.njk). Added a "One-click deploy to Render" entry to the existing "Running it somewhere other than your laptop" section, directly above the Parachute Cloud waitlist and the BYO-VPS path. Chose this over a homepage hero modification — less disruptive, and people deciding which install shape they want are already on/install/. Brief explicitly left the choice open and noted this lean.Roadmap (
roadmap.njk). Surgical: added "v0.6 Render self-host (just shipped)" to the "Here now" list with links to/deploy/render/and the architecture note. Bumped the "Updated" date to 2026-05-20.Docs index (
docs.njk). Added the 2026-05-18 v0.6 deploy architecture note to the design-notes list — links on-site to/design/2026-05-18-v06-deploy-architecture/since the markdown file builds to that URL viadesign.11tydata.json. Dropped the "Written 2026-04-20 in the week before launch" framing now that there's a post-launch note in the list. One-line clarification on the cloud-sketch excerpt distinguishing it from the v0.6 self-host path.Build + smoke
npx @11ty/eleventy— clean, no warnings, 19 files written.npx @11ty/eleventy --servethen curled:/deploy/render/— 200, 17.7KB, all key terms present (deploy URL, render.yaml, deploy-to-render-button.svg, PARACHUTE_HUB_ORIGIN, admin/setup, hub-as-supervisor, Render Starter)./install/— 200, contains the new Deploy-to-Render entry./roadmap/— 200, contains the v0.6 Render self-host shipped line./docs/— 200, contains the v0.6 deploy architecture excerpt + link./design/2026-05-18-v06-deploy-architecture/— 200, on-site link from /docs/ + /deploy/render/ + roadmap all resolve..hero,.section,.code-inline,.upgrade-callout,.ctaprimitives. No new CSS introduced.Commits
feat(site): /deploy/render/ page — one-click Deploy to Render walkthroughfeat(site): surface /deploy/render/ from the install pagedocs(site): mark v0.6 Render self-host as shipped in the roadmapdocs(site): link v0.6 deploy architecture note from docs.njkPatterns check
Static-site docs PR. No code patterns touched. Voice and structure conform to
install.njk(Why this step / What you should see / numbered sections). Doc-only PR perfeedback_rc_versioning_dont_bump_patch— no rc bump, no version bump (site has no npm package).Test plan
/deploy/render/and visually confirm hero + deploy button render correctlyCloses #42. v0.6 milestone close — last item per hub#257.
🤖 Generated with Claude Code