Game

PixelQuest

A bold, screenshot-first landing page for an indie game.

Best for: Indie devs building wishlists before launch.

Outrun the grid. Rewrite the night.

Overview

PixelQuest gives a small game a launch page with presence. The neon 'Arcade' theme — deep space-black, magenta glow, a bold Syne display face — is made to be screenshotted and shared. The flow sells the game: a key-art hero, what makes it fun, a screenshot gallery, an honest build-in-the-open roadmap, one big player quote, and wishlist CTAs everywhere they matter. It ships the screens an indie actually needs after launch day too — a game detail page, a pre-order checkout, a devlog, and a small Playtester HQ where wishlisters manage their beta keys.

Who it's for

Indie game developersSmall studiosSolo game makersGame jam → commercial launches

Highlights

Cinematic key-art hero
Gameplay feature highlights
In-engine screenshot gallery
Build-in-the-open roadmap timeline
One oversized player quote + a wishlister FAQ
Playtester HQ — wishlist & beta-key screen
Wishlist CTAs throughout

Pages included

Home
Sign in
Sign up
Terms of Service
Privacy Policy
Game detail
Wishlist & pre-order
Playtester HQ
Devlog
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.

PixelQuest 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 35 minutes
Deploys to: Vercel · Netlify
Guides: 4 included
Support: Standard email support and optional setup help.

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

Game name & key artGameplay featuresScreenshotsRoadmap milestonesWishlist / store 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

Point the page at your real game

Point every 'Wishlist' button at your Steam app pageThe hero, sticky nav, and closing CTA all share one wishlist URL — set it once.
Swap the in-engine screenshots for your ownThe gallery and detail page read from the same list; keep them true (no bullshots).
Rewrite the roadmap so it matches your public buildWishlisters check this against your Discord — 'Now' should be what you're actually building.
Line up your beta-key drop with the Playtester HQ screenIf you promise 'wishlisters first', the HQ screen is where they'll expect to claim it.

Launch