Which Website Do You Need: Builder, CMS, Shopify or Next.js

~14 min read

The technology a website is built on determines almost everything: what it costs now and a year from now, how fast it loads, how easy it is to change, and whether it can later be developed further or moved. You can change the technology later, but almost always that means building the site again from scratch. So you should choose at the very start and for your own task, not by fashion and not because your contractor is used to working with only one thing.

We will go from simple to complex: builders, then ready-made content management systems (CMS and CMF), then online shops (Shopify and WooCommerce), after that Next.js and server-side rendering, and finally the classic split into backend and frontend. We explain every term in plain words, and at the end we have put together a table: which situation calls for what.

Start with the task, not the technology

Websites come in different types, and each suits something different:

  • A business card site. A few pages: who you are, what you do, how to get in touch.
  • A site with a catalogue or a blog. Many pages of services, products and articles that need to be easy to add and change.
  • An online shop. Cart, payment, delivery, orders, stock.
  • A service or a site with a personal account. Booking, calculators, login by password, customer data, connections to other programs.

To choose, answer three questions:

  1. What should a visitor do on the site? Read and call, buy, book, or log in to an account? The more complex the action, the more serious the technology you need.
  2. Who will change the site, and how often? If it is you, every day, you need an understandable control panel. If it is once a year and through a contractor, the panel matters less.
  3. What will happen in two or three years? New languages, new services, a shop, an app, a connection to your accounting software. A site built only for today often hits a ceiling.

Builders: quick to launch, expensive to leave

A builder (Wix, Squarespace and the like) is a ready-made site that you assemble from blocks with a mouse, without programming. Hosting, domain and protection are already inside, and you pay one subscription. It is tempting: you can launch a site in an evening. But for a business that needs a site to find customers, this is most often a poor choice, and here is why:

  • The site does not belong to you. The site's code cannot be downloaded and moved to another host. If you want to leave, the site has to be built again. Texts and photos can be taken out, but not the design or the settings. And the more you have set up on it, the more expensive the move later.
  • A subscription for ever, and the price can rise. Stop paying and the site is gone. The functions you need are often available only on expensive plans, and you can't get rid of the builder's branding on your pages without a paid package.
  • Tight limits for SEO. You can't always set page addresses yourself, configure the files for search engines or fix technical details. For a small site that is enough, but in a competitive niche you will win only where the platform allows you to.
  • Speed is not in your hands. A builder adds a lot of its own service code to a page, and you can't remove it. Pages come out heavy, and a slow site loses customers, especially on phones.
  • Templates and limits in design. You draw only within what is provided. Your own logic (non-standard calculations, a link to a program you need) often can't be added there.

A builder is justified in narrow cases: testing an idea, making a temporary page or a personal project that you wouldn't mind forgetting. If the site must bring in customers and grow with your business, it is better to choose one of the options below right away.

CMS and CMF: a site that belongs to you

CMS (content management system) is a ready-made program that a site runs on, with a convenient panel where you change texts, photos and pages. The best known is WordPress. Unlike a builder, it is a program with open code: you can choose any host, move the site and change contractors.

How the site will look. With such a system, for example WordPress, there are two paths for design:

  • A ready-made template (theme). You buy a ready-made design and fill it with your own content. It is quicker and cheaper. The downsides: such a site looks like others, a template often carries a lot of unnecessary code that makes the site slower, and anything the author did not foresee has to be fitted in with extra work.
  • Design from scratch. A designer draws the site for your brand, and a layout developer turns it into pages, without unnecessary code. The site turns out unique, light and exactly suited to your tasks. The downsides: it costs more and takes longer, and some of the later edits also have to be made by a developer.

It is sensible to go by how important the site is: for a small site, a carefully set-up template is enough, and if the site must stand out and run fast, it is better to order a design from scratch.

When a CMS is a good choice:

  • A company site, a services site, a blog, a catalogue, a multilingual site with lots of text.
  • You want to change the content yourself without turning to a programmer.
  • You need standard functions (forms, search, a map, booking): there are ready-made add-ons (plugins) for these.
  • It is important not to depend on a single contractor: there are plenty of specialists for popular systems, and the site can be handed to someone else.

