Website Software Guide 2026: CMS, Site Builders and Headless Architecture

Website software may look like a single product at first glance, but it actually covers five distinct families that differ from each other in fundamental ways: off-the-shelf CMSs (WordPress, Drupal, Joomla), cloud-based site builders (Wix, Squarespace, Webflow), headless CMSs (Strapi, Sanity, Contentful), static site generators (Hugo, Astro, Eleventy), and fully custom applications built from scratch (Next.js, Laravel, Django stacks). Choose the wrong family and you'll spend 40-60% of your project budget later on migration; choose the right one and you'll grow trouble-free for years. This guide is a long-term decision framework written for everyone from entrepreneurs shopping for the right platform, to writers setting up a personal blog, to IT directors running enterprise web projects — not a one-by-one product review. From a vendor-neutral angle, I'll share real tools, real configuration files and realistic cost ranges from every family (figures reflect 2026 market averages and vary by provider).

Related guides: What is a website — comprehensive guide · How to build a website · Website pricing 2026 · Hosting types · Software development processes · Website optimization A to Z

What Is Website Software, Exactly What Does It Do?

Behind the scenes, every website is produced by four software layers working together: a content management layer (where posts, images and page structures are stored), a render layer (the engine that turns content into HTML/CSS/JS), a data access layer (database, file system, third-party API calls), and a delivery layer (server, CDN, edge cache). "Website software" is software that bundles all four of these layers; it looks like a single product to the user, but architectural decisions have to be made for each layer separately.

WordPress is a monolithic example: all four layers run inside the same PHP process on the same server. In a modern Jamstack architecture, content lives in a headless CMS (such as Sanity or Contentful), rendering happens during a static build by Astro, data access is handled at runtime by serverless functions, and delivery is done via Cloudflare Pages or Netlify edge. The same end result is reached through different paths; performance, flexibility and cost are distributed differently across the layers.

The Five Software Families: A Quick Comparison

Before you start deciding, you need to know each family's basic parameters. The table below works as a first filter for any decision; figures are market averages and vary by provider.

• Off-the-shelf CMS (self-hosted): roughly $1-5 USD/month (hosting + domain), 1-4 hour setup, 80% flexibility, full code access, broad plugin ecosystem.
• Site Builder (SaaS): roughly $5-50 USD/month (depending on plan), 1-3 day setup, 30-50% flexibility, limited code access, hosting included.
• Headless CMS: roughly $0-100 USD/month (tier and traffic), 5-15 day setup, 95% flexibility, requires a JavaScript framework, frontend is separate.
• Static Site Generator: roughly $0-3 USD/month (CDN included), 2-7 day setup, 85% flexibility, content produced during build, lowest annual cost.
• Custom Software: initial build $3,000-60,000 USD+, 2-12 months development, 100% flexibility, requires ongoing maintenance, no scale ceiling.

Needs Analysis: Run It Through Five Questions

These five families represent five different operational models. Nothing is more pointless than custom software for a personal blog, and nothing is more inadequate than an off-the-shelf site builder for a corporate banking portal. The answer to the five questions below determines roughly 80% of which family you should start with. Answer them honestly — share them in writing among stakeholders, because verbal consensus collapses the moment a decision is made.

• 1. Traffic expectation: 1,000 — 50,000 — 5,000,000 monthly visitors? High traffic demands headless+CDN; for low traffic, a CMS is plenty.
• 2. Content production cadence: 1 post per week vs. 50 products per day vs. 10 user-generated submissions per second — each scenario calls for different software.
• 3. Technical team: 0 developers (no-code/site builder), 1 developer (CMS), 3+ developers (headless or custom).
• 4. Brand flexibility: Are you happy with a ready-made theme, or do you need a pixel-perfect design system?
• 5. Budget model: Fixed monthly SaaS, variable cloud cost, or one-shot large development project?

Based on your answers to these five questions, usually 1-2 families stand out. If you're still on the fence, our guide on choosing a web agency and website pricing articles offer detailed cost comparisons.

