The open web wouldn’t be what it is today without WordPress, but as freelancer it’s just too much. So I built primo - an alternative built on the best of the modern web that makes it radically simpler (fun even) to build fast, editable, scalable websites. I hope you enjoy it as much as I have.
Hit the ground running with primo's ready-to-use components or start from scratch. Manage your content yourself or invite collaborators. Deploy your site and rest easy.
Use primo's built-in components out of the box or modify them right from your browser. Build your own library using TailwindCSS and use your components across websites.
Primo can be used for a lot of things, but it really shines when used to create one-off websites (or brochure sites) because of how quickly it lets you go from zero to website, how easy it makes updating content, and how customizable it is for developers (i.e. get to the code).
At the moment, primo works best with websites with fewer than thirty pages. There are much better options out there meant for creating larger sites (NextJS, ElderJS, Hugo) and managing them (Strapi, Sanity).
Since primo's an entirely new platform, you'll also have to be okay with leaving behind any functionality that comes with other solutions (e.g. WordPress plugins) unless find a way to use them alongside primo.
It's possible but not recommended at this point since primo can't consume data from an external source (yet), so you'll have to integrate your content after it's built by using something like Github Actions. For example, to use a site built in primo with WordPress you could theoretically build the site with shortcodes embedded, then deploy those files to a separate WP repo.
You can use primo as a headless CMS since it, by default, publishes a static API. So you can consume your site both as a webpage or as a JSON object. The neat thing about using it just as a CMS is that you can use primo's IDE to build yourself a custom dashboard.
Since primo's git-backed, the only data you could actually lose is anything you haven't saved yet. But because it’s a web tool, there’s no sure guarantee that your unsaved work won't be lost (for example, if the app crashes and you're forced to refresh the page), especially at this stage of development. But every time you save your site a snapshot of it gets saved in your repo, so if you ever need to go back to an earlier version you can.
Primo is being worked on full-time by a small bootstrapped team. We've been working on it for a year and a half and have enough runway to sustain ourselves until at least 2022.
Primo is under active development with a full-time team, so we're moving fast. We'll never sell or abuse your email address, ever.