Design a custom CRF250L graphics kit and download a print-ready vector file
Translation pending
AI summary · revised during review
CommerceHTML · PythonGitHub @eoinmcgee1993OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗This is a Next.js project bootstrapped with v0.
The CRF250L/300L storefront customers actually use is plain HTML in
public/ — six pages, no build step, talking straight to Supabase. That is
the live site. The Next app around it is the rebuild, and it is not serving
anything customer-facing yet.
next.config.mjs holds beforeFiles rewrites so the storefront keeps the URLs
it already has: /, /apparel, /ecu, /mods, /approve, /desk. The /
rewrite is what stops app/page.tsx taking the home page.
To cut a page over: build it in the app router, remove its entry from
STATIC_PAGES in next.config.mjs, and delete its file from public/. One
page at a time — nothing else has to move and the other five keep working.
Two things to know before touching the storefront pages:
/approve links are handed to customers and are the only way back to an
approval page. approve.html must keep answering at both /approve and
/approve.html until every outstanding order is finished.SELECT grant for anon. The browser may INSERT and
nothing else; reads belong in a Supabase Edge Function under the service-role
key. Architecture notes are in the Content-creation- repo under docs/crf/.The legal pages (privacy.html, terms.html) are deliberately not here.
They are unfinished, and are kept outside any publish root so no host can serve
them by accident — see docs/crf/legal-drafts/ in that same repo.
This repository is linked to a v0 project. You can continue developing by visiting the link below -- start new chats to make changes, and v0 will push commits directly to this repo. Every merge to main will automatically deploy.
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
To learn more, take a look at the following resources: