golang-ical VS chroma

I went ahead with https://github.com/arran4/golang-ical after a lot of googling, but I had to hand-roll alerts VALARM with no help of static types.

I've used a markdown to html converter to convert my blog posts into HTML with very nice and customizable code samples... in my case I used Go's Blackfriday library with bfchroma[1] doing syntax highlighting with Chroma[2]. To add your language to Chroma you have to provide a lexer, which in turn is written in Pygments[3] syntax.

[1] https://github.com/Depado/bfchroma/

[2] https://github.com/alecthomas/chroma#supported-languages

[3] https://pygments.org/docs/lexerdevelopment/

quick for generating Html and syntax highlighting code blocks

Chroma

For books from other publishers, I am just hardcoding language directly on an ad hoc basis. I briefly considered off-loading language detection to a library like chroma, but that might be too much work for little benefit.

Great blog, you should definitely do research on how you could implement a syntax highlighter for the code parts. Go Hugo for example, uses Chroma. Nice work 👍

So I pushed my code and made a pull request.

Hugo has a built-in syntax highlight that uses Chroma, a library written in go.

In Go we have https://github.com/alecthomas/chroma, and I implemented the lexer that the Caddy docs use for syntax highlighting the Caddyfile (see https://caddyserver.com/docs/caddyfile/concepts for example). What's cool about this is Caddy is serving that as a markdown rendered via Go templates, with Chroma for code blocks. So Caddy can highlight its own config.