Live data from Hacker News

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

primocms.org

61–70 of 122 posts

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

#61
post #22

Earlier quoted context omitted.

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.

There was never a time when WordPress was the only easy way for even a non-technical person to create a blog, they just did a great job marketing that that was the case. I spent a very brief time as a contributor to WP internals (not core by any means but a handful of contributions) and not only do you need a lot of internal knowledge to do anything outside of point-and-click, like you said, a lot of the core folks h…

I don't think it was even the marketing but the product placement. I remember in the 2000s if you wanted hosting that wasn't a dedicated server, the scene was dominated almost entirely by CPanel with a one click installer for Wordpress.

Once the plugin ecosystem sprung up around it, WP was off to the races.

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

#62
The drag-n-drop blocks/slices of content CMSes look cool in demos. As someone who has an in-house developed CMS editor just like this, it's a nightmare of constant updates. "Can we right align text and turn it blue?", "sure we'll add more and more props to each block". The actual content creators have a hard time using it effectively. So the results are almost always unsatisfactory. More training could possibly help but there's still a constant tradeoff between freedom and maintaining brand identity.

A headless CMS in our case would be a better approach. Simply provide the content and let a few professional folks code it up to match designs. Not everyone has that luxury I realize - so there's definitely a place for this type of CMS. I'm just pointing out how it can go horribly wrong.

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

#63
Great project. But honestly, I reached to the point of “less JS” or even no js is better for developers and also users. I’m currently migrating my old blog to a new one that gets generated by Zola [1], and even my main portfolio site, which funnily enough I newly made it with React/Gatsby, but I’m redoing it again with Zola because of the performance gap is just unmatched, not to mention I personally sometimes browse the web with js disabled so if a website is completely non-functional or doesn’t even load because of that is a deal breaker. My old site years ago used to use jquery and I was annoyed by it to some degree, trying react and the likes was a nightmare!

[1] https://www.getzola.org

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

#64
post #52

Sigh. I presume SSG = Static Site Generator (Does anyone actually try to write clearly for people who even slightly not keeping up with their specific domain? I do webdev and even I had to think for a moment to decode the acronym)

good point, shame I can't edit the title

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

#66

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.

Not sure if this is what you’re after but give https://getkirby.com/ a try

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

#67
post #5

Hey HN, it’s been about three years since you sent my open source CMS, Primo, to the front page ( https://news.ycombinator.com/item?id=23820201 ), inspiring me to quit my cushy remote job at the height of the pandemic to work on it full-time (naive and impulsive, I agree). Life has been pretty interesting since then. I’ve burned through my savings, lost my primo.af domain name to the Taliban, and convinced my wife to…

it's working for me :) i've been using primo for the last week to make my blog, and i feel more productive, and i've learned a lot. the forum is cool too. answers to a couple questions i had were already there. thank you for making primo.

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

#68
post #63

Great project. But honestly, I reached to the point of “less JS” or even no js is better for developers and also users. I’m currently migrating my old blog to a new one that gets generated by Zola [1], and even my main portfolio site, which funnily enough I newly made it with React/Gatsby, but I’m redoing it again with Zola because of the performance gap is just unmatched, not to mention I personally sometimes browse…

I agree! That's why Primo generates static HTML & CSS & only includes [vanilla] JS when its necessary to hydrate any interactive components. All using the Svelte compiler under the hood.

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

#69

As someone who has been working with WP since the beginning... Seems fun. Can you deploy it on a classic LAMP server? If not, it's not really a WP replacement for me. And I'm really looking for one.

Primo itself is a SvelteKit application, so I don't know how possible it would be to run it on a LAMP server, but you could certainly deploy the static sites it generates on one.

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

#70

The drag-n-drop blocks/slices of content CMSes look cool in demos. As someone who has an in-house developed CMS editor just like this, it's a nightmare of constant updates. "Can we right align text and turn it blue?", "sure we'll add more and more props to each block". The actual content creators have a hard time using it effectively. So the results are almost always unsatisfactory. More training could possibly help…

I definitely understand with the struggle to balance design freedom and brand identity (or good design). But wouldn't you still have the issue of content editors wanting to right align text and turn it blue regardless of the CMS you're using?
Post reply on HN