Current quest · Shipyard
Launch Control
Release Candidate

Use the public launch checklist before sharing the site: production URL, Vercel settings, trust pages, and release docs.

Launch Control

This repo is ready for GitHub + Vercel public deployment.

Launch Control is the deployment room: SEO, trust pages, env variables, checklist, and safe public-release steps. After deploying, use the v15 Release Candidate page for the final smoke test.

1. Publish to GitHub

Unzip the project, add it in GitHub Desktop, commit everything, and publish the repository.

2. Import into Vercel

Create a new Vercel project from the GitHub repo. Framework should auto-detect as Next.js.

3. Set production URL

After first deploy, set NEXT_PUBLIC_SITE_URL to the final domain, then redeploy so metadata and sitemap use the right URL.

4. Launch publicly

Share the homepage, Deck Audit, Import Vault, and Card Atlas routes first. They are the strongest public entry points.

Launch checklist

Before you send the link into the wild.

v15 does not make the app depend on analytics, wallets, accounts, or a backend. It stays static, safe, and easy to deploy.
SEO preview

How the app introduces itself.

https://veyran-bible.vercel.app

Veyran Bible Tools

Retro pixel-MMORPG Veyran, Voice of Duality Commander tools for Bracket 4 value-storm decks with optional Bracket 5 spice, import/export, data validation, and release-candidate launch checks.

Share card

Social preview files included.

Open Graph
/og.svg
Canonical base
NEXT_PUBLIC_SITE_URL

The default image is a lightweight SVG so GitHub/Vercel builds stay simple. Replace /public/og.svg later if you want custom artwork.

What is already configured?

Next.js App Router
Tailwind responsive UI
Local JSON database
Data validation script
GitHub CI workflow
Vercel config
SEO metadata
Sitemap and robots
PWA manifest
Privacy page
Disclaimer page
Changelog page
Rule 0 warnings
No backend required
Important: the first Vercel URL will work immediately. For a clean public launch, set your final domain as NEXT_PUBLIC_SITE_URL, redeploy, then open /release and run the smoke-test checklist before posting the link everywhere.