magidoc VS Svelte

Magidoc is a fully-free open source static documentation generator for GraphQL. Whether you want to get visibility on internal APIs or document public endpoints for your customers, Magidoc can do it all! If you're interested in learning more, come see our repo!

Indexing code

It depends on what you're trying to do with your blog. In Magidoc, this engine is used to take external markdown (provided by files or a GraphQL schema for instance) and convert it to html to build a static website. This kind of library is more adapted for this kind of use-case where the markdown is provided externally.

I'm asking because have an issue in my project in which I would like to implement such search. It is a relatively complicated feature, and one of the main thing is that I would like the site to be pre-indexed. Which means that the index should be created at build time, and not when you open the page. Is it what you did in your project?

Repo: https://github.com/magidoc-org/magidoc/tree/main/packages/starters/carbon-multi-page

Depends what you are looking to do with the documentation, but there are a few tools to generate static documentation. I personally built an open source tool to generate GraphQL documentation that we use in my company. It's called Magidoc, you can see the repo here, .

Building a templates means that you are free to choose the design of the website, but also that you can implement the template in Svelte! There is a contributing guide to help you get started with the project.

If you are not interested in contributing but the project interests you, you can still support Magidoc by leaving a ⭐ on Github!

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.