I like the idea of a docpad plugin. Action would be tied to the site, so long as
we continue using docpad this would be ideal. Python would be a strong
consideration for "future proofing".

So to address fluzz's Q#3 above - we'll start with a docpad plugin and proceed
from there.

I think the notion of an exchange file format would be most useful here. Code to
generate, for example, xml of all game data and a plugin that processes that
data to produce page output put sounds ideal. I do not recall any examples where
existing code needs special game-based rule processing other than dependencies
(e.g. to produce droid pages we also need item data to link to droid weaponry).
Exchange file is a workable solution.

Until we come up with a mechanism for when to execute update process, manual
intervention can be employed to generate the Player Guides from src code.

Off to dive into coffee-script...