Skip to content

Add landing pages for all Next.js toolkit libraries#9

Merged
sathergate merged 1 commit into
mainfrom
claude/create-project-websites-zAGMY
Mar 30, 2026
Merged

Add landing pages for all Next.js toolkit libraries#9
sathergate merged 1 commit into
mainfrom
claude/create-project-websites-zAGMY

Conversation

@sathergate
Copy link
Copy Markdown
Owner

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

  • notifykit: Landing page for unified notification infrastructure (SMS, email, push)
  • flagpost: Landing page for feature flags and A/B testing
  • searchcraft: Landing page for full-text search with BM25 scoring
  • croncall: Landing page for serverless cron jobs
  • shutterbox: Landing page for image processing pipeline
  • vaultbox: Landing page for encrypted secrets management
  • ratelimit-next: Landing page for rate limiting utilities

Implementation Details

  • All pages use a consistent dark theme with cyan accent colors (#22d3ee)
  • Shared design system with CSS custom properties for colors, typography, and spacing
  • Each page includes:
    • Sticky navigation with product branding
    • Hero section with installation command and copy-to-clipboard functionality
    • Quick start steps with code examples
    • API exports table documenting available functions
    • Responsive design using CSS Grid and Flexbox
    • Syntax highlighting for code blocks
    • MCP (Model Context Protocol) badges where applicable
  • Pages are self-contained HTML files with embedded CSS and minimal JavaScript for interactivity

https://claude.ai/code/session_01HJoBL8Nd56nYPq5Pth8df5

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
@sathergate sathergate merged commit 781d11a into main Mar 30, 2026
8 of 9 checks passed
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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 &mdash; one API. Swap providers, not code.</p>
<div class="install-box">
<span class="dollar">$</span>
<code>npm install notifykit</code>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Comment on lines +453 to +455
<pre>npx lockbox init
npx lockbox set DATABASE_URL "postgresql://user:pass@host/db"
npx lockbox set API_KEY "sk-secret" --env production</pre>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants