Getting Started with Fleet Studio v2
Prerequisites
- Node.js 20+
- npm / yarn / pnpm / bun
- Access to
TeamFleetStudio/fleetstudio-v2
Installation
Step 1: Clone
- HTTPS
- SSH
git clone https://github.com/TeamFleetStudio/fleetstudio-v2.git
cd fleetstudio-v2
git clone git@github.com:TeamFleetStudio/fleetstudio-v2.git
cd fleetstudio-v2
Step 2: Install dependencies
npm install
Step 3: Configure environment
NEXT_PUBLIC_SITE_URL=https://fleetstudio.fsgarage.in
Step 4: Run
npm run dev
Open http://localhost:3000.
Useful scripts
| Script | Purpose |
|---|---|
npm run dev | Local Next.js dev server |
npm run build | Static build - must succeed with all routes prerendered before calling a page change complete |
npm start | Serve the production build |
npm run lint | ESLint |
Verification
npm run buildcompletes with every route prerendered (no server-only code sneaking into a page)/sitemap.xmland/robots.txtreflectNEXT_PUBLIC_SITE_URL- Visually compare a rebuilt page against the legacy
fleet-studio-site-htmlequivalent - class names must match or styling breaks
Read AGENTS.md first
This repo has explicit, unusual constraints (no TypeScript, no client components on pages, no ad-hoc componentization, no dynamic state, static-only forms). Read AGENTS.md before making changes that would be normal in a typical Next.js app.
Troubleshooting
Issue: Styling looks broken after editing a page
- Solution: Class names must match the legacy CSS exactly - check
fleet-studio-site-htmlfor the original markup
Issue: Build fails on a page you added
- Solution: Confirm the page is a server component (no
"use client") and exportsmetadata