Add landing pages for all Next.js toolkit libraries#9
Conversation
Create individual landing pages for shutterbox, flagpost, ratelimit-next,
notifykit, croncall, vaultbox, and searchcraft — matching the gatehouse.sh
style with dark theme, cyan accents, code examples, and MCP badges.
Each site is a self-contained static HTML page under sites/{pkg}-site/
ready for deployment to {pkg}.sh domains.
https://claude.ai/code/session_01HJoBL8Nd56nYPq5Pth8df5
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 89e25e100e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <p class="tagline">SMS, email, push — one API. Swap providers, not code.</p> | ||
| <div class="install-box"> | ||
| <span class="dollar">$</span> | ||
| <code>npm install notifykit</code> |
There was a problem hiding this comment.
Use scoped notifykit package name in install instructions
This landing page tells users to run npm install notifykit, but the actual package name is @sathergate/notifykit (packages/notifykit/package.json:2, also mirrored in README.md:16). Following this command can install the wrong package (or fail), and the accompanying unscoped import examples will not resolve for consumers installing from npm.
Useful? React with 👍 / 👎.
| <pre>npx lockbox init | ||
| npx lockbox set DATABASE_URL "postgresql://user:pass@host/db" | ||
| npx lockbox set API_KEY "sk-secret" --env production</pre> |
There was a problem hiding this comment.
Replace lockbox CLI invocations with vaultbox command
The quick-start commands use npx lockbox ..., but this package exposes the CLI binary as vaultbox (packages/vaultbox/package.json:17-19). In practice, users following this page will run a different package or hit a command-not-found path, so the documented onboarding flow does not work.
Useful? React with 👍 / 👎.
| </div> | ||
| <div class="code-body"> | ||
| <pre># .secrets/*.json is safe to commit (encrypted) | ||
| # .lockbox-key is NEVER committed |
There was a problem hiding this comment.
Document the actual key filename generated by vaultbox
The safety guidance says .lockbox-key is the sensitive file, but the CLI uses .vaultbox-key (packages/vaultbox/src/cli.ts:45 and init adds that path to .gitignore). This mismatch can cause users to protect the wrong filename and accidentally commit the real encryption key material.
Useful? React with 👍 / 👎.
Summary
Added comprehensive landing pages for six Next.js toolkit libraries: notifykit, flagpost, searchcraft, croncall, shutterbox, and vaultbox. Each page includes hero sections, installation instructions, quick start guides, API documentation, and feature highlights.
Key Changes
Implementation Details
https://claude.ai/code/session_01HJoBL8Nd56nYPq5Pth8df5