Managing a Next.js Site — Content via Headless CMS

<h2>How Headless CMS Works</h2><p>In Next.js, the frontend (the site) is separated from the backend (the content database). You edit content in a separate admin panel, and Next.js fetches it during build or live.</p><h3>3 Options</h3><h4>1. Sanity Studio (Recommended)</h4><ul><li>Free up to 100k API requests + 3 users</li><li>Fast admin panel with live preview</li><li>Schema-driven (we define what the client can fill in)</li><li>Real-time collaborative editing</li></ul><h4>2. Strapi (Self-Hosted)</h4><ul><li>100% free, runs on our servers</li><li>Fully open-source</li><li>Custom roles + permissions</li><li>For clients with data sovereignty requirements</li></ul><h4>3. IT Live CMS (for Simple Clients)</h4><ul><li>Our own lightweight CMS</li><li>Directly in your IT Live customer portal — no separate login</li><li>Limited to text + images + simple lists</li></ul><h3>Build & Deploy Flow</h3><ol><li>Client makes changes in CMS</li><li>Webhook trigger to our CI/CD</li><li>Next.js build starts (avg. 90 sec)</li><li>Static export uploaded to CDN</li><li>Client sees changes live in < 2 min</li></ol><h3>Rollback</h3><p>Each build is version-stamped. Rollback to previous version via 1 click in dashboard, deploy in 30 sec.</p>