solid-docs VS astro

Note: Astro supports a variety of popular frameworks including React, Preact, Svelte, Vue, SolidJS, AlpineJS and Lit with official integrations. While for other frameworks e.g. Angular and Qwik, you may still benefit from this tutorial and you would need to further set up the community maintained framework integrations.

The most common and well known is React, with many others sharing this space, such as Svelte, SolidJS, Angular, Vue, Qwik and more. All are impressive feats of engineering and come with bold statements.

GitHub | npm | website

As always, for more information and resources, you can check out the official documentation for SolidJS. We hope this blog gave you insights to easily make the SolidJS vs React choice!

The DSS UI library serves as the central pillar of DSS Template, built with react-aria to ensure accessibility-first, headless UI components. While React is the selected framework for the template, DSS is meant to be easily adapted to other frameworks like Vue or Solid. This adaptability allows teams to choose the technologies that best align with their project needs without being locked into a specific stack

For our frontend, we’ll make use of Solid.js. Let’s introduce Solid.js a bit before moving forward.

- SolidJS (fine-grain, fastest, most consistent) (dx similar to react) (small ecosystem)

[1] https://www.solidjs.com/

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…

Can highly recommend HTMX with Astro[1] for pages that are mostly static.

[1]: https://astro.build/

You can make your website run fast as well with https://astro.build - it strips the Javascript and uses HTML until js is needed. You can get 300ms page loads for outcrop.app with Astro on Cloudflare Pages. Good luck with the project. I requested early access - You should use the response to the form submit requesting access better - I mean somebody who added their email expressed a lot of intent - why end the conversation with a toast notification? I hope life is going well in Dublin.

https://astro.build/ plus cloudflare pages, deno deploy, netlify, vercel or any cloud provider with edge caching.

I host both my gamedev tutorials and web game portal websites with cloudflare pages and so far they're pretty decent:

https://raizensoft.com/tutorials/

Astro 5

In this guide, we'll walk through the entire process of creating a high-performance blog using Astro, managing the code in a private GitHub repository, pointing a custom domain from the affordable Porkbun, and deploying it all seamlessly with Cloudflare Pages. To top it off, we'll explore two powerful methods for ensuring your site's integrity before it goes live: a custom GitHub Action and Cloudflare's own Preview Deployments.

My motivation for completing Frontend Mentor's Contact form challenge was to test-drive my field and form packages. I also recently started using and enjoying Astro so I wanted to explore what it would be like to use it as my frontend workshop environment. I even ended up experimenting with Makefiles, Nushell, and Nix flakes within this project. Overall, I learned a lot and gained some new skills. In this post I'm sharing the highlights of my experience.

The data from HTTP Archive and Chrome UX Report cited on astro.build gives us a clear picture. Only 44% of WordPress sites pass Core Web Vitals benchmarks, while Astro (unsurprisingly) leads the pack at 63%.

I recently remade my website (I know, I know) and I got a surprise when getting to reimplement an rss feed because, while Astro has a module that helps with generating an rss feed, Nuxt doesn't - at least not for V3 and consequently V4. But worry not, for making one is easy enough !

Enter Astro. Astro allowed me to build a page from any URL pattern, server-side, include complex js driven divs, but have a 90+ lighthouse score. It still uses tailwindcss it still can use any js modules or functions that the SPA uses. So it was familiar. It did not require a whole re-think.

I recently discovered a static site generator called Astro, which supports many syntaxes but the .astro is a nice mix of TypeScript and JSX-like syntax. Content can use MDX which is like Markdown but with {JSX} style markup for variables and etc. The static components are used very similar to React, with familiar import statements and patterns. It is extremely easy to pick up. Best of all, it has plugins to support all sorts of other interactivity, so you can create interactive 'islands' of content using React or Preact or SolidJS or Vue etc. That way you have most of your content statically generated, and then the dynamic parts can be done from the client side.

Best of all, if you use simple unchanged files for other dynamic stuff like JSON etc, you can just generate those on build and serve those files in the host directly as the 'response' to a simple REST request, which is sometimes overlooked despite being the most fundamental form of a REST API.

https://astro.build/