Vivere Colorado LLC · Launch Point Racing · Internal — Eyes Only
Site Build Report & Forward Guide
What was built, where it lives, what actually works versus what's a placeholder, the DNS/domain path to a real address, and the comprehensive next-steps guide — one document to come back to, in the same format as the Ten Four report. Everything below is on preview URLs; no domain has been purchased, no DNS has changed, nothing is publicly launched.
8
Site pages, navigating
4
Social templates rendered
$0
Hosting cost (CF Pages)
0
DNS changes made
Bookmark
Launch mode (no billing yet)
01Executive Summary
The dashboard pilot is now a real, navigating website — eight pages under one design system, matching the media channel guide's skeleton exactly: the Race Day Dashboard as the front door, with News, Events, Tracks, Garage, Watch, Community, and Partners as first-class sections. Every nav link works; every page carries the pilot ribbon and honest "planned vs. real" labeling.
It launches in bookmark mode by design: no signup CTAs anywhere, because the account/billing layer (business plan §11) doesn't exist yet. The site's whole current job is to be worth bookmarking. Conversion switches on when auth + Stripe are built — no page will need redesigning for that, only CTA swaps.
Alongside the site: four production social-card templates (Dead-On, Pit Wall, Dial-In School cover, universal end-card) built as living HTML — the same headless-Chrome render pipeline used on other Vivere channels turns these into full-resolution post images, auto-filled from data.
The link to actually share — dedicated report domain
Same pattern as the Ten Four report: this document also lives on its own Cloudflare Pages project, separate from the working site, so it can be shared without exposing the pilot's raw file structure. → launch-point-report.pages.dev
All URLs are noindex, nofollow — invisible to search until launch is deliberate.
03Site Map & Navigation Model
/hub/ ← THE SITE (future launchpointracing.com root)
├── Dashboard — command strip + 5 expandable widgets; every widget deep-links to its section
│ Conditions → /app/ · Events → events · News → news · Gear → garage · Community → community
├── News — 6 planned Gate-1 articles (Dial-In School written versions = the SEO spine)
├── Events — regional calendar, one data source shared with the Pit Wall social cards
├── Tracks — CO ring live (Julesburg, Pueblo, Western Colorado + Bandimere marked closed), D5 next
├── Garage — 3 planned gear guides, affiliate disclosure written up front
├── Watch — all 6 series as a library, launch-gated by the media guide's backlog rule
├── Community — Discord-first plan, adult-only policy stated, illustrative channel previews
├── Partners — the 3-tier track offer (referral / site license / launch package), contact gated
└── Social renders — the 4 live card templates
Navigation rules baked in: sticky nav with active-page highlighting, identical footer everywhere, the app always one click away ("Open the App"), and every page reachable from every other page in one hop.
Wire to the app's existing weather source (same API the engine already uses)
Events & track data
Illustrative
One JSON data file, hand-maintained weekly at first (the Pit Wall workflow feeds it)
News articles
Titles only
Write the 6 Gate-1 articles (media guide backlog rule)
Racers-online / member counts
Illustrative
Real Discord + visit counts, post-launch
Geolocation ("nearest track")
Not built
Browser geolocation + track lat/long table — no account needed, good pre-Phase-2 win
Personalization (home track, tailored feed, followed threads)
Not built
Business plan Phase 2: auth → then this. The subscription's core value.
Accounts / subscriptions / payments
Not built
Business plan §11 — auth, Stripe, gating, lifecycle. The revenue gate.
Discord server
Not created
15 minutes to create; waits for channel launch so it doesn't open empty
05Social Render Pilots
Four templates live at /hub/social-renders, each shown with format specs and production notes:
Template
Format
Series it serves
Production path
Dead-On card — PREDICTED / RAN scoreboard
1080×1080
Dead-On (flagship) + future in-app share card
Auto-filled from run data · ~15 min turnaround
Pit Wall card — weekend preview/results
1080×1350
The Pit Wall (2×/week)
Auto-filled from the same events data file as the site
Dial-In School cover — question-as-thumbnail
1080×1920
Dial-In School (weekly)
Weekly batch block
Universal end-card — lights + line + QR
1920×1080 + 9:16
Every series
Static, QR added when domain exists
Why HTML templates and not one-off graphics
These are living templates: the established headless-Chrome pipeline screenshots them at full resolution with real data injected — the same system proven on other Vivere channels. Design once, render every week's cards automatically. The site and the feed share one design language because they literally share the code.
06Domain & DNS — The Full Path to a Real Address
Current state, stated plainly
The site lives at launch-point-racing.pages.dev (free Cloudflare Pages subdomain). No domain is owned, no DNS exists, and nothing here changes that — domain purchase is a you-action (§08). Below is the exact path for when you say go.
Step 1 — Choose and buy the domain (~$10–12/yr)
Checked 2026‑07‑22 via Verisign RDAP + DNS — not a guess
launchpointracing.com is unregistered and available. It matches the trademark filing ("LAUNCH POINT RACING") exactly, which strengthens both the brand and the mark. Confirm again at actual purchase time (registrations happen in real time and this can change), but as of this report, nothing is blocking it.
Buy through Cloudflare Registrar (at-cost pricing, no markup, and the domain lands in the same account as the Pages project — zero-friction connection). Registering a domain is account-level and takes ~5 minutes.
Buy the .com and nothing else for now — defensive TLD collecting can wait until revenue exists. (Fallbacks if the above somehow falls through by purchase time: launchpoint.racing, lpracing.app, launchpointhq.com.)
Step 2 — Connect it to Pages (~10 minutes, zero downtime)
Because the domain is on Cloudflare, the DNS records are created automatically (CNAME flattening to the Pages project) and SSL issues itself — typically live in minutes.
The .pages.dev URL keeps working forever as a fallback; all existing links survive.
Step 3 — The DNS records that will exist
Record
Name
Target
Purpose
CNAME
@ (apex)
launch-point-racing.pages.dev
The site (auto-created by Pages)
CNAME
www
launch-point-racing.pages.dev
www → same site
MX + TXT
@
Cloudflare Email Routing
hello@launchpointracing.com forwarding to your inbox — free, ~5 min setup, needed before the Partners page contact goes live
TXT
@
SPF/DKIM/DMARC
Added when real outbound email starts (newsletter/receipts) — not needed day one
Step 4 — Decisions that come with the domain
Root swap: promote /hub/ to the site root (the marketing one-pager either retires or moves to /about). Recommended: dashboard IS the homepage — that's the whole bookmark thesis.
App path: keep the engine at /app on the same domain (shares the Functions/D1 backend cleanly; no subdomain complexity until there's a reason).
Remove noindex only at deliberate launch (media guide Gate 2), never as a side effect.
Handles to match (media guide Gate 0): the domain and every social handle should be secured in the same week so the name is consistent everywhere.
07Next Steps — The Comprehensive Build Guide
One merged sequence across all four planning documents — each step names its source doc, so the details are always one click away.
Now — filings & foundations (owner actions, ~1 week)
The clock-driven items
File the provisional patent ($65) and trademark ($350–700) — everything is copy-paste ready in the filing packet
Buy the domain + reserve identical social handles everywhere (§06 here + media guide Gate 0)
Close the EIN / bank account / bookkeeping gaps (business plan §17)
Weeks 1–3 — make the pilot data real (site work, no auth needed)
From illustrative to live
Wire the dashboard weather widget to the app's existing weather source
Create the events/tracks JSON data file; hand-maintain weekly (this also powers Pit Wall cards)
Write the six Gate-1 articles (media guide backlog)
Add browser geolocation for "nearest track" — no account required
Full platform rhythm (Gate 3) → conversion mode when billing is live (Gate 4)
First track partnership pitch with real usage data (business plan Phase 4–5, ecosystem proposal §09)
February "pre-season tune-up" becomes the annual conversion tentpole
08Still Needed From You
Nothing below can be done for you — each is an owner decision or action, listed in priority order:
File the provisional + trademarkThe only items with real clocks. Packet is ready; ~45 minutes of portal time total.
Approve + buy the domainlaunchpointracing.com confirmed available (§06) — ~$10–12/yr on Cloudflare Registrar. Say the word and I'll walk the connection steps with you when it's purchased.
Approve the root swap/hub/ dashboard becomes the homepage; marketing page retires or moves to /about.
Answer the three channel questionsFace of the channel · named presenter or brand voice · who owns the 4–6 hrs/week. Every storyboard's VO plan depends on these.
Reserve social handlesFB/YT/IG/TikTok/X/Discord, same name everywhere, same week as the domain.
Commit the batchBusiness plan, filing packet, ecosystem proposal, media guide, hub site, social renders, this report — all uncommitted pending your review. One word commits them together.
One deploy publishes everything (site, app, docs, report) — the folder is a single Cloudflare Pages project with shared Functions/D1 backend. Local preview runs via the launch-point-hub launch config, so iterations don't burn deploys.
10Document Inventory
Document
Covers
Link
Master Business Plan & IP Record
The whole business in one place — product, filings, LLC, pricing, B2B models, risks, roadmap