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.
[dead]
A SvelteKit template for building CMS-free editable websites
51–60 of 85 posts
Re: A SvelteKit template for building CMS-free editable websites
#52Earlier quoted context omitted.
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 introduce…
> But for view-layer code, I really don't get why a lot of people are dying to use Typescript that way.
"view-layer code" is underselling how complex many modern webapps can get. When you've got 10+ engineers across 2+ teams running around in your 30,000+ line codebase, TypeScript offers a lot of benefits and makes overall iteration speed much much faster.
You don't need TypeScript for small/personal projects though. As long as everything fits in your memory, you're fine.
Re: A SvelteKit template for building CMS-free editable websites
#53Earlier quoted context omitted.
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 introduce…
Typing only eliminates a certain class of bugs. And user-defined type systems scare me. I loved ReasonML precisely because you got typing (and confident enforcement) for free through the HM type system, but TypeScript always struck me as the embodiment of "now you have two problems"
Re: A SvelteKit template for building CMS-free editable websites
#54It looks and feels awesome. Then I get to GitHub repo. Isn't JavaScript deprecated and should be replaced with TypeScript wherever it possible?
Re: A SvelteKit template for building CMS-free editable websites
#55Postgres + S3 is a great choice but is there any limitation on changing it to SQLite + on disk? Thinking that this could be easily deployed to serverless+disk like fly.io without additional components.
Re: A SvelteKit template for building CMS-free editable websites
#56It looks and feels awesome. Then I get to GitHub repo. Isn't JavaScript deprecated and should be replaced with TypeScript wherever it possible?
No, JavaScript is not deprecated.
Re: A SvelteKit template for building CMS-free editable websites
#57Earlier quoted context omitted.
yah, this is like the todo app of content management, being able to change the text (and perhaps add bold and some links), and has probably been built thousands of times by now in the short history of the web. building in-place editing for fixed text nodes isn't that hard, whatever the underlying toolkit. a CMS should be able to do that in its sleep. it's when you get beyond text into other media and into layout, spa…
To clarify: It's a different concept. And it's more of a starting point, rather than a solution. Its goal is not to build full-fledged a page builder or prototyping tools (such as Framer or Webflow). The layout is entirely up to the developer (and expressed in code), the content (as in structured data) is made editable. It's how Facebook/LinkedIn/Twitter/Medium etc. work, with the benefit that in many cases, you can…
I think you should emphasize that it is based on svelte. You can't fairly call CMS and No-Code solutions complicated when you expect users to know Svelte. That limits your audience to the kind of people (front-end developers) that aren't desperate for such tools. I am using Framer on a project and I'm pretty happy with it.
If you want to go commercial, you could develop a platform for others to contribute building blocks and templates. Something that will pave the way for a no-code tool.
Re: A SvelteKit template for building CMS-free editable websites
#58Earlier quoted context omitted.
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 introduce…
Rich and I chatted a bit about TS vs JSDoc for library authors today on the monthly dev vlog: https://www.youtube.com/live/MJHO6FSioPI?feature=share&t=95 TL;DR - Svelte's codebase will move to JSDoc types but still use TS. To be clear - Svelte will still have full support for TS, nothing is changing for users of Svelte.
Why adopt the inferior way of declaring types?
I just don’t get the issues. TS is great, and generating good types directly from TS is easy with API extractor[0]. It makes it so easy.
The resistance to me from the community boggles me and I’m sad Rich feels this way
Re: A SvelteKit template for building CMS-free editable websites
#59Earlier quoted context omitted.
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 introduce…
Typing only eliminates a certain class of bugs. And user-defined type systems scare me. I loved ReasonML precisely because you got typing (and confident enforcement) for free through the HM type system, but TypeScript always struck me as the embodiment of "now you have two problems"
> "now you have two problems"
Interesting take. I always look at it like "now you have a better solution for your modeling needs".
Re: A SvelteKit template for building CMS-free editable websites
#60Earlier quoted context omitted.
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 introduce…
Typing only eliminates a certain class of bugs. And user-defined type systems scare me. I loved ReasonML precisely because you got typing (and confident enforcement) for free through the HM type system, but TypeScript always struck me as the embodiment of "now you have two problems"
Agreed. If I'm dealing with strong static types, good inference (and TS / Rust / Whatever ain't it) is a must.
'
If I'm going to invoke a bunch of ceremony every time I blink might as well write Java.