Question 1

How does partial hydration work in Elder.js?

Accepted Answer

Elder.js allows hydrating only interactive Svelte components on the client, reducing JavaScript payloads. You specify which components need hydration, and the framework handles the rest during build or SSR, as described in the features.

Question 2

Can I use Elder.js with a headless CMS like WordPress?

Accepted Answer

Yes, through async shortcodes and data functions in routes, you can fetch content from CMS APIs. However, it requires manual setup for data fetching and caching, unlike some SSGs with built-in CMS integrations.

Question 3

Elder.js vs Next.js for a large SEO site?

Accepted Answer

Elder.js is optimized for static generation with zero JS default, ideal for purely static, large-scale sites. Next.js offers more flexibility for hybrid apps and dynamic features, but may have larger bundles for SEO-focused pages.

Question 4

How to deploy an Elder.js site to production?

Accepted Answer

Run `npm run build` to generate static files in the `public` folder, then deploy to any static hosting service like Netlify, Vercel, or AWS S3. The README provides basic commands for local serving.

Question 5

Is Elder.js good for e-commerce with thousands of product pages?

Accepted Answer

Yes, it can handle large-scale static product pages efficiently with optimized builds. However, for real-time features like inventory updates, you'll need custom client-side logic or consider a more dynamic framework.

Question 6

How to handle image optimization in Elder.js?

Accepted Answer

Elder.js doesn't include built-in image optimization; you must use plugins or custom hooks to manage assets, which can add complexity compared to frameworks with integrated solutions like Next.js Image component.

Elder.js

What is Elder.js?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions