WordPress vs Primo
WordPress is one of the most popular content management systems (CMS) in the world, with a large user base and a wealth of features. But its 20+ years of service has made it dated and bloated for many use-cases - particularly those best served by static sites - and its strategy of learning into the no-code movement (best seen by its recent Gutenberg editor) has left the web developers who use it struggling more than ever to use it as a professional tool.
Primo is a next-generation CMS aimed at web developers of all backgrounds that makes building, editing, and publishing websites easier and more streamlined than ever before.
Who they're for
One of the key differences between Primo and WordPress is that Primo is designed to be used by people who know how to code, while WordPress is more geared towards non-developers. This means that Primo may be more appealing to professional developers, entrepreneurs, marketers, and even weekend hackers, who want to have more control over their websites, and especially those intending to hand their websites off to non-technical editors.
Content Editing
Primo has arguably the simplest content editing experience of any CMS on the market. Component content is edited in an isolated context where changes can be instantly previewed on different devices (such as phones, tablets, laptops, and monitors), and editorial content is edited directly on the page. Non-technical content editors can be invited to collaborate on a Primo site and start editing, page building, and publishing changes with little to no training.
Development
Primo integrates a development environment directly into the CMS, which makes it possible to access and customize a site's code without having to set up a local development environment. Primo components are build with Svelte, a popular and approachable compiled language that builds on standard HTML, CSS, and JavaScript and makes it significantly easier to build interactive components. Combined, This makes it possible to preview component changes in realtime, which can save a lot of time and effort when making site edits.
Publishing
Primo builds websites as static sites, rather than generating them on-demand from a database like WordPress does. This means that Primo websites are faster and more secure, since there isn't a database or attached CMS for an attacker to target. Hosting a Primo site also significantly easier, since all you need to do is configure a web host (Vercel, Netlify, or GitHub) and click publish.
When to use WordPress
WordPress has a large and active user community which has contributed a wide range of plugins and themes that extend its functionality. This means that WordPress has a lot of features that may not be available in Primo without extra setup, like membership systems, forums, etc. If you need a CMS with a lot of features and a long track record, WordPress may be your best bet. Also note that, at the moment, only one person can edit a Primo site at a time.
When to use Primo
Primo is an approachable and streamlined CMS that is particularly well-suited to users who have at least a basic understanding of HTML and CSS and have simple content management needs. While it may not have as many features as WordPress, its focus on simplicity and speed make it a compelling alternative for those who want to build and manage their own websites while offering content editors a dead-simple editing experience.