feat: AWS Amplify build spec + deployment docs for docs.grith.ai#2
Merged
Conversation
Closes P1 #5 in ../grith/work/findings/launch-readiness-followup- 2026-05-18.md. The docs site source has existed for months but docs.grith.ai is not deployed anywhere (HTTP 000, DNS doesn't resolve). The audit flagged the missing deploy CI as the gating item; the user's preference is to host on AWS Amplify, matching grith.ai. amplify.yml at the repo root: single-app build spec (the docs site is a static Next.js export, no monorepo wrapper needed). preBuild sets Node 22 and runs `npm ci`; build runs `npm run build` which chains gen:llms → next build → gen:pagefind. baseDirectory is `out/` where Next emits the static tree and Pagefind appends its search index under out/pagefind/. No environment variables are needed — the docs site has no runtime secrets. README.md gains a "Deployment to docs.grith.ai" section with: - a table of the canonical Amplify settings, - one-time setup steps for the AWS Amplify console (connect GitHub, pick branch, confirm auto-detected build spec, add custom domain, point CNAME), - ongoing-operations notes (push-to-deploy on main, preview-build toggle, log location). Verified locally: - `python3 -c 'import yaml; yaml.safe_load(open(\"amplify.yml\"))'` parses. - `npm run build` succeeds end-to-end: 146 pages indexed by Pagefind, search index written to out/pagefind/. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Closes P1 #5 in
work/findings/launch-readiness-followup-2026-05-18.md. The docs site has existed for months butdocs.grith.aiis not deployed anywhere (HTTP 000, DNS doesn't resolve).Per your instruction, this wires up AWS Amplify (same provider as grith.ai). The PR is the code half —
amplify.yml+ setup docs. The console-side half (connecting the repo, adding the custom domain) is your ~5 minutes of clicking; the README walks through it step-by-step.What's in this PR
amplify.yml(new)Single-app build spec — grith-docs is a static Next.js export, not a monorepo wrapper. Mirrors the grith-website pattern minus the env-var injection (the docs site has no runtime secrets).
README.md— new "Deployment to docs.grith.ai" sectionmain, confirm auto-detected build spec, add custom domain, point CNAME, ACM provisions TLSVerified
python3 -c 'import yaml; yaml.safe_load(open("amplify.yml"))'parses.npm run buildend-to-end clean locally: 146 pages indexed by Pagefind, search index written toout/pagefind/.docs.grith.airesolves with valid TLS. Then we close P1 #5 in the audit followup.Your next steps (post-merge)
grith-aiorg (one-time).grith-ai/grith-docs, branchmain.amplify.yml.docs.grith.ai. Amplify gives you a CNAME target.docs.grith.ai.🤖 Generated with Claude Code