CMS

A Content Management System lets non-technical users create, edit, and publish content on a website without touching code. WordPress, Strapi, and Sanity are common examples. A CMS separates the content from the design, so writers and marketers can update pages independently while the site structure stays intact.

Picture a restaurant owner who changes the menu every season. Without a CMS, every price change means emailing a developer and waiting. With one, they log into a simple dashboard, edit the text in a form, hit publish, and the site updates in minutes. That is the entire pitch: routine content changes stop being developer work.

Why it matters for your project: be honest about how often your content will actually change. If you plan to publish blog posts weekly or update product listings constantly, a CMS pays for itself fast. If your site is five pages that change twice a year, a CMS adds cost, hosting complexity, and security maintenance for little benefit — a static build with occasional developer edits is often the smarter buy. Deciding this early shapes the whole quote.

The CMS also interacts with how your site is built and served. Content from a CMS can be baked into static pages at publish time (static site generation) or rendered fresh on each visit (server-side rendering). Modern "headless" CMS setups pair an editing dashboard with a fast custom front end — a common combination when speed and editorial freedom both matter.