Comparison
heyweb or a classic CMS?
A classic CMS can do almost anything. heyweb does one thing. Which one fits depends on the site and on who looks after it.
In shortA classic CMS such as WordPress runs on a server with a database and gives editors an admin panel for content, layout and plugins. heyweb hosts a finished static site and gives the client a chat that changes content only.
Side by side
Compared as ways of working, not as feature lists.
| Classic CMS | heyweb | |
|---|---|---|
| How the site is built | Themes, templates and plugins inside the CMS | Any way you like, usually with a coding agent |
| What runs in production | Server software and a database | Static files |
| What the client uses | An admin panel | A chat |
| What the client can change | Content, and often layout and settings, depending on roles | Content only |
| Ongoing maintenance | Updates for the system, themes and plugins | None for the site itself |
| Shops, logins, forms, plugins | A large ecosystem | Not available |
Which one fits
A classic CMS fits when
- The site needs a shop, bookings, member areas or other server features
- Editors publish often and need drafts, roles and workflows
- The client’s team already knows the system
- You rely on a specific plugin
heyweb fits when
- The site presents a business: pages, pictures, prices, team, contact
- The design was made to measure and should stay that way
- The client changes something a few times a month
- Nobody wants to maintain a server
Moving from one to the other
There is no import. A site on heyweb is built fresh, by you and your coding agent, and that is usually the reason to move: a new design without the weight of the old installation.
The client chat is in early access. Hosting, versions and undo work today. What that changes for monthly upkeep is in website care plans.