Live data from Hacker News

Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

primocms.org

11–20 of 122 posts

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#11
post #9

Thank you for using an MIT license :)

Sure thing! Just changed it from AGPL actually. It would be ideal if anyone forking it would contribute changes, but I was worried that would keep them from using it to build internal tools or separate products, and all the underlying tech is MIT anyway.

Yep, that is actually a big problem (benefit?) with Wordpress, were all the code is redistributable because of the GPL license. So paid plugin developers are in this weird limbo were they are charging people for their plugins without telling them that the code is freely redistributable.

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#14
Nice project! I was a bit disappointed that you need a supabase account for "self hosting it".. And this is supposed to work only on some hosting service that can connect to Supa base, and also it encourages to fetch your pages content from github.. So it's more a CMS to run with specific service providers rather than something you can actually self host.

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#16

I wish there was something like this, but for serial dynamic content, like blog posts, reviews, etc. People are really attached to WP, but customization and themes are a nightmare.

I think people are attached to Wordpress for the same reason we are attached to Javascript. At the time, it was one of the only ways of easily creating a blog.

The problem with Wordpress is that once you need to do something outside of the norm then all of the sudden you need deep knowledge of Wordpress's inner workings.

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#17
post #14

Nice project! I was a bit disappointed that you need a supabase account for "self hosting it".. And this is supposed to work only on some hosting service that can connect to Supa base, and also it encourages to fetch your pages content from github.. So it's more a CMS to run with specific service providers rather than something you can actually self host.

Thanks! And yeah I agree it's a bit mislabeled; the goal was to enable people to put up their own server as easily as possible, which meant plugging into those services. We are working on decoupling the backend so you could self-self-host it though.

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#18

I wish there was something like this, but for serial dynamic content, like blog posts, reviews, etc. People are really attached to WP, but customization and themes are a nightmare.

That sounds like static content to me, what's wrong with just HTML?

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#19

I wish there was something like this, but for serial dynamic content, like blog posts, reviews, etc. People are really attached to WP, but customization and themes are a nightmare.

Definitely possible in the future, although to keep the project focused I'd imagine using a plugin or fetching that content from a separate CMS tailor-made for that kind of content would be ideal.

Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG

#20

I wish there was something like this, but for serial dynamic content, like blog posts, reviews, etc. People are really attached to WP, but customization and themes are a nightmare.

That sounds like static content to me, what's wrong with just HTML?

It's not really static. It grabs data from a database, or an API, and renders using entity-specific templates, both from a single entity perspective (post.php theme) and listing (search.php, index.php).

What I mean is: having something like Primo that allows visual management of such dynamic blocks and themes would be nice, so Editors can just play around with the result of their content calls (which the CMS handles transparently, doesn't matter if a SQL query or an API call).

Post reply on HN