3-6 Pal is a static, international-first activity library for grown-ups and children ages 3-6. It helps a caregiver choose a five-minute, low-prep activity using ordinary materials and a clear prompt.
The validation release intentionally has no accounts, payments, advertising, child profiles, or behavioral tracking. Bookmarks are stored only in the visitor's browser with localStorage.
- Next.js 16 App Router with TypeScript and React 19
- Static export (
output: "export") with unoptimized local images - Tailwind CSS 4 and project CSS in
src/app/globals.css - Lucide icons
- Cloudflare Workers Static Assets via Wrangler
The project uses pnpm. With Node.js 20+ available:
pnpm install
pnpm devOpen http://localhost:3000. To use the bundled workspace runtime on the development machine, prepend these directories to PATH:
$env:Path='C:\Users\Administrator\.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin;C:\Users\Administrator\.cache\codex-runtimes\codex-primary-runtime\dependencies\bin\fallback;'+$env:PathAll public activity content lives in src/data/activities.ts. Each activity has a stable slug, age range, duration, category, materials, skills, steps, grown-up tip, and optional safety note.
When adding an activity:
- Add a complete record to
activities.tswith a unique URL-safeslug. - Keep the activity safe for ages 3-6, low-prep, and usable without an account.
- Add or reuse a category icon in
src/components/category-icon.tsxif a new category is introduced. - Run the checks below. The sitemap and static detail route are generated from the data automatically.
pnpm lint
pnpm typecheck
pnpm build
pnpm deploy:drypnpm build creates the static site in out/. The current release generates the home page, activity library, private-in-browser Saved page, 30 activity detail pages, About, Privacy, a custom 404 page, robots.txt, and sitemap.xml.
For a local Cloudflare runtime preview after building:
pnpm previewThe production path is Cloudflare Workers Builds connected to this GitHub repository. Every push to the selected production branch runs the static export and then publishes out/ through the Worker configuration in wrangler.jsonc. This is a Worker with Static Assets, not a Pages project; it needs no server-side runtime, database, or application secret.
- Push this repository to GitHub (the repository can be private or public).
- In Cloudflare, open Workers & Pages > Create application > Workers > Connect to Git and select the GitHub repository. In an existing Worker, use Settings > Builds > Connect repository.
- Select the production branch (normally
main) and use these build settings:- Build command:
pnpm build - Deploy command:
pnpm deploy - Non-production branch deploy command:
pnpm exec wrangler versions upload - Root directory:
/(the repository root) - Build watch paths:
src/**,public/**,next.config.ts,package.json,pnpm-lock.yaml,wrangler.jsonc - Node.js version:
20or newer - Package manager:
pnpm
- Build command:
- Workers Builds runs the build command first.
pnpm buildcreatesout/; the deploy command runs Wrangler, which reads theassets.directoryvalue fromwrangler.jsoncand uploads the static assets to the Worker. - In Settings > Builds, select Connect and authorize the Cloudflare Workers & Pages GitHub App for
tonylate520/three-six-pal. Workers automatically creates a build token for the connected account. Do not commit an API token or put one in the repository. - In the Worker, open Settings > Domains & Routes and attach
36pal.comand, if needed,www.36pal.com. Keephttps://36pal.comas the preferred canonical host; redirectwwwto the apex host with a Worker route or Cloudflare redirect rule. - Verify HTTPS, the home page,
/activities/, one activity detail URL,/saved/,/robots.txt,/sitemap.xml, and a missing URL after the first successful build.
After the first connection, the Worker's Deployments tab should show a Build history entry for the GitHub commit. A deployment listed as Source: Upload is the manual Wrangler path and does not prove that GitHub Builds is connected yet.
The repository also includes the same deploy scripts for a manual Workers deployment when GitHub Builds are not being used:
pnpm build
pnpm deploy:dry
pnpm deployPush content or UI changes to the connected production branch. Cloudflare Workers Builds will install dependencies, run pnpm build, and publish the resulting out/ directory through wrangler deploy. Before pushing, run:
pnpm lint && pnpm typecheck && pnpm build && pnpm deploy:dryNo environment variables are required by the validation release. Do not add analytics, ad scripts, or child-identifying data without revisiting the privacy and product review.
src/app/ Routes, metadata, sitemap, and global styles
src/components/ Finder, library, cards, shared header/footer, actions
src/data/ Structured activity content and matching helpers
public/images/ Local editorial image assets
wrangler.jsonc Cloudflare Workers Static Assets configuration
- The domain-facing brand is written as 3-6 Pal in source and metadata so it remains clear in terminals and deployment tooling; the UI may use the typographic range mark where supported.
- The app is intentionally static. Adding personalization, accounts, or a CMS would change the hosting and privacy model and should be treated as a separate phase.