I gave #Eleventy (the static-site generator) a go, suggested by some fine folks from 32bit.cafe, particularly inspired by @Leilukin's site.
it went pretty well and could even handle my bi-hosting for markdown -> html for my website and gemtext -> gemtext for my gemini capsule surprisingly smoothly.
...until I needed to handle per-blog-post assets.
I put assets such as images associated with each post in the same folder as the index.md of the post resides: posts/2025-01-01-my-post/index.md and posts/2025-01-01-my-post/my-image.png. this is not only easier for organization, but also referencing assets and avoids duplicating post slugs in the file hierarchy.
In #Hugo, these assets will get the same permalink as that of the post. ie, /posts/my-post/index.html and /posts/my-post/my-asset.png, where /posts/my-post is the configurable permalink for blog posts.
Eleventy doesn't handle any file extension other than what can be made into pages, from (md, html, njk, etc) and so these assets are ignored by default. With eleventConfig.addPassthroughCopy(...) I can use a glob such as posts/*/*.{png,mp4,webp,...} to copy the assets into the posts/*/ directory for output. However, it does not respect the permalink field in the data cascade at all, and ends up reproducing the full source directory slug together with the ISO date prefix, ie: /posts/2025-01-01-my-post/my-image.png.
The PR that resolves this which adds a new mode: "html-relative" option to addPassthroughCopy was merged about 3 weeks ago(!), and only part of the latest alpha release as of writing.
At a glance, this seems to solve my problem, but only partially -- it might not work when a post has no HTML output, only gemini, with a single index.gmi file in the posts/2025-01-01-my-post/ directory.
Fingerprinting and cache busting for resources also seems to require using a post-site-generation hook. one of the solutions would loop through all copied assets, rename the files (eg, asset.ext -> asset.hash.ext), loop through all output files and rewrite references to each asset.
Don't get me wrong -- Eleventy, Hugo, Lume, and all the rest of them, they're all great at doing what they are able to do. But when popular SSGs try and fit every need they still end up becoming a little opinionated in certain corner cases. My attempts to roll my own ends up being not very well tested clones of existing SSGs. Perhaps if I'd started with something different, such as Eleventy rather than Hugo to begin with, the story would be different. Or am I just doing everything wrong?
In any case, looks like Eleventy won't be the end to my SSG-hopping...
) to the end of your route’s name. e.g., admin![Screenshot of Kitten’s interactive shell, showing me alterning a database entry in development:
}
]
🐱 💬 kitten.db.news[0].link = kitten.db.news[0].postLink
'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/'
🐱 💬 kitten.db.news[0]
Proxy [
News {
link: 'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/',
title: 'New Kitten features: Interactive Shell (REPL), Multi-page Settings, and backup and restore (data portability)',
date: '2024-05-23',
image: '',
summary: 'In this video, Aral demonstrates the new features added to Kitten in May: including the new Interactive Shell (REPL), Multi-page Settings, and backup and restore (data portability).',
author: 'Aral Balkan',
sourceName: 'Aral’s Blog',
sourceLink: 'https://ar.al',
postLink: 'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/',
presets: 'custom'
},
{
get: [Function: bound getHandler] { boundObject: [DataProxy] },
set: [Function: bound setHandler] { boundObject: [DataProxy] },
defineProperty: [Function: bound definePropertyHandler] { boundObject: [DataProxy] },
deleteProperty: [Function: bound deletePropertyHandler] { boundObject: [DataProxy] }
}
]](https://s3-eu-central-1.amazonaws.com/mastodon-aral/media_attachments/files/113/980/351/306/618/092/original/ebbb5caaed9329a6.png "Screenshot of Kitten’s interactive shell, showing me alterning a database entry in development:
}
]
🐱 💬 kitten.db.news[0].link = kitten.db.news[0].postLink
'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/'
🐱 💬 kitten.db.news[0]
Proxy [
News {
link: 'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/',
title: 'New Kitten features: Interactive Shell (REPL), Multi-page Settings, and backup and restore (data portability)',
date: '2024-05-23',
image: '',
summary: 'In this video, Aral demonstrates the new features added to Kitten in May: including the new Interactive Shell (REPL), Multi-page Settings, and backup and restore (data portability).',
author: 'Aral Balkan',
sourceName: 'Aral’s Blog',
sourceLink: 'https://ar.al',
postLink: 'https://ar.al/2024/05/23/new-kitten-features-interactive-shell-repl-multi-page-settings-and-backup-and-restore-data-portability/',
presets: 'custom'
},
{
get: [Function: bound getHandler] { boundObject: [DataProxy] },
set: [Function: bound setHandler] { boundObject: [DataProxy] },
defineProperty: [Function: bound definePropertyHandler] { boundObject: [DataProxy] },
deleteProperty: [Function: bound deletePropertyHandler] { boundObject: [DataProxy] }
}
]")
It's very bare-bones, has almost nothing, but it's a start!
star stuff (hail 
![export default async function(eleventyConfig) {
// glob here is relative to project root
eleventyConfig.addPassthroughCopy("content/**/*.mp4", {
mode: "html-relative"
});
}...](https://est.social/system/cache/preview_cards/images/003/135/060/original/d2ebecf7afe93065.png "export default async function(eleventyConfig) {
// glob here is relative to project root
eleventyConfig.addPassthroughCopy("content/**/*.mp4", {
mode: "html-relative"
});
}...")