anchor.diff:  = LiquiDoc
   
  -LiquiDoc is a system for true single-sourcing of content with various output requirements.
  +LiquiDoc is a system for true single-sourcing of content in flat files with various output requirements.
  +The command-line utility engages templating systems to parse data into rich text.
  +
   Sources can (or soon will be able to) be flat files formatted in:
   
   * JSON
  
positive.code: After this parsing, files are built in any of the given output formats.
  Liquid templates can be used to produce any flat-file format imaginable.
  Just format valid syntax with your source data and Liquid template, then save with the proper extension, and you're all set.
  
  AsciiDoc files can be parsed into more sophisticated formats, including websites (using Jekyll), PDF (using Prawn), or slide decks (using Deck.js).
  
  YAML and XML files can be converted to JSON in the process.
  
  == LiquiDoc Future
  
  Where is this project headed?
  
  === Rocana
  
  The *Milestone 1* plan is to build the files by running commands manually--probably with the same PR in which a config sample file is edited.
  
  *Milestone 2* is automated build integration.
  Once we get some tests in place, maybe we can automate this procedure and never keep AsciiDoc configuration files or sample configs in the source--only the YAML source and the liquid templates that press the configs into AsciiDoc during the build.
  This will require having a testing regime in place.
  
  === Open Source
  
  If approved for release under an open license, this tool will feature in as an example for instructing DocOps techniques.
  
  == License
  
  Needs license info.
  Hoping to open source this project before too long.
  
negative.code: Both AsciiDoc and Liquid can be treated as templating languages in LiquiDoc.
  
  *AsciiDoc* is used when the variable content of the template is minimal, and the static text is maximal.
  For instance, a book chapter that contains a few variables depending on whether the book is for Windows or MacOS.
  
  *Liquid* is used for complex, variable data, typically for looped output.
  For instance, a list (array) of glossary terms and definitions that need to be looped over and pressed into a cleaner markup, such as Markdown, AsciiDoc, or HTML.
  
  You may also use these templates *in combination*.
  