The Off-the-Shelf CMS Family: WordPress, Drupal, Joomla, Ghost

Content Management Systems (CMSs) are open-source software you can install on your own server, centralizing content production behind an admin panel. Roughly 43% of the web runs on WordPress (W3Techs data); Drupal is preferred in enterprise/government projects, Joomla powers mid-sized community sites, and Ghost is favored by publishers.

WordPress: The Default for Most Projects

WordPress was born as a blog engine in 2003; today it's used for full-scale e-commerce (WooCommerce), memberships (MemberPress), learning management systems (LearnDash) and even as a headless backend. You can download it from wordpress.org; wordpress.com is the SaaS version and is more limited.

The setup above is the manual, from-scratch method. On a hosting environment with a cPanel or Plesk panel, the same job is done in 30 seconds via an Auto-Installer (Softaculous). For an admin walkthrough, see our cPanel website management and Plesk panel management articles.

• Pro — Plugin ecosystem: 60,000+ free plugins (Yoast, Rank Math, WooCommerce, Elementor, WP Rocket, All in One WP Migration, etc.).
• Pro — Theme ecosystem: 12,000+ free themes, ready-made page builders (Elementor, Bricks, Beaver Builder, GeneratePress).
• Pro — Developer pool: WordPress freelancers number in the thousands worldwide; staffing is easy.
• Pro — SEO maturity: Plugins like Yoast and Rank Math handle advanced SEO (schema, sitemaps, redirects, breadcrumbs) with one click.
• Con — Performance is not the default: Without optimization, pages load in 3-7 seconds; make sure to read our website optimization and Core Web Vitals guides.
• Con — Security demands attention: The plugin attack surface is wide; sites are exposed to brute-force, SQLi and XSS attacks. Learn the basics with OWASP Top 10 2026.
• Con — Plugin chaos: With 30+ plugins installed, performance drops and conflicts begin.
• Con — Maintenance burden: Core, plugin and theme updates are your responsibility; ignore them and the site will be hacked within 1-2 years.

Drupal: The Quiet Giant Behind Enterprise and Government Projects

Drupal is technically a more advanced CMS than WordPress for multi-site, complex user roles, and multilingual enterprise structures. The U.S. White House site (whitehouse.gov, at one point), NASA, Tesla, Pfizer and many European governments run Drupal. Some ministry websites and large universities also rely on Drupal.

Drupal's learning curve is significantly steeper than WordPress's, but its type-safe content models (Field API), revision control, workflow modules and multilingual capabilities are far more mature. Overkill for small corporate projects, ideal for medium and large enterprise ones.

Joomla and Ghost: Niche Picks

Joomla was popular between 2005 and 2014; it still holds about 2% market share. It remains a stable choice for community sites, association portals and mid-sized multilingual websites. Ghost is a modern Node.js-based publishing/blog platform; it's easier to use than WordPress for subscription (newsletter) and membership business models. ghost.org offers both self-hosted and managed editions.

The Site Builder Family: Wix, Squarespace, Webflow, Shopify

Site builders are SaaS platforms that let you produce sites visually with drag-and-drop, no coding required. Hosting, certificates, security updates and CDN are included; the site keeps running as long as you pay the annual subscription. Target audience: small business owners, freelancer portfolios, event landing pages, boutique e-commerce.

Wix vs. Squarespace vs. Webflow

Wix offers 800+ ready templates, an AI-driven site generator (Wix ADI), the Wix Velo developer platform, restaurant reservations, online appointments and boutique store modules — making it one of the most comprehensive no-code options. Plans run roughly $10-50 USD/month, varying by provider, 2026 data. Squarespace offers fewer but higher-quality templates; it's considered a sector standard for photographers, artists, restaurants and event sites. The editor is more constrained than Wix's but produces consistent results; plans range from about $15-70 USD/month. Webflow is the platform design studios and agencies prefer — what sets it apart from other site builders is that the HTML/CSS it produces is clean and the code can be exported; CSS Grid, Flexbox and animations are controlled visually; plans run roughly $10-100 USD/month, with e-commerce plans on top.

