automation
Next.js and Tailwind CSS Boilerplate for Burdlytics
A minimal boilerplate for building the Burdlytics site with Next.js, Tailwind CSS, and Cloudflare DNS integration.
Shipped January 2026
This is a minimal Next.js + Tailwind CSS boilerplate for the Burdlytics site:
- Landing page (
/) - Login page (
/login) - Dashboard stub (
/dashboard) - Cloudflare DNS update helper script (
scripts/update-cloudflare-dns.sh)
Quick start
-
Install dependencies:
npm install # or pnpm install # or yarn -
Run the dev server:
npm run devThen open http://localhost:3000 in your browser.
-
Deploy to Vercel:
- Push this repo to GitHub.
- Create a new project in Vercel and import the repo.
- Vercel will auto-detect Next.js and deploy.
-
Point
burdlytics.com(or a subdomain) to Vercel using Cloudflare DNS:- Get your Vercel-provided domain for this project (e.g.
burdlytics.vercel.app). - Use the helper script to create/update a CNAME via the Cloudflare API.
- Get your Vercel-provided domain for this project (e.g.
Cloudflare DNS helper
The script scripts/update-cloudflare-dns.sh uses the Cloudflare API to create or update
a CNAME that points a subdomain (e.g. app.burdlytics.com) to your Vercel domain.
You must set these environment variables before running it:
CLOUDFLARE_API_TOKEN– API token with DNS edit permissions for the zone.CLOUDFLARE_ZONE_ID– The Cloudflare Zone ID for your domain (e.g.burdlytics.com).CF_DNS_NAME– The DNS name you want to manage (e.g.app.burdlytics.com).CF_DNS_TARGET– The target CNAME, typically your Vercel domain (e.g.your-project.vercel.app).
Then run:
chmod +x scripts/update-cloudflare-dns.sh
./scripts/update-cloudflare-dns.sh
The script is idempotent: it will create the record if it doesn't exist or update it if it does.
Need more context?
Want help adapting this playbook?
Send me the constraints and I'll annotate the relevant docs, share risks I see, and outline the first sprint so the work keeps moving.