Foo.
IbexDoc targets four primary documentation tasks: Books, Manuals and references Articles Literate Programming (documentation embedded in source code) Presentation Slides Web pages, including WikiWebs The goal of separating markup from content has been around for a long time in the document world. For some reason it never succeeded. The problem is that: The purpose of content is to convey semantic meaning. Some markup and formatting carries semantic meaning. For example, consider italicization. Adding or removing italicization can actually affect the meaning of a piece of text. Therefor italicization (or rather "emphasis") is part of the content of a document. IbexDoc recognizes this and does not attempt to use XML for anything that might carry semantic meaning. Effectively, you can remove all XML tags from an IbexDoc file without altering the meaning of the text (although it might be rather hard to discern the meaning with all the text jumbled together!)
(title subtitle logo license options(toc,index) logo) (email, name) changes (contains sections, must appear once at EOF) (title) .. .. (a different kind of list?) .. .. .. .. .. .. .. .. .. 

     **italics**
     __boldface__
     ||typewriter||
     ==nonstructural heading==

     blank lines become paragraph breaks

     # 1
        # 1.1
           # 1.1.1

     - 
        -
           -

     \\     -   backslash
     \0x??  -   unicode
     \amp
     \lt
     \gt
     \quot
     \apos

     wiki plugins: page topology (who points here, orphaned pages, statistics, document upload, etc)
                   http://en.wikipedia.org/wiki/Special:Specialpages

     structured ebnf content?
     http://www.docbook.org/tdg/en/html/docbook.html
tables plugins (charts, graphs, diagrams) wiki-style links slides slide breaks overlays 2-column different diagram layouts color persistent outline watermark/logo 

          /** */
          ///      
          ///<
          @param
          @throws
          @see
          @link, autolinking (wiki-style?) of other classes/modules
          @return
          @deprecated
          @since
          @author?
          package-level overview (but it's lame to put it in a separate file)
          inheritance