elderjs VS Hugo

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.

E.g. Hugo-academic has Microdata RDF (Go) Templates; and supports Markdown, Jupiter, LaTeX: https://github.com/wowchemy/starter-hugo-academic

"Build pages from data source" https://github.com/gohugoio/hugo/issues/5074

Hugo is the fastest static site generator out there, and it’s past time we celebrated it, as well as the developers, agencies and contributors who make the most of it.

I've been looking at replacing my project's website with Hugo (https://gohugo.io). Rather than generating a web page dynamically every time someone comes to your site, you generate the entire website statically whenever you change something. That means hosting can be entirely a "dumb" web server (or a "dumb" web server + apis which feed info to javascript, if you really need it). It also means:

* you can keep everything in version control to roll things back

* content can be fed to it programmatically

* project members can send pull request to post content, rather than requiring a special account

I've only gone through some examples from a book so far, but it looks pretty powerful, and is has good recommendations from others in the community.

I don't (yet) have a personal web presence, but if I do, it will definitely be something like Hugo.

And https://gohugo.io

Reading the commit message:

You already know Hugo. It’s one of the most popular static site generators in the world, because of its optimized build speeds, built-in templates for SEO, analytics, commenting (and more!), and its flexibility for developers. But while frontend developers will usually be the ones who build and set up new Hugo websites, they’re far from the only people who use Hugo on a day-to-day basis. In fact, most content and marketing teams will spend more time adding, removing, and tweaking website content than a site’s developer will. (This is another reason Hugo’s blistering fast build speeds are vitally important for production sites which see a lot of content changes.)