4 ms·

Looks nice, but I don't think it will replace my current setup. I simply use makefiles (or rather mkfiles [0], because of the neater syntax) to administrate the

Looks nice, but I don't think it will replace my current setup. I simply use makefiles (or rather mkfiles [0], because of the neater syntax) to administrate the generation of the site from markdown. That also makes it easy to add a deploy-target which deploys the site. [0] http://doc.cat-v.org/plan_9/4th_edition/papers/mk http://doc.cat-v.org/plan_9/4th_edition/papers/mk

falcolas 11y ago
Mind documenting and displaying your toolchain? Would be interesting to see how you do it with Makefiles.
- black_knight 11y ago
  I'll do a more thorough write-up some time, but I do the obvious thing — use meta rules to generate the files using the appropriate tools. I use Pandoc to convert to html and glue together the files. An index file lists which files go to the server. Some files are html only, others are also available as PDF. Some of the things I do are less obvious. There is a rule to make the target «deadlinks» which iterates through the resulting html files and attempts to fetch the (first bytes) of each linke. The links which fail go into deadlinks. There is also a target which lists spelling mistakes. The deployment target is configured to fail if there are dead links or spelling-mistakes (there are also a few other sanity checks).
qznc 11y ago
Did you implement stuff like a blog-aggregation-page and Atom-feed? How do you show the dependencies from aggregation to all aggregated items into the Makefile? I tried using make, but then made my own 152-lines [0] of simple Python instead. [0] https://gist.github.com/qznc/6fbdc37ad33e6853911a https://gist.github.com/qznc/6fbdc37ad33e6853911a
- black_knight 11y ago
  I didnl’t try that since my site is not a blog. Some files on my site depend on others in non-trivial ways. For them I just use an index file of dependencies, and cat the index file in the dependencies list. It is a bit tedious to update the lists, but I have sanity checks in place to tell me when something is missing.

falcolas 11y ago

Mind documenting and displaying your toolchain? Would be interesting to see how you do it with Makefiles.

black_knight 11y ago
I'll do a more thorough write-up some time, but I do the obvious thing — use meta rules to generate the files using the appropriate tools. I use Pandoc to convert to html and glue together the files. An index file lists which files go to the server. Some files are html only, others are also available as PDF. Some of the things I do are less obvious. There is a rule to make the target «deadlinks» which iterates through the resulting html files and attempts to fetch the (first bytes) of each linke. The links which fail go into deadlinks. There is also a target which lists spelling mistakes. The deployment target is configured to fail if there are dead links or spelling-mistakes (there are also a few other sanity checks).

qznc 11y ago

Did you implement stuff like a blog-aggregation-page and Atom-feed? How do you show the dependencies from aggregation to all aggregated items into the Makefile? I tried using make, but then made my own 152-lines [0] of simple Python instead. [0] https://gist.github.com/qznc/6fbdc37ad33e6853911a https://gist.github.com/qznc/6fbdc37ad33e6853911a

black_knight 11y ago
I didnl’t try that since my site is not a blog. Some files on my site depend on others in non-trivial ways. For them I just use an index file of dependencies, and cat the index file in the dependencies list. It is a bit tedious to update the lists, but I have sanity checks in place to tell me when something is missing.