Publish flow
Create a site, request upload URLs, upload files to R2, finalize the upload, and NanoPage updates D1, KV routing config, R2 manifest, and cache purge state.
The public docs stay intentionally compact while the MVP backend is moving quickly.
Create a site, request upload URLs, upload files to R2, finalize the upload, and NanoPage updates D1, KV routing config, R2 manifest, and cache purge state.
Plan limits are enforced in D1-backed control-plane APIs. Native Cloudflare rate limiting protects production API and serving traffic from bursts.
Serving requests write lightweight events to Analytics Engine. The dashboard reads per-site summaries and breakdowns through authenticated Worker APIs.
Keep product docs, pricing, and legal pages in this repo for versioned deploys. Use NanoPage itself for the public blog once the editable file-list workflow is stable for pro users; that lets us dogfood publishing without making legal or onboarding pages depend on dashboard content editing.