elderjs VS Strapi

Does someone has experience with headless static sites generator that uses svelte with an optimized SEO in mind? I'm currently testing https://github.com/sveltejs/kit but I ran into some problems into building using static-adapter (index.html without static content, metatags being generetad by JS and not inside html file) so I'm currently testinghttps://github.com/elderjs/elderjs and https://github.com/withastro/astro and I would like to know if someone has any experience using svelte to build "simple" projects without the need of client side routing or SSR, just a plain old html, js and css build. Thanks!

If you are in a larger scale SEO project this does blazing fast static generation with Svelte: https://github.com/Elderjs/elderjs

check out https://github.com/Elderjs/elderjs

Finally, there is the frontend process powering the RoboStreamer website and the control center. The whole frontend is created with Svelte using Elder.js which makes it easy to create fast and SEO friendly web projects.

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.

Strapi provides a centralized data managing platform. This makes it easier to organize, update, and maintain the FAQ data. It also automatically generates a RESTful API for accessing the content stored in its database.

https://prisma.io is popular as I understand it. I've been trying out https://strapi.io the last week and am thoroughly impressed.

They both do much more than build queries. One big thing both do is automate database migration calculations. Strapi goes further and gives you a CMS and admin UI on top, as well as doing a lot more of the complex query building from a json object. Both still require a fundamental understanding of the data model and SQL

As of April 2024, Strapi's GitHub repository has garnered 59.7k stars and 7.5k forks, showcasing its widespread adoption. The project has also secured a substantial $45+ million in funding, cementing its position as a prominent player in the headless CMS space.

const pages = await client.GET("/pages", { params: { query: { filters: { // @ts-ignore - openapi generated from strapi results in Record // https://github.com/strapi/strapi/issues/19644 path: { $eq: path, }, }, // @ts-ignore populate: { blocks: { populate: "*" }, }, }, }, });

On a side note. Where do all these endpoints come from? Strapi is open source. We can read the source code. All these endpoint come from the Users and permissions plugin. So, if we go to Strapi on github and browse around the files a bit eventually you will find the auth.js file that contains all of the routes. You can also find the Strapi controllers in there if you're interested.

Strapi

Strapi: The Code Anarchist

Strapi - Open source Node.js Headless CMS 🚀