When it is not so good:

  • You need non-standard logic: complex calculations, different roles for staff and customers, personal accounts with a lot of rules. An attempt to squeeze that into an ordinary CMS ends with a clumsy system of dozens of plugins that get in each other's way.
  • Plugins are a frequent cause of hacks and slowdowns: the more of them there are, the harder it is to update the site and the sooner it starts to lag.
  • The site has to be updated regularly and watched, otherwise it becomes easy prey for hackers.

CMF (a framework for building a management system) is not a ready-made program but a set of building blocks (users, roles, pages, data) from which a developer assembles a system for your task. The difference is like that between ready-made furniture from a shop and a wardrobe made to measure for you. Examples are Symfony CMF and custom systems built on popular frameworks (Laravel, Django).

When a CMF is a good choice:

  • Your business has its own rules that can't be put together from ready-made plugins: your own calculations, your own order statuses, your own role model.
  • You need to connect the site to your internal programs (accounting, CRM, stock).
  • The site will grow and become more complex, and you don't want to run into the limits of a ready-made system.

When it is not so good:

  • For an ordinary site with texts and services it is unnecessary complexity: more expensive and slower than a ready-made CMS.
  • You depend heavily on the developer: the code is written for you, and a new contractor will take a long time to understand it. Insist on documentation and access to the code.

Online shop: Shopify or WooCommerce

For a shop you choose one of two solutions, and the difference between them is like the difference between renting a ready-made unit in a shopping centre and having your own premises.

Shopify is the rental of a ready-made platform for a shop. Hosting, cart, payment, protection and updates are already inside, and plans start from roughly 39 dollars a month*.

  • A quick start: a shop can be launched in a few days, without a programmer.
  • You don't need to look after the server, security and updates: the platform does it.
  • Costs are easy to predict: the monthly bill is clear.

The downsides: it is a rental for ever, and the shop is tied to the platform. Necessary functions are added through paid apps, and their subscriptions add up to quite a lot as you grow. If you take payments not through Shopify's built-in system, the platform takes up to 2% more of each sale. Page addresses are also rigidly set by the platform's rules and can't be changed.

How to improve Shopify's look. The look of a shop on Shopify's ready-made templates is limited, but there is a way out. Shopify can be used as a backend: it keeps storing products, orders and customers and taking payments, while the visual side (the frontend) is made separately, for example on Next.js. Then the design can be anything you like, and the site will open faster. Such a solution is more expensive and more complex: you need a developer, and you will pay both for Shopify and for hosting the storefront. It is justified if design and speed matter for your brand and your turnover allows you to spend on it.

WooCommerce is a free add-on (plugin) for WordPress that turns an ordinary site into a shop. The plugin itself costs nothing, but you pay for hosting, some add-ons, support and a developer's work.

  • Full control: you own the site and your customers' data and can move the shop to any host.
  • No commission from the platform itself on sales: you pay only the payment provider. The bigger the turnover, the better the deal.
  • A lot of flexibility: non-standard delivery and price conditions, a link to your own program, freedom in SEO, one site for articles and products.

The downsides: all the responsibility is on you. Security, performance, updates and backups have to be handled by you or through a contractor. A large catalogue needs a good server, otherwise the shop will be slow. A specialist is needed to launch it.

Who chooses what. Shopify suits you if you need to start selling quickly, you have few products and no wish to deal with the technical side. WooCommerce suits you if the shop is part of a large site with lots of text, you need non-standard conditions, and search visibility and independence from the platform matter in the long run. And what you should compare is not the price of a plan but the full bill for a year: apps, commissions, hosting, plugins and a specialist's work. At a small turnover the final difference is often small.

Next.js: when the site is assembled on the server side

First, what "rendering" means. It is the assembly of a page: data from the database and a template are turned into the finished view that is shown to a visitor. It can be done in three places, and the site's speed and its visibility in search depend on that:

  • In the visitor's browser. The site is first given an almost empty page and a program, and the browser assembles the page itself. This is slower on weak phones, and search engines sometimes find it harder to make sense of the content.
  • On the server for every request (SSR). The server assembles the page anew for each visitor and hands over the finished one. It suits cases where the data changes constantly or is different for everyone: a personal account, stock levels, prices in real time.
  • In advance, before the request (static generation, SSG). Pages are assembled once and sit ready, like printed leaflets. They open instantly. It suits pages that change rarely: services, articles, contacts. There is also an in-between option: the page is rebuilt on a schedule or when the content changes.

