Web book boilerplate

Another book builder.  JavaScript/Grunt.

Dexy

Dexy is a neat documentation tool - here's its examples page.  Since I've started looking more closely at Heckle again for use in rebooting Decl by writing the tutorial first, Dexy seems like a good model.  (Yeah, I know, I should just use Dexy - but I'm like that.)

Anyway, its flexibility is fantastic.  That's a great model.

Learn X the Hard Way

Zed Shaw has pulled out the skeleton of his Learn Python the Hard Way book series so you can roll your own Learn X book with LaTeX.  This would be a great alternate target for mltut/Heckle.

Markdent

Well, naturally I want to write my books in Markdown instead of HTML, so I've been prowling around CPAN for proper Markdown processors...  They're all direct-to-HTML converters, except one: Markdent, by the ubiquitous Dave Rolsky.  Markdent is an event-based, configurable Markdown dialect parser.  So that's what I'm going with - because I want to be able to pull out links and the like as I go along my tree, and later I want to be able to output HTML5 article/section/aside tags, especially "aside" for sidebars, and I want to be able to write a markdown block for those.

Actually, I'm probably going to standardize on Markdent in Decl as well, once I get back to it.

Of course, that introduces a Moose dependency, but you know what?  Maybe it's time.

What I really want is Jekyll...

... only in Perl.  Which, you know, doesn't actually exist.  There's Hyde in Python.  Maybe Heckle or Hekyll?  Hekyll is actually taken.  Being, you know, obvious.  "Magpie" would be nice, but ... is even taken on CPAN.

I think I'm going with Heckle.  App::Heckle.  I'll worry about a plugin structure later.  Use TT for templates.  Stupid static generation.  Multiple blog feeds (any directory can be a blog).  Tags.  Book structure - i.e. hierarchical chapter/section structure.  Math.  External resources.  Assume the use of a modern VCS.