What's this good for?
- Brochure sites - Events, portfolios, landing page, small businesses, or any site that would benefit from quick development and simple content management is a dream in primo.
- Site Prototypes - Sometimes you just want to see what a design looks like when it's built. You can do that, then use the result as a starting point in your normal build system.
- Starting Points - Most big sites start as small sites. You can start your site in primo and when it gets too large, migrate it to a new framework/CMS.
- Design Systems - You can build and publish an entire design system from primo - both the interface and the actual components.
- Portfolios - Many developers still don't have portfolios because of the time involved in getting a site spun up. Well, now you have no excuse.
- "Publish and Forget" Sites - Since your site is static you can just publish it, renew your domain every year, and sip margaritas on a beach somewhere without worrying about it getting hacked by a chechnyan gambling site.
What isn't this good for?
primo's simple interface isn't made for editing and navigating a lot of data and content. There are much better options out there meant for creating large sites (NextJS, ElderJS, Hugo) and managing them (Strapi, Sanity).
- Not coding - you could certainly build a site in primo without seeing any code, but you'll have to be okay with using the components as they are. Or could you edit their code yourself (it's actually not too hard).
- High-value work - primo is considered stable but since it's only a year old, there are still a lot of things to iron and develop. Those with high demands and volatile projects should wait at least a few months for primo to mature.
- Sites with many collaborators - since there's no real-time collaboration and simultaneous edits get overwritten.
- Blogs - they're usually large, and there are many other options meant specifically for blogging and publishing (Ghost).
Can I use primo's IDE with another CMS?
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.
Can I use primo's CMS with another IDE/framework?
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. And the great thing about using it as a CMS is that you can use primo's IDE to build yourself a custom dashboard, if you're into that kind of thing.
My work is important. How do I know I can trust primo not to lose it?
Since primo's git-backed, the only data you could actually lose is anything you haven't saved yet. Since 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.
How do I know this won’t shut down in a few months, forcing me back into the Stone Age?
You will always have your full website in your repo. There's nothing primo-specific about it besides a couple classes labelled
primo. Since primo's open source, you could always keep using it in the self-hosted version. Either way, there's no reason to worry - primo has enough funding to continue full-time development for the foreseeable future.
Was this site built with primo?
It sure was!