<pclass="commentary firstcommentary"><aid="SP1"class="paragraph-anchor"></a><b>§1. </b>Indoc is not part of the main Inform compiler and is not shipped inside the
Inform apps. Instead, it's used as a stand-alone command-line tool by the
maintainers of Inform: it generates the formatted documentation about the
language which is used both inside the apps and on the project website. (So,
although Indoc is not included in the apps, its output is.)
</p>
<pclass="commentary">Indoc is a single literate program, and is not divided into modules.
</p>
<ulclass="items"><li>● The contents page for the Indoc web is here: <ahref="indoc/index.html"class="internal">indoc</a>.
</li><li>● See <ahref="indoc/M-iti.html"class="internal">Manual (in indoc)</a> and <ahref="indoc/M-rc.html"class="internal">Reference Card (in indoc)</a> for usage.
</li><li>● In particular, <ahref="indoc/M-dm.html"class="internal">Documentation Markup (in indoc)</a> explains how the two books
supplied with Inform are marked up.
</li></ul>
<pclass="commentary firstcommentary"><aid="SP2"class="paragraph-anchor"></a><b>§2. </b>The texts of the manuals and examples supplied inside the Inform app are
stored elsewhere in the repository.<supid="fnref:1"><ahref="#fn:1"rel="footnote">1</a></sup>
<ulclass="footnotetexts"><liclass="footnote"id="fn:1"><pclass="inwebfootnote"><supid="fnref:1"><ahref="#fn:1"rel="footnote">1</a></sup> In principle, Indoc could be used with other books entirely, and the author
has sometimes used it as a quick way to turn text files into ePub ebooks. But
it's a non-goal to make it a super-duper general purpose documentation maker:
there are plenty of those in existence already.
<ahref="#fnref:1"title="return to text">↩</a></p></li></ul>
<pclass="commentary firstcommentary"><aid="SP3"class="paragraph-anchor"></a><b>§3. </b>Indoc contains the basic <ahref="../../inweb/foundation-module/index.html"class="internal">foundation</a> library, but none of the <ahref="services.html"class="internal">services</a>.