This is a Next.js project bootstrapped with create-next-app.

Getting Started

Create your local environment file first:

cp .env.example .env.local

To enable feature flags with Flagsmith, set NEXT_PUBLIC_FLAGSMITH_ENVIRONMENT_ID in .env.local.

For rollout rules, naming, and cleanup steps, see docs/feature-flags.md. For agent-facing repository guidance, see docs/agents.md.

Helpful Docs

• docs/feature-flags.md - rollout rules and flag lifecycle
• docs/troubleshooting.md - common setup and runtime fixes
• CONTRIBUTING.md - workflow, checks, and PR guidance

Feature Flag Checklist

When adding a new flag:

1. Add the flag name to lib/featureFlags.ts.
2. Create the matching flag in Flagsmith.
3. Test it on your own account first.
4. Expand gradually and remove the flag after full rollout.

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun 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.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.