Next.js is a popular framework in JavaScript that can do all of these methods and lets you pick them for each page separately. A search engine gets ready-made text straight away, so such sites open quickly and are read well by robots. But note: ranking depends not only on the technology. A well-built site on any system gets found in search, and a badly built one on any system does not.

When Next.js is a good choice:

  • You need maximum speed and full control over the look.
  • The site is more than a set of pages: a personal account, a calculator, booking, a customer panel, product configuration.
  • The site will grow and connect to other systems.
  • You need pages for different countries and languages with carefully designed speed.

When it is not so good:

  • Next.js has no ready-made panel for editing texts. It has to be either built separately or connected to a content management system (more on that later, in the section about the split into backend and frontend).
  • You need a developer, and not only for the launch but for any further work. An edit that takes a minute in WordPress may here require a programmer's work.
  • Server-side rendering needs hosting designed for such sites.
  • For an ordinary business card site or a small catalogue it is excessive and more expensive than a ready-made CMS.

Backend and frontend: when a site is two parts

In the classic scheme, a site is split into two parts, like a restaurant:

  • The frontend is the dining room: what the visitor sees. Design, buttons, pages, animation.
  • The backend is the kitchen: what is hidden. The database, users, orders, payment, calculations, the rules of your business.

They talk to each other through an API, like a waiter. The dining room passes on the order, the kitchen cooks and hands back the result. The backend is written in a programming language such as PHP, Python or JavaScript, and the frontend in HTML and JavaScript. Ready-made sets of tools such as React or Next.js are also built in JavaScript and make working with it easier. Both parts can be changed separately.

How this relates to what we covered earlier. In ordinary WordPress, both your texts and the look live in one system. In a split scheme, WordPress or another CMS remains only as a panel for texts and a store of data (this option is called headless), and the look of the site is drawn by Next.js. This way you can combine a convenient panel for you with a fast site for the visitor.

When the split is justified:

  • Besides the site you need a mobile app or several sites: all of them can take data from one backend.
  • Complex business logic and many integrations: the backend becomes the foundation of the product, and the presentation can be changed without touching the data.
  • Several teams work on it: one does the design, another the logic, and they don't get in each other's way.
  • The load is growing: the parts can be strengthened separately.

When it is not so good: instead of one system you get two, which means more cost, more time and more maintenance work. You need a team that can work with both. For a business card site, a blog or a small shop it is almost always unnecessary: for the same money it is easier to make a good site on a CMS.

How to choose: situation and suitable technology

Everything we covered is gathered in one table:

Situation

What suits

Why

You need to test an idea in an evening or make a personal project

Builder

Quick and no developer needed. Not a pity to drop it if the idea doesn't work out

A company site, services, blog, catalogue, you change the texts yourself

CMS (for example, WordPress)

An understandable panel, many contractors, the site belongs to you

A shop, you need to start selling fast, few products

Shopify

A ready-made platform, protection and hosting inside, a clear monthly bill

A shop inside a large site, non-standard conditions and freedom in SEO needed

WooCommerce

Control, no platform commission, the data is yours

You need your own logic: calculations, roles, links to your programs

CMF or custom development

The system is built around your rules, not the other way round

You need maximum speed and freedom in design, the site is growing

Next.js (possibly with a CMS for edits)

Any wishes in design. Pages are assembled in advance or on the server and open fast

Besides the site you need an app, many integrations, a team is working

Backend + frontend

One set of data for all screens, parts change independently. The best solution for mobile apps

The main thing

A site is chosen not by fashion but by task: a builder for a quick start, a CMS for most company sites, Shopify or WooCommerce for a shop, Next.js and a split scheme for complex projects. The costliest mistake is to take something that is too simple or too complex and then redo everything from scratch. What it will cost to run a site after launch we covered in a separate article.

Want to understand which technology is right for you? Write to us: we will go through your task and suggest an option without unnecessary spending.

* Prices are approximate and may change: check platform plans on their own websites.

Hi! How can we help?

Usually reply within a few hours during business hours