On Thu, May 07, 2015 at 09:30:59AM +0200, Philippe Bruhat (BooK) wrote: > On Thu, May 07, 2015 at 06:14:57PM +1200, Kent Fredric wrote: > > > > Even some git based workflow that published to github pages with some > > atrocity of jekyll would be better for this task IMHO than a wiki. ( This > > is also a "moderately low barrier to get it working using existing > > contribution systems" thing ) > > Hey, this is exactly what I was proposing in my other email: aggregating > documents that live on specific branches of specific directories. > > I'll try to quickly produce a proof-of-concept.
It lives in the book/publishing branch: https://github.com/book/CPANio/tree/book/publishing The current reference documents are obtained from these repositories: - https://github.com/neilbowers/history-of-cpan.git - https://github.com/Perl-Toolchain-Gang/toolchain-site.git Each document has a "fork me on github" link pointing back to it, and so does the table of content (pointing back to the project instead of individual files). The configuration lives here: https://github.com/book/CPANio/blob/book/publishing/cpanio.yml New documents in the source repository are published automatically (see include/exclude for ways to ignore documents). Unless someone objects, I'll put this live in a day or two. -- Philippe Bruhat (BooK) Beauty may be a curse, but not as great a curse as stupidity. (Moral from Groo The Wanderer #11 (Epic))