I'm also experimenting with using Pagefind to provide search for my static site using client-side Javascript. It currently analyzes 10934 files and indexes 8183 pages (87272 words) in 40 seconds. The data is 125MB, but a search for, say, "sketchnote" transfers only 280KB, so that's pretty good. I think I'm adding the date properly and I know I can set that as the default sort, but I haven't yet figured out how to make it possible for people to sort by either relevance or date as they want. I also want to eventually format the search results to include the date. Maybe Building a Pagefind UI – dee.underscore.world will be useful. #pagefind #ssg #search

Würde ja liebend gerne wieder #publii (→ https://getpublii.com/) verwenden, aber von github etwas Abstand nehmen. Hat das irgendwer schon auf #codeberg zum Laufen bekommen? Oder welche Static Site Generators nutzt ihr auf codeberg? #SSG #blogging

Weeknotes for 2025, week 12: https://denisdefreyne.com/weeknotes/2025-w12/

I don't want to generate a full (hierarchical) graph of all pages in my #AspNet #SSG, but it looks like I have no choice.
Also, I have to load all Markdown files upfront, before I can even think about building the graph as a whole.
Upside, all Markdown files are loaded once, and then accessed from memory.

personal blog republished with thanks to @akkartik and https://git.sr.ht/~akkartik/gen_site/tree - a "freewheeling" static site generator written in lua; and so accessible, immediate, and encouraging.

once you marked up up a post `gen_site` does three things well: filing of markup, indexing of content, updating of feed.

`gen_site` is tiny, doing just the right amount of organisation to keep a blog fresh and tidy #ssg #lua

#TIL #zola can link your notes / pages like a #zettelkasten note taking app. You just have to enable backlinks in config.toml.

bottom_footnotes = true

Just checked with `time` the time it takes for two CLI frameworks to perform one command invocation (which is basically an empty method body).

One takes 0.13s, the other 0.16s (synthetic benchmark difference is 0.04s).
Most of the time is spent configuring the WebApplicationBuilder.
Do I care that "--help" is printed in 0.09s/0.16s?

Adding to my #SSG ramblings. This is roughly the layout I'm thinking of.
Whether /content/Home will be there, I don't know yet, that is how Grav does it.
Keeping the wwwroot and Views/-structure, as that is configured by-default in ASP.NET.

The Views are all runtime-compiled and then rendered based on files inside the content-folder.

Building an #SSG, the easy part: Getting templates to render.
The difficult part: Listing all content (Markdown), storing them, assigning metadata.
The hard part: Making sense of all the data acquired.

Thinking about an #SSG, and why I don't like the established ones (Hugo, Astro, probably many more): I have no clue what I want, and what I'm used to doesn't work.
Another frustrating thing: I can't communicate up-front what I want, because I only realize what's missing or orthogonal to what I'd like when I use stuff.
Here's a non-exhaustive list of things I want to remedy with my own generator.

Just before lunch, while I was mowing the lawn (a symbol of the start of spring), I was reflecting on my SSG.
I made two more changes:
First, I added caching. On Hugo, every time I modified content, the entire site was regenerated. No problem, but with my distributed CDN system, this meant that all the content was essentially outdated. Not a big deal on a small blog like mine, but it could be quite different on larger sites. The caching I've added now tracks the dependencies of added and/or modified articles and only regenerates what was added/modified and its dependencies. I’ve been generous with the dependencies, as it’s better to regenerate more than less. I’ve noticed that from generating 600 pages, now a single modification regenerates about 30, leaving the rest unchanged.
This is good for caching and performance optimization.
As a result, in the footer banner, I've added the generation date and time (missing the timezone, I’ll add that), so I can see and debug what gets regenerated and what doesn’t.

Aquí un listado enorme de generadores de sitios web estaticos.

https://jamstack.org/generators/

Je fais un #website pour un collectif d'ami·es non tech. Selon vous quelle est la meilleure manière pour qu'iels s'en sortent sans moi pour mettre à jour & modifier le site?
Un #CMS à part entière comme #Grav ?
Un #SSG comme #Eleventy , sur #gitlab ou sur un de leurs ordis?
Avec un #headlesscms ? Ou du sur-mesure?

Vous avez suggestion, bonne pratique, outil?
Sachant qu'il n'y a pas d'envie manifestée d'apprendre le web et l'utilisation du terminal etc.

One of the reasons I didn’t use Hugo for the new company website is that, once again, the latest update broke my blog. Version 0.143 removed some things (already deprecated), causing issues with the theme I use. It wasn’t anything a jail dataset rollback couldn’t fix, but is this really what I want?
I’m seriously considering switching to something else. manpageblog is also a contender; I just need to figure out if it has all the features I need.

incorporating Quarto into my Hugo site workflow

Hello Quarto

#SSG #Hugo #Blog

https://randomgeekery.org/post/2025/02/hello-quarto/

So I’m playing around with #Hugo modules, and this really is a much easier way to do Hugo. Is there a database of these modules somewhere? Maybe like a getting started directory for modules that you can use other than themes? somewhere? I know you can use them for other things, but I’m having trouble figuring out what else to use them for other than themes. When I launch the new website, I’m going to upgrade my static site generator guide because this is so much easier. #SSG #staticSite