📚
Controlled documents
Publish canonical URLs at `www.wizwam.com/documents/archive/...` while preserving historical versions privately in R2.
- Public latest versions
- Private historical archive
- Manifest-driven browsing
New operating model
Build the public site around documents, systems, and delivery.
The old Pages upload is now archived locally. This repo is the new foundation for a business-facing site that can grow around your document archive, private apps workflow, and future delivery capabilities.
1 repo
Site, archive routes, and Pages deployment source
R2-backed
Canonical public documents with private version history
Git deploys
Previewable changes instead of manual direct uploads
Core capabilities
The rebuild should support how you actually work: controlled public information, private operational tooling, and room to expand the site without rebuilding the deployment model again.
⚙️
Private operating surface
`apps.wizwam.com` remains the authenticated dashboard for uploads, workflow control, and future admin functions.
- Authenticated uploads
- Background git push workflow
- Expandable internal tools
🚀
Git-backed public web
Move off direct uploads and treat the public site like a real product surface with commit history, previews, and predictable rollback.
- Preview deployments
- Commit-linked releases
- Single source of truth
Build-out roadmap
This structure is ready for real pages and content instead of another rebuild.
Projects
Case studies
Service pages
Featured docs
News and updates
Lead capture
The immediate next win is to connect Cloudflare Pages directly to this GitHub repo so every site change and every archive change follows the same deployment model.
Where to go next
Use the public site for the customer-facing story, the document archive for controlled resources, and the apps platform for the operational side.