When a South Australian small business, not-for-profit or council plans a new website, the platform question comes up early: should it be WordPress, a custom-built site, or a modern framework such as Next.js with a headless CMS? Each option can produce a good website, and each can go wrong. The right choice depends on who will update the site, what it needs to do, how much maintenance you can take on and how important speed, security and accessibility are to you. This guide compares the main options in plain English.
The options at a glance
- Traditional WordPress: one system stores the content, runs the plugins and builds every page on the server when someone visits.
- Website builders and hosted platforms: services such as Squarespace, Wix and Shopify host the site for you, with a subscription and a set of templates and apps.
- Static or custom-built sites: pages are built ahead of time from code and served from a content delivery network (CDN). There is no database or admin login on the public site.
- Headless CMS with Next.js or Astro: editors use a separate content management system, and a modern framework turns that content into fast static pages. This is often called a headless or Jamstack approach.
Traditional WordPress
Strengths: familiar editing screens, a huge choice of themes and plugins, and many people who can work on it. It suits content-heavy sites where staff publish often and need lots of features without custom development.
Watch for: WordPress core, themes and plugins need regular updates, and out-of-date plugins are one of the most common ways small business sites are compromised. Heavy themes and page builders can make pages slow on phones, and accessibility depends on the theme and plugins chosen. Budget for ongoing care, and check who holds any premium licences.
Website builders and hosted platforms
Strengths: quick to start, hosting and security patches handled by the platform, and for online stores Shopify includes checkout, payments and stock management.
Watch for: you are limited to what the platform and its apps allow, monthly fees and app subscriptions continue for as long as the site runs, and moving away later can mean rebuilding. Check how well the templates perform on mobile and against WCAG 2.2 before you commit.
Static and custom-built sites
Strengths: very fast, because pages are prebuilt and served from a CDN close to the visitor. With no database or public admin login, there is far less to attack, and hosting on services such as Amazon S3 with CloudFront or Azure Static Web Apps is inexpensive. Full control over the code makes it easier to meet accessibility and Core Web Vitals targets.
Watch for: without a CMS, content changes need a developer, so this suits sites that change rarely or organisations happy to use a care plan for updates. Forms, search and payments are built as small separate services that need their own security.
Headless CMS with Next.js or Astro
Strengths: combines the speed and security of a static site with a friendly editing screen. Editors work in a CMS such as Sanity, Strapi or WordPress used headlessly, and the site rebuilds automatically when they publish. It handles larger sites, multiple content types and integrations well, and it suits organisations that care about performance, accessibility and long-term flexibility.
Watch for: it needs a developer who knows the framework, previews and publishing workflows have to be set up properly, and some CMS products charge per user or by usage. Make sure the code and content are in accounts your organisation owns.
Which is right for you?
- A small site that changes a few times a year: a static site with a care plan for updates is fast, secure and inexpensive to run.
- Staff publish news, events or resources every week: a headless CMS with a static front end, or a well-maintained WordPress site.
- Selling products online: Shopify or WooCommerce for most stores, or a headless storefront where speed and custom design matter more.
- Councils, agencies and not-for-profits with strict accessibility and security needs: a headless or static build gives the most control over WCAG 2.2 AA and the attack surface.
- A tight timeline with existing WordPress skills in the team: WordPress with a lightweight, accessible theme and a minimum of plugins.
Questions that matter more than the platform
- Will your organisation own the domain, hosting, code and content?
- Who will update the site, and how easy is the editing screen for them?
- How will security updates, backups and form tests be handled after launch?
- Will the site meet WCAG 2.2 AA and pass Core Web Vitals on a mid-range phone?
- If you are replacing a site, how will old URLs be redirected to protect your rankings?
Our guides to choosing a web designer in Adelaide, what affects the cost of a website and website speed and Core Web Vitals go further on each point.
How EITSAA can help
EITSAA is vendor neutral. We build static and headless sites with Next.js and Astro, and we work with WordPress, Sanity, Strapi and hosted platforms where they are the better fit. This website is a static Next.js site served from Amazon CloudFront, so you can test its speed yourself with PageSpeed Insights. Get a website quote or call 0402 401 584, and see our website design and development service.
Not sure where your current site stands? Request a complimentary website check: a no-obligation review of mobile layout, speed, accessibility basics and Google setup for South Australian businesses, not-for-profits and councils. Already have a written quote for a new site? See our price beat and its conditions.