My favorite part of SvelteKit is the interactive tutorial (learn.svelte.dev). I suspect that sometime in the past few years, I lost the ability to stay focused with traditional documentation.
A SvelteKit template for building CMS-free editable websites
61–70 of 85 posts
Re: A SvelteKit template for building CMS-free editable websites
#62This is great, and it's something I've always wanted. The closest I've ever got to that was Hugo and Github Pages.
Also, it's the best demo I've seen in a while. Completely obvious to use.
Re: A SvelteKit template for building CMS-free editable websites
#63Wix, Squarespace, Weebly are also examples of websites you can "edit without changing the source code."
Re: A SvelteKit template for building CMS-free editable websites
#64As 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…
Thinking about it some more, I agree that a having "static mirror" of the editable site might be a nice thing. But that's for another day to implement. If someone else does I'd be curious to see it in action!
Re: A SvelteKit template for building CMS-free editable websites
#65I 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.
A full-featured CMS includes editing workflow I think: so an intern writing a press release has to have the article checked by an editor and maybe the legal department before publication, with corrections or comments included. At a pinch you could use Google Docs but that comes with more friction - hard to preview the content on the site etc and it's not so easily enforced as a locked-down CMS workflow.
Re: A SvelteKit template for building CMS-free editable websites
#66Postgres + 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.
I was wondering about SQLite as well, but for the purpose of easy local-first development.
Re: A SvelteKit template for building CMS-free editable websites
#67Earlier quoted context omitted.
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 bl…
Exactly. This is for frontend developers, who want to control the layout in code, but allow end-users to make content changes (without destroying the layout :P).
If you or your end-users prefer to also define layout and style in a visual interface, that's what CMS and No-Code tools are made for.
As for earning money: I was thinking of creating specific templates (e.g. an editable artist portfolio website) and sell those at a one off price (in a similar way that Tailwind offers paid website templates). But I'm also really happy to do custom work. Like someone comes with a design and I execute it using this approach. I think there's much value for people who want a website but have not technical experience and still want to keep the content of their website up to date themselves. I could offer training for frontend developers to build editable websites with Svelte.
Re: A SvelteKit template for building CMS-free editable websites
#68Earlier quoted context omitted.
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 [0]: https://api-extractor.com/
It's not about generating types though. The reasons are laid out in the video.
Re: A SvelteKit template for building CMS-free editable websites
#69Wix, Squarespace, Weebly are also examples of websites you can "edit without changing the source code."
When we enter the space of non-open source interactive website builders, I believe this list could be extended to a never-ending stream of products. Maybe this isn't exactly true, but at least in this market segment there is more than enough competition.
Re: A SvelteKit template for building CMS-free editable websites
#70I'm currently looking for something even more limited and lightweight, where I, as a developer, can just deploy a static site regulary (e.g. built by hugo), but with a few small sections editable on the front page, like a vacation notice, job openings etc.
Moving everything to a CMS or something like this, seems a lot of work. I'm looking at just using server-side includes for those sections, but haven't found a good editing frontend for that. Just exposing a single file in a git repository and deploying that via some build infrastructure (e.g. build.sr.ht) would be another method. Some live content preview would be nice in either case...
A surprising number of sites don't even need new pages dynamically, like blog articles, but just rather minor edits to a small subset of the content. Small businesses, medical practices etc.