segbedji

That's actually a very good idea. I was thinking about using a CLI, but this will make that not necessary, and easily scalable.

Thanks for the idea.

I don't know much about Rails. But how easy is it to add a CLI, where users can select the options they want and get a scaffold generated with those specifically.

+1 to what @kevinak said. SvelteKit already provides some good ways to handle basic backend features. API routes, form actions etc... work great.

If needed, once can also plug in a customer Express or other Node.js servers, https://kit.svelte.dev/docs/adapter-node#custom-server.

I've been thinking about the right balance for validation. Should I just do a simple checks (check if fields are not undefined, empty strings, etc…), or just plug in Zod.

I will probably go with the latter.

I have kitforstartups.com, and yeah, the final goal is to add some example, and more documentation there.

Wouldn't that be much overhead? I was thinking just having a CLI where you'd choose the things you want, and the boilerplate gets scaffolded automatically with those.

Thanks, will do that.

A few weeks ago, I authored a blog post spotlighting major companies using Svelte in production.

The inspiration?

On several occasions, potential clients at my agency, which specializes in Svelte and SvelteKit, hesitated to proceed with us.

Their concerns?

They were unsure about Svelte's fit for their needs, and were unaware of its successful large-scale application by leading businesses.

So, I turned to Reddit, Twitter, Hackernews, and other sources to compile a persuasive list of Svelte and SvelteKit users.

I hope my post can help others convince more people to explore the potential of Svelte and SvelteKit.

I had a lot of fun experimenting with headless WordPress and SvelteKit, and writing a comprehensive guide about this.

Sitemaps are interesting things to tackle when you're building a website, that pulls content from a CMS (headless), and uses SSR. Both technically and for SEO purposes.

I go through in this post about how I implemented one on my SvelteKit - DatoCMS website.

For the past months, I have been using Svelte and SvelteKit more and more. And I'm absolutely a big fan of everything about them.

Things like how close the language and the framework stay to native BTML, CSS and JS.

And also how Svelte handle styling (which is the topic of the linked post).

What does the full URL looks like?

> What if there are multiple latest releases for different OS's/chips?

Yep, that would be interesting to add. It can be done easily by adding a new parameter to the URL and the form.

> Also, would be could to turn it into an open-source Chrome extension!

I haven't thought about that. How would it work? By adding the repo URL in the extension windows, or just one click download when you're on the repo page?

I create this little tool yesterday, initially for personal use, but thought it could help others if I make it public.

It basically allows to download the zip for the latest release (if it exists) on a GitHub repository.

At my work, I didn't want to download that zip every time I release a new software version and send it to my manager and colleagues. Now I just send them a unique link, and they'll always directly get the up-to-date zip.