Shopify: A Site Builder Specialized for E-commerce

Shopify is a SaaS platform exclusively focused on e-commerce. It hosts more than 4 million active stores; multi-channel selling (POS, Instagram, Amazon), inventory management, shipping integrations and payment infrastructure (Shopify Payments, iyzico, Stripe) all converge in a single dashboard. Plan range: Basic around $40 USD/month, Advanced around $400 USD/month, depending on provider, 2026 data. When making a strategic e-commerce decision, I recommend reading our E-commerce SEO guide and Website pricing 2026 articles.

The Three Hidden Costs of Site Builders

• Vendor lock-in: Content export from Wix or Squarespace is limited; themes, in-app purchases and custom code don't migrate.
• App marketplace cost: Add-on paid plugins for pop-ups, email, appointments and memberships — extra bills of $10-100 USD/month.
• Plan tier upgrade: As traffic or features grow, you're forced into the next plan up; CDN bandwidth, user count and product limits trigger unexpected jumps.

If your site is expected to live 5+ years, factor vendor lock-in cost into the equation now. Open-source CMSs and headless architectures provide long-term freedom.

Headless CMS: The Fastest-Growing Approach of 2020-2026

Headless CMS is an architecture that decouples content management from the frontend rendering layer. In a classic CMS, "WordPress both manages content and renders HTML through templates"; in the headless model, content sits behind an API (REST or GraphQL) and any frontend (React, Vue, Astro, mobile app, IoT device) can consume the same content.

• Multi-channel publishing: When the same content is consumed across web + mobile app + Apple TV + email, headless is ideal.
• High scale expectations: When forecasting 1M+ monthly visitors, edge cache + static build is critical.
• You have a development team: Ideal for teams building the frontend separately with Next.js / Astro / Nuxt and running code review.
• Advanced brand design: Design-system-driven projects that won't fit into theme constraints.
• Top-tier SEO + performance: When you're targeting 95+ Lighthouse scores via static rendering.

Leading Headless CMS Options

• Strapi: Open source, Node.js-based, self-hosted. Plugin ecosystem is growing. Roughly $0/month (on your own server) up to $50+/month (Cloud).
• Sanity: GROQ query language, real-time editor, structured content modeling. Generous free tier, scale tier is usage-based.
• Contentful: Enterprise-focused, the most mature GraphQL API. Limited free tier, team plans from roughly $100 USD/month.
• Storyblok: Visual preview + headless editing. Gaining traction among e-commerce players.
• Directus: Open source, builds a headless API on top of an existing SQL database. Ideal for migration projects.
• Payload CMS: TypeScript-first, Node.js-based, self-hosted. Trending among dev teams looking for a modern stack.

The catch with headless CMS: now you write the frontend yourself. The example below shows a Next.js page pulling content from Strapi; ISR (Incremental Static Regeneration) refreshes the content every 60 seconds — giving you static-grade speed for reads and dynamic control for management.

For details, see our Next.js 15 App Router guide; for the GraphQL alternative, see GraphQL vs REST.

Static Site Generators: Maximum Speed and Security

Static Site Generators (SSGs) are tools that turn every page into HTML/CSS/JS files at build time. PHP, Node or Python do not run on the server; only static files are served. The result: the world's fastest, safest and cheapest site architecture.

• Hugo: Written in Go, the fastest builder (10,000 pages in <5 seconds). Ideal for documentation portals, corporate blogs and multilingual sites.
• Astro: The most popular post-2022. Its "islands architecture" keeps JS to a minimum. Component-friendly (supports React, Vue, Svelte all together).
• Eleventy (11ty): Simple, JavaScript-based, flexible template engine choice (Liquid, Nunjucks, Handlebars).
• Jekyll: Written in Ruby, the GitHub Pages default. Old but still stable; sufficient for a simple blog.
• Next.js (static export): With output: 'export' it switches into static-site mode. Brings the React ecosystem with it.
• Gatsby: Rich plugin ecosystem with a GraphQL data layer; build times can be long for large sites.

