Gatsby VS Svelte

Gatsby.

When we decided to open-source our blog and docs, we were spoilt for choices. Today there are multiple well-supported and fully-featured frameworks for open-source content creation. Some of the options that we considered were Ghost, Jekyll, Hugo, Nanoc, and Gatsby. There are even more frameworks beyond these, and each tool has its pros and cons. Which one do we recommend? Well, we don't. The best tool for you is the one that fulfills your requirements.

#31 gatsbyjs/gatsby

Take a look through this thread https://github.com/gatsbyjs/gatsby/pull/19458 and related discussions - not sure if this carried over to the new gatsby image component but appears intentional.

Links to more sources on Gatsby Gatsby Home Site

For the frontend, you have the option to use a starter storefront built with either Next.js or Gatsby. As with both options, you will end up with a static website that connects to the headless server, the speed of your website is almost guaranteed to be fast.

Related discussion - https://github.com/gatsbyjs/gatsby/discussions/33710

This is a bit complex, and you might want to use a UI framework like React, Vue, or Svelte.

When linking https://svelte.dev/ the description is set to null which is probably due to the uppercase letter in the meta tag? Is this something the proxy could/should take into account so the description is read nevertheless?

Of course, the correct tool, as usual, depends on the requirements of your project. For an API, Apiary might be your best choice, if you want a more generalized documentation you Read the Docs might give you a quick and free way to have your documentation up and running, however if you really want a lot more control over styling and such, docussaurus can really help. There is also a last option which is quite rare though: just make a static website from the ground up. You can use React, Svelte, or really anything you want to build a documentation site. It's a lot more work than any of the previous options, but if you truly believe you need to control every single aspect  of your documentation it is still a possibility.

But the big name players are still React, Angular and Vue, in my opinion (and I fully confess there was a lot of my opinion in the decision phase here!). Other noteworthy candidates were Next.JS and Svelte.

AJAX and Single Page Apps ushered in a new age of web experiences, however it is not without it's flaws. Transitional Apps is a new paradigm of web apps which proposes a new direction. Rich Harris of Svelte introduces this concept at Jam Stack Conf 2021.

Svelte hasn't anointed a set of testing tools or does not advocate for a particular testing strategy. It gives some basic advice. More established frameworks have recommendations and integrations specific to their CLI tooling - React recommends using Jest and React Testing Library, and Vue recommends using Mocha or Jest with Vue Testing Library. In theory, you can use whatever JavaScript testing library you want for testing, because in the end you will be testing JavaScript code, regardless of whether it is transpiled or not. However, it can prove to be tricky to integrate different tools into a frontend toolchain for your "dev stack".

Agree. However I haven't been able to overcome slight lag when custom cells are rendered. I'm using svelte components which is not ideal since svelte carries a lot of extra code and it's esp noticeable with very small components. Wonder how templates pr might improve this (https://github.com/sveltejs/svelte/issues/3898).

I’ve been using it in production for months now, and started the project the day SvelteKit went public, have had absolutely no issues. As for tutorials, honestly the docs have been enough with how straight forwards they are. Sometimes if I didn’t fully understand a concept I’d look at the RealWorld SvelteKit implementation. Another good thing to look at is the svelte.dev sites repo. You mentioned connecting to a database and not being able to find tutorials for it, so there’s how the Svelte site does it. Imo the best tutorial is production-code written by the people who made the thing you’re using.