Djmoch's Auto Generator
git clone git://git.danielmoch.com/dag.git
Log | Files | Refs | README | LICENSE

commit cd6a59d9fc695b56eb9e30884c047cfe97e61ae3
parent 1c291f956e3c0a953913172b6e8b187b193a239d
Author: Daniel Moch <daniel@danielmoch.com>
Date:   Wed,  2 Sep 2020 10:31:24 -0400

Flesh out README a bit more

MREADME | 27+++++++++++++++++++++++++++
1 file changed, 27 insertions(+), 0 deletions(-)

diff --git a/README b/README @@ -14,3 +14,30 @@ on tools available in any POSIX operating system. - m4(1) is used to process page headers, footers, and any other data built from a template + +The design is intended to make it trivial to swap in different tools, +provided drivers are available. + +There are methods, documented (more or less)[1], on using the tools +above to generate a static website. Dag was created because these +solutions have several drawbacks: + +- Short of dropping a Makefile in every source directory (which is + honorous), it's not apparent to the author how best to avoid the + problem of regenerating files unnecessarily. Dag is able to do this + trivially. + +- Even if the above hurdle were overcome, make(1) would still need a + helper tool to parse the post metadata at the beginning of each + Markdown file. Once we've begun to write a tool for this, we may + as well make our lives easier and avoid recusive make(1) while we're + at it. + +- Generating indexes without a specialized tool to do so is cumbersome + at best, and may not even be possible without using GNU extensions + to m4(1). + +[1] - See, for example, http://p.hagelb.org/Makefile.html. Phil boasts +that his website is generated using nothing but m4(1) and the linked +Makefile, although he admits that index generation is tricky (ed: and +probably relies on GNU extensions)