elderjs VS Strapi

I like SvelteKit and am using it on projects, but this looked interesting too https://elderguide.com/tech/elderjs/

I'll just throw it out there though: it looks like Elder.js might be a another good option for this: https://elderguide.com/tech/elderjs/

If you're comfortable with html and not afraid of learning Javascript you should be able to pick up Svelte quite quickly. There's a cool project build on it called Elder.js and it's all about massive statically generated sites from data.

This lets you reduce your payloads while still having control over component lazy-loading, preloading, and eager-loading. While lesser known than Astro, Elder.js included partial hydration as early as August 2020, roughly six months before Astro's initial commit.

Personally for SSG I use Elder.js and found it to be great. Built both my hobby project and work project using it.

I mostly use Svelte (https//svelte.dev) for any frontend development, and stick with two frameworks: SvelteKit(https://kit.svelte.dev) or Elderjs (https://elderguide.com/tech/elderjs/).

Svelte might be worth looking into. There is even another version called ElderJS that boasts 10k+ paged SEO First deployments, both server side and static site. For reference, Elder.js easily generates a data intensive 18,000 page site in 8 minutes using a budget 4 core VM

If you're dead set on SPA, I'd take a look at Elder.js. It's Svelte based and is designed to handle SPA prerendering at scale.

Don’t see a feature you’d like in the backlog? Feel free to submit new feature requests or even better, start contributing to Strapi on GitHub. All contributions and users are welcome!

Strapi is an open-source headless CMS that allows you to effectively manage your application content by separating the backend and front end utilizing Jamstack technology. it provide flexible and dynamic method of exchange content across your applications.

In this article, I will show you how to create a Pet Adoption CRUD application. You will use a headless CMS, Strapi, for the backend, and React with Context Api. The application will display a list of pets with details related to each, and you will be able to add, edit or delete pets from the list.

Strapi is an open-source headless CMS based on Nodejs and used in designing APIS and managing content. Strapi helps us scaffold our backend quickly, build APIs and consume the APIs from the client-side. The client can be mobile, web, desktop, cURL, etc.

But, to be more direct to your question, WordPress is what's called a CMS (Content Management System). Unless your site is very basic, or extremely customized, a CMS is important. WordPress is a competent CMS, but it can be difficult to work with. There is a new CMS I'm very excited about called Strapi that is very developer focused. Strapi is a headless CMS, which means it takes care of all the content behind the scene, and you're responsible for building the site to ingest that content. A Strapi backend with a Vue/Nuxt frontend - that would be a great site and developer experience!

Strapi is an open-source Node.js headless CMS (Content Management System) based on Node.js used to develop APIs(RESTful and GraphQL APIs) and build the APIs content. The APIs in Strapi are built in the form of collections or single types.

Strapi

Netlify + Jamstack : Netlify + Jamstack A. Gatsby/NextJs (My preference is gatsby) B. Strapi/Contenful/Any other headless CMS: Strapi Contentful Extra: Deity ( havent tried this one yet but it's for ecommerce) C. Stripe for your payments Stripe D. FaunaDB/DataStax as the DB: Serverless DBs Netlify E. Form Bucket to store forms submits in the cloud: FormBucket

Strapi continues to be the most popular free, open-source, headless CMS, and, recently, it released v4. Built using Node.js with support for TypeScript, Strapi allows developers to perform CRUD operations using either REST or GraphQL APIs.

Strapi is a headless CMS coded in Javascript. A headless CMS has no frontend, only an admin panel, so it is ideal for developers. In other words, a Headless CMS is an API that serves up your content to be consumed by a frontend.