Skip to content

feat(web): /launch landing page - #15

Closed
Codehagen wants to merge 1 commit into
mainfrom
feat/launch-landing
Closed

Codehagen wants to merge 1 commit into
mainfrom
feat/launch-landing

Conversation

@Codehagen

Copy link
Copy Markdown
Owner

Summary

One-page YC-style marketing landing at helpbase.dev/launch. Built for sharing in outbound DMs and posts where the current docs-index hero (helpbase.dev/) is too dense.

  • Hero: one-liner ("Docs your AI agent can actually use.") + install command + demo CTA
  • Three pillars: code-grounded · agent-native · you own it
  • Three-step flow: create-helpbase → ingest → deploy
  • Built-on row (shadcn/Next/MCP) with a helpbase add card callout
  • Closing CTA + GitHub star link

Additive route. Doesn't touch /. Reuses the grid + radial-gradient hero treatment from the existing docs index so it visually belongs.

Test plan

  • pnpm --filter web typecheck — clean
  • Preview deploy: verify hero renders, command boxes scannable, mobile stack looks right
  • Dark mode: gradient + card borders readable

🤖 Generated with Claude Code

One-page marketing landing at helpbase.dev/launch. Additive route, doesn't
touch the existing docs index at /. Use this URL for outbound DMs and
social posts where the docs-index hero is too information-dense.

Layout: hero with one-liner + install command + demo CTA, three-pillar
"why it exists" (code-grounded / agent-native / you own it), three-step
"how it works" (create-helpbase → ingest → deploy), built-on row
(shadcn/Next/MCP) with a `helpbase add card` callout, closing CTA. Reuses
the existing grid + radial-gradient hero treatment so it visually belongs
in the rest of the site.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
helpbase Ready Ready Preview, Comment Apr 19, 2026 8:41am

Request Review

@coderabbitai

coderabbitai Bot commented Apr 19, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@Codehagen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 10 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 10 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ff79db01-e8d0-4ddf-932b-93186322998b

📥 Commits

Reviewing files that changed from the base of the PR and between 9a1b9c3 and c58d573.

📒 Files selected for processing (1)
  • apps/web/app/(main)/launch/page.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/launch-landing

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Codehagen Codehagen closed this Apr 19, 2026
@Codehagen
Codehagen deleted the feat/launch-landing branch April 19, 2026 08:45

This branch was successfully deployed

1 active deployment
Preview — c58d573b Deployed Apr 19, 2026 by vercel[bot]
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.

1 participant