Earlier quoted context omitted.
Orthogonal. Many open source projects have companies behind them, that doesn’t restrict what you can do with the license.
That's true, but it does communicate something important to companies and individuals looking to use, contribute, or build on the project to say what kind of open source it is, rather than just saying its open-source IMO. Would be interested to hear if you think it could be clarified though.
Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
101–110 of 122 posts
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#102Earlier quoted context omitted.
That's true, but it does communicate something important to companies and individuals looking to use, contribute, or build on the project to say what kind of open source it is, rather than just saying its open-source IMO. Would be interested to hear if you think it could be clarified though.
Your answer completely sidesteps the question though and doesn't mention that it's open source, which makes it sound like it's not
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#103https://www.youtube.com/watch?v=B-ff53t8TuU&t=224s
Responsive designs got hot during that time (2010) and it made me shut down the project. But I still believe this is the way to go to build websites in the near future.
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#104The 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…
(or if you just have general feedback or learnings from your own experience, I'd love to hear that too!)
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#105I 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
#106The 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…
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#107Earlier quoted context omitted.
Not sure if this is what you’re after but give https://getkirby.com/ a try
That’s a bit more expensive than I’m open to for some random personal website.
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#108One of your themes shows an “email subscribe” field like one might expect for a blog with a newsletter. Does this have a concept of email subscribers and management related to such? Does this support transactional/batch emailing?
Ghost has this functionality and is used by many https://ghost.org/
Re: Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
#109Nice 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
#110Earlier 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…