Live data from Hacker News

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

primocms.org

51–60 of 122 posts

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

#51
post #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.

sqlite or flat html files would enable the ease of self hosting without any third party external service dependencies

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

#53
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…

Would love to see this where blocks are standard web components and use native encapsulation!

I just tried it out with web components using Lit and it seems to work pretty well (https://i.imgur.com/PFvMgFp.png), allowing you to pass in on-page editable fields. But I'd be interested to hear where web components would work better than static/hydrated components.

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

#54
post #9

Earlier quoted context omitted.

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.

A plugin is a separate code module that wordpress loads, surely those are not bound to the wordpress core license. Extending wordpress with non-wordpress owned code does not grant them the right to push their license onto somebody else's completely unrelated code. If that were true, nobody would ever be able to sell a proprietary app on any linux distro. GitLab is open core yet extends the functionality with enterprise under a different, proprietary license.

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

#55
post #19

Earlier quoted context omitted.

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.

[dead]

Looks neat! Signed up.

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

#56
post #15

Huh nice. Looks like it uses Supabase as a backend.

Yup! Makes it super easy to spin up a server. We're working on making it backend-agnostic to open it up to more people, but Supabase has always been my go-to.

It would indeed, you clearly worked long, and hard on this as such I'd like to ask (since you've used Svelte). What is something you wish you knew earlier (a feature or an approach) with Svelte that you've found invaluable?

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

#59
post #45

Earlier quoted context omitted.

Totally understand the interpretation, but if you take a closer look I think you'll find Primo is actually the opposite. Site builders like Dreamweaver, Squarespace, Wix, Webflow, Weebly, etc. (and even WordPress now) replace code with visual controls - bridging the gap between users and their websites, but also putting up a wall that keeps them from modifying the code directly (or at best, applying some custom CSS o…

Primo is not the opposite. From the primo site, the 3 main bullet points - Drag-n-drop page building > Build your site's pages by dragging and dropping your directly blocks onto the page, unencumbered by overwhelming design options. - Visual content editing > Update your text, images, and links directly on the page or open up the Fields view to manage your content from a structured view. - Integrated development > Ac…

Ah yeah I forgot Dreamweaver does give you access to the code, in that regard it's similar. But, speaking as a user of Primo (and echoing what I've heard from a lot of other users), I haven't found anything that rides the line between no-code and code quite like this (especially open-source).

Yes Primo offers visual content editing and page building, because that's the only way to make a page flexibly editable by a non-technical user. Abstraction is only a negative thing when it stands in the way of what you want to do. Page building abstracts copy-pasting code. Visual content editing abstracts writing editorial content in HTML. Styling & building is the one thing that's left up to code because it has so many more possibilities than laying out blocks or writing content. So in the sense of building, Primo is the opposite to visual site builders like Webflow, Squarespace, Wix, etc.

I think that's why a new site builder pops up every other day - because they're all attacking the problem from different ends of the spectrum. Some give you more control, but are more complex/professional (like Webflow), while others are easier to use but offer less control (like Squarespace), and others are tailored to particular industries.

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

#60
post #17

Earlier quoted context omitted.

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.

sqlite or flat html files would enable the ease of self hosting without any third party external service dependencies

Possibly for the database but authentication and file storage would still need to be taken care of
Post reply on HN