Eastbase.
All kits

Devtool / OSS

OpenForge

A homepage that turns stars into contributors.

Best for: OSS maintainers who want a real homepage, not just a README.

driftkit

Type-safe forms that don't fight you.

Get started
Open live preview

Overview

OpenForge gives a serious open-source project a homepage to match. The light, technical 'Forge' theme keeps it credible, and the flow does what a good OSS landing page should: a clear one-liner, project stats, a copy-ready install, what it does, a code example, the humans behind it, and a friendly sponsor ask. Point it at your repo and ship.

Who it's for

OSS maintainersLibrary authorsGitHub project teamsDeveloper communities

Highlights

  • Project hero with repo stats
  • Copy-ready install command
  • Feature overview + code example
  • Interactive schema playground (edit + live output)
  • Contributors grid + public roadmap
  • Sponsor / star CTA

Pages included

  • Home
  • Sign in
  • Sign up
  • Terms of Service
  • Privacy Policy
  • Docs — getting started
  • Playground
  • Examples gallery
  • Releases
  • Themed 404 / 500 / loading

Built with

Next.js 16React 19Tailwind v4TypeScript

What you'll get

A launch kit is more than code. Here's exactly what's in the box and what it takes to get it live.

OpenForge Launch Kit

v1.0.0 · Single-project license

Coming soon

In the box

  • Next.js source codeThe complete, typed project — yours to keep and edit.
  • Content configEvery word, link, and price in one editable file.
  • Theme configColors, fonts, and shape as simple design tokens.
  • Auth screensThemed sign in & sign up — split layout, ready to wire up.
  • Legal starter pagesPractical Terms & Privacy you can customize, not legal advice.
  • 4 niche product screensDesigned for this kit — e.g. a dashboard, detail, or checkout.
  • Themed error & loading screensMatching 404, 500, and loading states — not generic fallbacks.
  • Guides + launch checklistCustomization, deployment, launch checklist, and troubleshooting.
  • DESIGN.md + AGENTS.mdSystem-design map + agent operating rules and starter prompts.
  • License + changelogPlain-language usage terms (placeholder) and version history.

To launch it

  • Difficulty: beginner
  • Setup time: About 30 minutes
  • Deploys to: Vercel · Netlify · GitHub Pages (static)
  • Guides: 4 included
  • Support: Self-serve, with the full guide set bundled in.
Request early access

Downloads open when checkout launches.

Customization & requirements

Everything renders from one config file, so editing copy, pricing, sections, or the theme is a data change — no component rewiring.

You'll need

Node 20+A code editorGitHub accountVercel account (free)

You can customize

Project name & taglineInstall command + code examplePlayground schema + startersRepo statsContributorsSponsor / docs links

Built for AI agents

Customizing with Claude, Cursor, or another agent is the intended path — the kit tells the agent what it may touch. Use the “Build it with AI” button in the sidebar for a ready-made starter prompt.

  • AGENTS.mdOperating rules, project map, starter prompts.
  • DESIGN.mdDesign system and theming contract — tokens only.
  • configThe safe editing zone: copy, links, pricing, and theme as data — AGENTS.md names the files.

Launch checklist

Every kit ships with a practical, step-by-step checklist so you know exactly what to change before you go live.

Launch checklist

19 steps

Make it yours

  • Replace the logo and favicon
  • Update your business / brand name
  • Rewrite the hero copy
  • Update services, features, and pricing
  • Set your real contact email
  • Swap placeholder images for your own

Metadata & SEO

  • Update the page title and description
  • Set your Open Graph share image
  • Point metadataBase at your real domain

Quality check

  • Test the responsive layout on mobile
  • Test every button and contact CTA
  • Run a quick Lighthouse pass

Make it your project

  • Point every link at your repoThe hero, navbar, CTA, and footer all share one GitHub URL — set brand.socials and the 'Star on GitHub' href once.
  • State your license and add a CONTRIBUTING.mdThe hero eyebrow and 'Truly open' feature both claim MIT — match your actual LICENSE, and link the contributing guide the CTA promises.
  • Swap the install command, code example, and playground schemaThe terminal block, the editor example, and the Playground screen all reference driftkit / useForm — change the package name in all three.
  • Wire self-host / docs links to real destinationsThe Docs nav item and the getting-started screen assume a docs site; point them at your README, wiki, or docs deploy.

Launch

  • Deploy to Vercel
  • Connect your custom domain
  • Do a final launch reviewOpen the live URL in a fresh browser

Ships with the kit as a Markdown checklist — tick it off as you go.

Related kits

Not quite it? Nearby on the shelf.

Browse the full gallery