You can even spend time and money to acquire a patent and it still doesn’t guarantee profit. It’s called the Miura-ori even though it was patented decades earlier. In this case, the patent acts as a record emphasizing that it’s all been done before.
I would say that the current format is a 'book' in content, but not a 'book' nor an 'e-book' in form, as you can't manipulate it as a single object. But I've seen a few other examples here on HN where people showed off a 'book' purely as a website.
As I shared in a comment above, the book is released under a Creative Commons license that does not authorize sharing derived works so only the original author can distribute you an alternative version
Feedback about a technical aspect of your blog, not about the contents of the article: unfortunately the HTML title of the page is not the title of the article, but the title of your website.
As a consequence, when I print your blogpost to a PDF file to read it offline at a later time, the filename of the saved PDF has no clues whatsoever about what the article is about.
It's probably a pirate station, deliberately broadcasting on the same frequency. Contrary to FM modulation, with AM modulation two superimposed signals one the same frequency are demodulated as if they came from one transmission.
Swan Lake was played on UVB-76 in 2010 I believe and on other occasions previously. There have been other strange sound/musics broadcasted from this location so I don't think the pirate station makes sense.
I like minimalistic tools and designs! But I don't like minimalistic documentation.
You included an example with .md files and a template, but I would like to see what Kew generated from it, without having to run the program.
How exactly does templating work in Kew? Does it fully support the 'rc' templating from Werc, or is it purely Lowdown-based with optional HTML wrappers?
Are the config options as shown in config.go the complete set, or does Kew support more config options like Werc does?
