21–30 of 85 posts
Looks like it uses Postgres: https://github.com/michael/editable-website
I found that useful when i worked with https://www.getlektor.com/ years ago. In lektor the dynamic part runs on a users desktop machine, but it of course wouldn't need to.
SvelteKit is such a breath of fresh air, glad to see it used on this.
It really is - writing a svelte component feels like writing something in vanilla html/js/css, but you get all the advantages that come with a framework.
TypeScript support can be hit or miss, and there could be more improvements around the stores API
Cool idea, and I really like how the site still functions for readers with JS disabled, which is (as far as I'm aware) uncommon for this sort of thing. One thing that isn't clear from reading the GitHub page — do all visitors end up downloading the editor payload or do only admins who are logged in get that?
My general approach to this is considering website development as "minimal web app development". Think of it as developing your very own little Facebook thingie, where people could log in and post and edit stuff, without thinking about the technicalities.
My feeling is that, thanks to abstractions like Svelte, this is not super difficult anymore and my hope is that in many cases this approach could replace integrating a CMS. At least for me it feels much more natural like this, and really all I have to know is some HTML+CSS, the SvelteKit API and SQL to model my content. Just like in the old days, where you didn't have to depend on 100 things to make a website. :)
Earlier quoted context omitted.
It really is - writing a svelte component feels like writing something in vanilla html/js/css, but you get all the advantages that come with a framework.
I just can't get over the `$:` reactive label syntax. TypeScript support can be hit or miss, and there could be more improvements around the stores API
I think this pitch overstates the problem with CMSes. It seems for many organizations, their CMS is working well for them. Not saying this doesn't have benefit, but, as for me, I rather like my CMS and don't feel like this is a big win.
I hope to work in one of such orgs some day because the most common experience I've witnessed was pain.
And things don't improve when you throw more money at a CMS. There's an entire industry of enterprise CMSs (yearly license in five figures) and their users aren't any happier with their CMS than WordPress users.
Is contenteditable not widely used? Is it too limited? https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...
contenteditable is pretty terrible if you want it to behave exactly the same on all browsers. that's why there are projects like CKeditor or TinyMCE.
I wrote about it here in more detail: https://letsken.com/michael/how-to-implement-a-web-based-ric...