<noscript>2026-05-10
recently, i set a goal to more actively write content for my website. in coming back to the repository, the friction for writing content was unbearable. while i initially set out for simplicity, i somehow landed in the worst of all worlds:
i wanted to keep everything minimal but functional.
as a go programmer, i immediately reached for a minimal
binary that would use rsc.io/markdown to convert my
writing into html. similarly, a single go html template
solves the gallery toil.
i also wanted to remove mathjax. this seemed like the perfect task for an llm:
i booted up claude code. after exploring a few go LaTeX
parsers, i simply told it to generate a recursive descent
parser for LaTeX to preprocess before converting to html
with mathml. it happily did so with two bugs in all of 83
seconds. another couple minutes of active thought and a
usable parser eliminated both my writing friction and gave
me a <noscript> website.
the only downside here is that i felt the need to write the following into my README:
There is no promise anything here will be maintained, will continue compiling, or ever compiled.
./gennow, it is easier than ever for me to write content and
modify my site. i can simply stream my consciousness into
.drafts/ and programmatically generate and preview my
site before launching: go run ./cmd/site.
i really tried to avoid github actions for various reasons; however, i settled for the following, notably excluding any execution of the go binary for deployment:
gen dir