Yes, in shell, but requiring 'comrak', whatever that is. I also generate[0] html[1] from markdown for my vimwiki.
[0]: https://github.com/tasuki/vitwiki/blob/master/build.sh [1]: https://wiki.tasuki.org/
https://github.com/kivikakk/comrak - common mark renderer
I do somewhat wonder why not pandoc, but it is still an interesting project
My first blog was made with NanoBlogger, which was what you would call a static site generator today. It's made in Bash.
I remember setting up a few of these back in the day.
I've set up a few with that too, it was a great bit of software and a great concept.
I wonder what would be a good way to generate a website with minimal software installations, for example in standard github runner image. This example uses comrak tool to process markdown into HTML.
I've come up with using Java and XSLT. Java is installed in Github Runner image and there's built-in XSLT support in Java standard library. You can write HTML and use XSLT to add header, footer and do other processings if necessary.
So basically I want to generate a website in github runner without accessing network to install something else.
I guess one could just `cat header.html content.html footer.html` but that requires a lot of tiny things like extracting title from content and inserting it into header, etc. Nothing that lots of greps and seds couldn't handle, of course...
In fact, that is my line of thinking, except "using whatever already exists on my computer(s)", which is: bash, sed, grep, jq, awk, pandoc, inotifywait, and xdotool.
The point being exactly to avoid whatever a third party may or may not deign to let me use, without hassle.
We do basically this for our tests in statue: https://github.com/accretional/statue/tree/main/test/hermeti...
npm pack builds the file locally, then we expose it to the container filesystem where we do a build and check the outputs. You can move dependencies to bundledDependencies in npm to embed them in the image.
However, this is assuming you're rebuilding the static site generator itself every time. If you just want to build a site using an existing static site generator, it's much easier provided that the site generator itself is easy to use (for example, ours has a one-liner to take you all the way from nothing to a local static site running on localhost, see https://statue.dev)
If you aren't changing the SSG code itself between container runs you'd just mount the markdown to the container and pre-install the ssg in the Dockerfile itself. For statue.dev that would just be a Dockerfile almost exactly the same as the one we use already, except you'd use your own script, and RUN this in the Dockerfile itself: yes | npx sv create . --template minimal --types ts --no-add-ons --install npm && npm install statue-ssg && npx statue init && npm install
In your script you'd just npm run build then do whatever it is you want to do to send the files somewhere, and wherever starts the script, you'd do something like -v "pathtomymarkdown/foo:/test-package/" - not sure how to do this in github runners.
Depending on how interested you/other people are in doing this with statue.dev, we could prob get something like this (where the markdown is parameterized, not the npm package) working by Tuesday. We're building out the sandbox/build features on our cloud platform as we speak, this could be one of the first use cases/defaults.
For GitHub just use Jekyll provided by GitHub itself?
A good way to do that with anything, I found, is a Makefile which downloads and compiles the few things it needs :D
This is fun. I do love a good bit of shell scripting. Also makes me want to make my own little ssg in whatever way I see fit.
Very much pro-this. Mine says:
It's job is to help me make my website. Thus, its scope, (mis)feature set, polish will always be production-grade, where production is "works on my machine(s)" :)
i write in markdown, use lowdown + make to build html, push the html to a branch that my hoster serves from : https://piraty.dev/
Love it! My personal sites tend to start hand-written, evolve into a bash script, occasionally advance into python, but mostly just stay in bash, because it's convenient, doesn't need to please anyone else (nor would it!), and is already built for text processing into files. (I write a lot of scrappy shell scripts for my job too. I guess I should start asking an AI to generate whatever I want directly instead. Cobbling together a script is more fun though...)
The title seems to be a bit misleading IMHO because it does not really only use `sh` but heavily `sed` it seems, which is a whole programming language well suited for templating. I've in the old days written a Macromedia Dreamweaver compatible template engine using such a scheme, which I personally used quite a long time actually without Dreamweaver because this WordPress madness was even a thing.
why not perl?
Sometimes we are very self-aware, but we still do things just because...
- It is a wee publishing system made of pipelined workflows, optionally driven by streams of file events (for the hotreloadin' bits).
- It will not surprise a Perl/PHP gentleperson hacker from the last century.
- It exists because one whistles silly tunes and shaves yaks.
- my site maker's READMEfell out of popularity lately
What is wrong with people.
Please have a moment to read the title of this site again :)
Care to elaborate? I don’t see anything of issue here, in fact it’s pretty good.
I don't get this kind of indignation against anything shell related.