Live data from Hacker News

A SvelteKit template for building CMS-free editable websites

editable.website

31–40 of 85 posts

Re: A SvelteKit template for building CMS-free editable websites

#31

This will sound snarky but I just write in html and css. No requirements, no set up, no steps.

At this point, that's like being proud you write in assembly while all the hipsters use C++. Or it's like being proud you don't use any libraries in Go.

Build steps aren't evil. For most projects, you never even touch them. You use a project template and then you're done.

What you get in return is an amount of work no human can do by hand: type-checking, tree-shaking, cross-browser shims, image optimization... it's a huge list.

At this point, I wouldn't hire someone who thinks build steps are a waste of time. Programmers should know the value of automating complex manual tasks.

Re: A SvelteKit template for building CMS-free editable websites

#32

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

Compared to all the weird rigamarole in other frameworks, the `$:` syntax is one of the least offensive compromises I've come across. Virtually nobody uses label syntax, the `$` is unlikely to clash with existing labels, and it means it can be easily parsed with non-specific JS AST parsers.

Haven't used Typescript much with it, though.

Re: A SvelteKit template for building CMS-free editable websites

#33

Earlier quoted context omitted.

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 am sure I am in the minority at this point, but the lack of TypeScript proliferation to me is a plus.

Haha, yeah. I justify this decision by assuming that designer-folks wouldn't be afraid to touch the code if it were JavaScript but would it were TypeScript. :)

To me JavaScript does a great job (if you know what you are doing) and if you're working on a reasonably small project.

Re: A SvelteKit template for building CMS-free editable websites

#34

Earlier quoted context omitted.

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 am sure I am in the minority at this point, but the lack of TypeScript proliferation to me is a plus.

You're not the only one. I don't hate Typescript, but I don't think it's necessarily worth using everywhere. I like using it for libraries that I might share or reuse, that contain some complex logic, in which case it helps my code keep guarantees. But for view-layer code, I really don't get why a lot of people are dying to use Typescript that way.

Beyond that, pretty much every Typescript project I've been introduced to suffers from just as many bugs as codebases that use plain JavaScript. Strict typing at compile time doesn't replace conscientious development practices and rigorous testing.

Re: A SvelteKit template for building CMS-free editable websites

#35
post #24

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'm coming from a minimalist perspective. Of course a hand-crafted site like this template doesn't cover all the enterprise CMS use cases, such as image manipulation, video transcoding etc. It's not a one-size-fits-it-all solution but for for me personally, it speeds up things and gives me 100% control. I'm the person who'd rather invest in developing a FFMPEG API endpoint tailored for my application than pulling in the complexity of a CMS.

Re: A SvelteKit template for building CMS-free editable websites

#36
From a cursory look, the type of content it supports seems limited. Like something you would use for a minimalist journal. If it could replicate something like https://framer.com I'd be all ears. A gallery with code would help potential users better understand its potential.

Re: A SvelteKit template for building CMS-free editable websites

#38

This will sound snarky but I just write in html and css. No requirements, no set up, no steps.

For a lot of content this really works.

What sticks with me in a way that I don't love is that this and many other modern, simple-ish solutions to having a lightweight CMS still relies on some Postgres config. I'm being picky, but I want a DB without having to think about the DB at all. Just templates plz.

Re: A SvelteKit template for building CMS-free editable websites

#39
post #22

As far as I understand it, the dynamic website you use is the same as served to the client minus the editing parts? Would it also support a scenario where the dynamic part runs on one host, say inside an intranet and users can "publish" to pre-configured static hosts or s3 buckets with a click? Static hosting could be enough for many sites and one could combine the technical and UX advantages of your dynamic interfac…

Incremental Static Regeneration could help here, but it introduces a whole category of implementation challenges. It may be worth it for high traffic websites but one beauty of the purely dynamic design is that you can mostly forget about all "build" and "caching" problems.

Anyways, at this point I'm just happy that my 0.2 vCPU / 512 MB Node.js instance on Northflank survived a HackerNews spike at 60% CPU max.

Re: A SvelteKit template for building CMS-free editable websites

#40

Is there some component library rather than "template" for doing this?

Intentionally there isn't. I wanted to demonstrate that a website with "editing" capabilities is no magic, and to encourage people to hack on every piece.

My experience after 25 years of web development is that often examples > libraries. Not always true, but I think particularly for websites it works well and gives you full control over every pixel to be rendered.

Post reply on HN