I guess Racket’s proposal of language oriented programming isn’t so kooky after all.

Pollen, written in Racket, is arguably a "dsl for specifying ssgs"

https://docs.racket-lang.org/pollen/

Pollen seems so incredibly cool and powerful, but every time I have tried to play around with it, I get distracted by small quirks and areas that I wish were documented more clearly, or in a more organized format.

My daydream is to make a _good_ technical documentation system with it that is usable by the everyman, but it's still just a bit too much of a stretch. Markdown + pandoc + LaTeX templates get close, but LaTeX templating is a nightmare, and markdown is far too limiting and lacks expressivity (without ad-hoc DSL's slapped on top).

If anyone has a good pollen tutorial or example repo, I'd _love_ to know of it.

This is a sample Pollen project, annotated by the author using Racket's literate-programming dialect.

https://docs.racket-lang.org/pollen-tfl/

Don't mess around with Markdown and LaTeX for documentation. AsciiDoc is what you want.

Your post changed my life. Thanks for sharing this about AsciiDoc. It's such a nice tool.

I believe Metalsmith [1] is trying that approach

[1] https://metalsmith.io/

Metalsmith is pretty slick. I like how _everything_ is a just a plugin/middleware in essentially a pipeline. I've used it to template/scaffold [1] out projects before and it worked reasonably well.

[1] https://github.com/Pinjasaur/project-scaffolder

As long as they all use the same content format (like markdown + preamble) it’s relatively easy to move from one to another. Transferring themes is a pain though.

I think we are doing pretty well with increasing the number of SSGs even without a meta SSGG. But I guess there are still more blogs around than SSGs, so there's still potential for incrementing that counter.

SSGG*

Are we all thinking of the same xkcd comic at this point?