Astro pulls content from src/content/blog/*.md files; you can write Markdown + frontmatter and version it with git. This setup is ideal for a developer-writer team: content via PRs, publishing flow protected by branch rules. For a detailed performance comparison, see our website optimization article.

• Pro — Performance: Pure HTML is being served; TTFB <50ms and LCP <1s become the norm.
• Pro — Security: Since no code runs on the server, the attack surface is non-existent outside of XSS.
• Pro — Cost: Free hosting is widely available on Cloudflare Pages, Netlify, GitHub Pages and Vercel.
• Limit — Dynamic content: Forms, search and user dashboards require separate serverless functions.
• Limit — Build time: At 10,000+ pages, even Hugo takes minutes; every content change triggers a rebuild.
• Limit — Editor experience: Writers who don't know Markdown need a headless CMS like Decap CMS, Tina or Sanity.

Custom Software: Building From Scratch

Custom software is the last resort when your needs are so specialized that no off-the-shelf CMS or SaaS can cover them. It's the typical pick for banking portals, multi-tenant SaaS, marketplaces, fintech and healthcare platforms. Common stacks: MERN (MongoDB + Express + React + Node.js), Laravel + Vue/Inertia, Django + Postgres + HTMX, Next.js + Prisma + Postgres, Ruby on Rails, Spring Boot + React. For details, see Node.js REST API development.

This code is just a starting point — a real custom product adds authentication (OAuth 2.0 and OIDC), authorization, validation, error handling, logging, tracing (OpenTelemetry distributed tracing), CI/CD (GitHub Actions) and tests (Jest unit testing).

The Cost of Custom Software — A Realistic View

• Discovery + design: 2-6 weeks, roughly $2,500-10,000 USD.
• MVP development: 3-6 months, roughly $8,000-50,000 USD.
• Pilot launch in broad strokes: live by the end of 6-12 months.
• Annual maintenance: 20-30% of the development budget (versions, security patches, performance tuning).
• Scalability: AWS/Azure/Hetzner bills run from $50 to $5,000 USD/month depending on monthly traffic.

These numbers are approximate market averages; the team's location (in-house, freelancer, agency, offshore) can swing the cost by up to 50%. When picking a development partner, I recommend reading our Software development processes guide.

Decision Matrix: Which Family Is Right for You?

The decision matrix below summarizes how each family fits various needs. Scale: ★ (not suitable), ★★★ (acceptable), ★★★★★ (perfect fit).

• Personal blog / portfolio: SSG ★★★★★ · WordPress ★★★★ · Site builder ★★★ · Headless ★★ · Custom ★
• Small business marketing site: WordPress ★★★★★ · Site builder ★★★★ · SSG ★★★ · Headless ★★ · Custom ★
• Mid-sized e-commerce (200-5,000 products): WooCommerce ★★★★ · Shopify ★★★★ · Headless commerce ★★★★ · Custom ★★
• Large e-commerce (5,000+ SKUs): Headless commerce ★★★★★ · Custom ★★★★ · Shopify Plus ★★★★ · WooCommerce ★★
• Enterprise / public-sector portal: Drupal ★★★★★ · Custom ★★★★ · WordPress ★★★ · Headless ★★★
• Publisher / news site: WordPress ★★★★★ · Headless ★★★★ · Ghost ★★★★ · Custom ★★
• Documentation / wiki / API docs: SSG (Hugo, Docusaurus) ★★★★★ · Headless ★★★ · Custom ★
• SaaS application: Custom ★★★★★ · Headless + custom auth ★★★ · Site builder ★
• Marketplace: Custom ★★★★★ · Shopify multi-vendor plugin ★★★ · WordPress ★★
• Single-page event landing: Site builder ★★★★★ · SSG ★★★★ · WordPress ★★★

Local Provider Landscape: Options in Turkey

In the Turkish market, website software providers fall into two categories: cloud-based SaaS site builders (international + local) and traditional firms offering hosting + CMS combinations. International SaaS players (Wix, Squarespace, Webflow, Shopify) still dominate; local providers (such as İdeasoft, Ticimax, Ethica, T-Soft) are particularly strong on the e-commerce side. In the hosting category, firms like Natro, Turhost, Hosting.com.tr, Radore and Doruk make WordPress installation easy on cPanel/Plesk. None of these companies are inherently good or bad; the right choice depends on your needs + team combination. For a hosting comparison, I recommend our Hosting types and pricing guide; for domain selection, our What is a domain name guide.

Architectural Decision Framework: 12 Critical Questions

Before turning the page, use a 12-question framework to clarify the needs side. Fill it out in writing; share a signed copy among stakeholders.

• 1. Site purpose: informational marketing, sales, community, SaaS product?
• 2. Primary conversion goal: form, purchase, signup, downloadable content?
• 3. Target traffic: year 1, year 3, year 5 forecast?
• 4. Content production rate: how many posts/products/pages per month?
• 5. Author/editor count: a single person, or a 10+-person newsroom?
• 6. Multilingual needs: single language, 2-3 languages, 10+ languages?
• 7. Design flexibility requirement: is a ready theme enough, or is a design system mandatory?
• 8. Integration needs: CRM, ERP, email automation, payment, analytics?
• 9. Compliance: KVKK, GDPR, PCI-DSS, sector-specific regulation?
• 10. Backup + disaster recovery: RPO/RTO tolerance?
• 11. Team capability: developer, devops, content editor distribution?
• 12. Exit strategy in 5 years: Is content export easy, is there lock-in risk?

Performance, Security and SEO Expectations

On an unoptimized install, each family's typical Lighthouse mobile score is different: SSG (Hugo, Astro, 11ty) 95-100, Webflow 75-90, Next.js + Vercel 85-95, Headless + Astro 90-100, Squarespace/Wix 65-85, default Shopify theme 60-80, optimized WordPress 80-95 (with LSCache + Cloudflare), vanilla WordPress 35-65 (not recommended). These numbers are based on field observation and vary by provider and content weight. Whichever you pick, treat performance optimization as one of the architecture's foundational decisions.

From an attack-surface standpoint, the families also differ significantly: SSG (no code on the server) > SaaS site builder (provider manages patches, but vendor compromise risk) > Headless (secure if the API layer is set up correctly, see REST API security guide) > Vanilla WordPress (broad plugin attack surface, weekly updates + WAF + 2FA are mandatory) > Custom (depends on the architect's expertise: most secure when set up correctly, most fragile when set up poorly). Security fundamentals: OWASP Top 10 2026, XSS and CSP, SQL injection prevention.

From an SEO standpoint, the rendering model is decisive: SSG/SSR pages are always safer (HTML arrives ready, all content is indexable on the first crawl); CSR (JS only) sites suffer from crawl delay, and content goes unindexed if JS errors. WordPress server-side renders with PHP; Webflow publishes in an SSG-like fashion; Wix/Squarespace are hybrid; for custom SPAs you must use SSR (Next.js, Nuxt, Remix) or a prerender strategy. SEO fundamentals: Search engines and SEO guide; technical checklist: Technical SEO 2026.

Choosing Software for Multilingual (i18n) and E-commerce

Multilingual needs can flip the architectural choice on its head. WPML and Polylang offer solutions on WordPress, but at a performance cost. On Drupal, i18n is integrated into the core — the most mature experience. On a headless CMS, content is modeled per language and you define the frontend routes yourself. On SSGs, Hugo and Astro provide built-in i18n support. For multilingual SEO, hreflang tags, canonical URLs and local keyword research are critical.

The E-commerce Side

E-commerce is the budget-burning category of website software selection. The wrong platform spawns a re-platform project within a year. Three options stand out: Shopify (5-5,000 products, fast time to market, $40-400 USD/month plan + transaction fee, 1-2 week setup); WooCommerce (WordPress + plugin, free core, hosting cost, scales from 1 to 50,000 products, requires a maintenance team); Headless commerce (Medusa, Saleor, commercetools — product and cart APIs in the back, frontend in Next.js/Astro, 5,000+ SKUs, multi-channel, ideal for B2B + B2C hybrids).

For e-commerce strategy, our E-commerce SEO guide helps you optimize category and product pages.

Data Modeling: Content Structure Lasts Forever

There's one decision that comes even before software selection: content types and fields. If types like "blog post", "product", "event", "article" and "author profile" don't have well-designed fields (title, slug, image, category, tag, relations, schema), you'll hit cascading problems no matter which platform you're on. The schema below maps directly onto Sanity, Strapi, Contentful or your own PostgreSQL tables. The key point: design the content model independently of the software — when you migrate someday, conversion becomes mechanical because your types and fields are already in a standard schema.

DevOps: CI/CD, Backups, Monitoring

After software goes live, nothing wears the team down faster than manual deploy and backup workflows. CI/CD and a backup strategy are inseparable parts of the architectural decision.

For details, see our CI/CD with GitHub Actions guide. For backup strategies, see Database backup strategies; for monitoring, see Server monitoring with Prometheus and Grafana.

Backups, Disaster Recovery and Migration

The most overlooked critical decision in website software selection is backups. SaaS site builders generally take backups automatically but limit data export; on CMSs, backup responsibility is yours; on SSGs, the git repo already serves as a backup. Apply the 3-2-1 backup rule across every software family: 3 copies, 2 different media, 1 offsite.

Migration: Fixing the Wrong Choice

After 6-24 months in, you may end up feeling "I picked the wrong family." Migration projects are tough but not impossible. Common paths: Wix → WordPress (content extraction script + URL map + 301 redirects), WordPress → Headless (keep the WP REST API as the backend, move the frontend to Next.js; all SEO is preserved), WordPress → Astro/SSG (pull content from WP REST API, convert to Markdown + static build), Custom → Headless CMS (data export → Sanity/Strapi import → frontend rebuild), Shopify → Headless commerce (move to Next.js+Medusa or Vendure via the Storefront API).

During migration, the most critical point is SEO continuity: every old URL must 301-redirect to its new counterpart, the sitemap must be updated, and a "Change of Address" must be filed in Search Console.

A Practical Decision Path: Three Scenarios

To make the decision concrete, let's walk through three realistic scenarios. Scenario 1 — Solo Educator / Personal Brand: Blog + e-book sales + email subscriber capture. Traffic: 200K per year. Team: a single person. Budget: under $50 USD/month. Recommendation: Ghost (Pro plan), or Astro + Buttondown + Stripe integration. Scenario 2 — Local Business / Grocery-Style E-commerce: 500 products, 3 staff entering products, no cash on delivery, with shipping integration. Traffic: 30-50K per month. Recommendation: WooCommerce (local hosting + Cloudflare CDN) or Shopify Basic. Scenario 3 — Enterprise / 50 Branches, Multilingual, B2B + B2C: Multilingual, branch info, corporate reports, press room, 5,000+ product catalog, B2B price list, KVKK-compliant form management. Traffic: 1M+ per month. Recommendation: Drupal, or headless commerce (Sanity/Contentful + Medusa/commercetools + Next.js).

Ten-Year Cost Comparison

Initial setup cost is not enough on its own to make the call. The 10-year total cost of ownership (TCO) tells the real story. The table below shows approximate figures for a medium-sized corporate site.

• WordPress + good hosting + team maintenance: ~$20,000 USD (10 years).
• Wix Business plan + extra plugins: ~$13,000 USD.
• Shopify Plus: ~$100,000 USD+ (transaction fees included).
• Headless (Sanity + Vercel + team): ~$80,000 USD.
• Custom software + DevOps: ~$170,000 USD+.
• SSG (Astro + Cloudflare Pages + team): ~$8,000 USD.

These figures are approximate market averages; depending on provider, team location and content production rate, they can vary by 50%, 2026 data.

Seven Common Mistakes

• 1. Trend-chasing: Setting up Sanity + Astro for a small blog "because headless is modern." Over-engineering.
• 2. Lock-in blindness: Picking a site builder without factoring in the cost of vendor lock-in.
• 3. Plugin-stacking habit: Loading 50+ plugins onto WordPress; performance and security tank.
• 4. Postponing backups: Saying "we'll set it up later," then waking up six months in to a hack or disk failure.
• 5. Leaving SEO until the end: Thinking about sitemaps, schema and redirects only after the software is chosen.
• 6. Skipping performance testing: Picking a theme, populating content, going live; Core Web Vitals come back red.
• 7. Starting without a migration plan: Not thinking about a 5-year exit scenario.

Edge Computing and Next-Generation Software Architectures

The rising trend of 2025-2026: dynamic sites running on the edge runtime. Tools like Cloudflare Workers, Vercel Edge Functions, Deno Deploy and Bun + Hono compute and ship content from the PoP closest to the user. Result: dynamic personalization at SSG speed.

The edge architecture looks like it will be the default of the next 5 years — especially for multilingual, multi-region and high-traffic sites. AI-assisted software (Wix ADI, Shopify Magic, Webflow AI, Framer, Durable, 10Web) gives you a good starting point but requires manual tuning on design system consistency, schema.org integration and long-term SEO.

Pre-Launch Final Checklist: 20 Items

• 1. Domain and DNS at the right provider; TTL lowered.
• 2. SSL certificate installed; verified for an A+ grade with our SSL check tool.
• 3. sitemap.xml generated, robots.txt accessible.
• 4. Search Console + Bing Webmaster Tools registered.
• 5. Analytics (GA4, Plausible or Matomo) installed.
• 6. KVKK/GDPR-compliant cookie banner + privacy policy in place.
• 7. 404 and 500 pages designed in line with the brand.
• 8. Lighthouse mobile score: 85+; LCP <2.5s, INP <200ms, CLS <0.1.
• 9. Images in WebP/AVIF; lazy loading enabled.
• 10. Backup cron scheduled; 14+ days of retention.
• 11. Monitoring (uptime + APM) integrated.
• 12. Form spam protection (hCaptcha or similar).
• 13. Schema.org JSON-LD (Organization, Article, Product, BreadcrumbList).
• 14. Open Graph + Twitter Card meta tags on every page.
• 15. Internal linking: at least 3 internal links per page.
• 16. Accessibility: alt text, labels, contrast, keyboard navigation.
• 17. 301 redirect table (if migrating from an old site).
• 18. Tested cross-browser (Chrome, Safari, Firefox, Edge) and on mobile devices.
• 19. CDN cache enabled; HTTP/2 or HTTP/3 turned on.
• 20. Emergency runbook: hack scenario, downtime scenario, contact list.

Conclusion: Choosing the Family Is Choosing the Right Match

At the start of this guide I said: "Choose the wrong family and you'll spend 40-60% of your project budget later on migration." Pick the right family with a decision matrix; invest in your team's capabilities and your growth forecast. Website software is not a static product; it's a living system that evolves over 5-10 years. The architectural decision is one you make today and live with for years. Each family represents a different balance point; there is no "best," only "the best fit for your scenario."

Resources and Related Articles

• wordpress.org/documentation — official WordPress documentation
• drupal.org/docs — official Drupal documentation
• docs.astro.build — Astro static site generator
• gohugo.io/documentation — Hugo SSG
• docs.strapi.io — Strapi headless CMS
• sanity.io/docs — Sanity headless CMS
• nextjs.org/docs — Next.js framework
• docs.medusajs.com — Medusa headless commerce
• w3techs.com — CMS market share statistics
• web.dev/learn — Google's official web platform training
• jamstack.org — Jamstack architecture guide
• What is a website? Comprehensive guide
• How to build a website
• Website pricing 2026
• Website optimization A to Z
• Software development processes
• Technical SEO checklist 2026
• SSL Certificate Check Tool