mirror of
https://github.com/sphinx-doc/sphinx.git
synced 2025-02-25 18:55:22 -06:00
Merged revisions 65640,65675,65699,65701 via svnmerge from
svn+ssh://pythondev@svn.python.org/doctools/branches/0.4.x ........ r65640 | georg.brandl | 2008-08-11 16:11:17 +0200 (Mon, 11 Aug 2008) | 2 lines More info in intro. ........ r65675 | georg.brandl | 2008-08-14 13:53:02 +0200 (Thu, 14 Aug 2008) | 2 lines #3546: add missing linebreak. ........ r65699 | benjamin.peterson | 2008-08-15 23:02:22 +0200 (Fri, 15 Aug 2008) | 4 lines rename util.with_testapp to util.with_app; nose was running it also make an assert more informative ........ r65701 | benjamin.peterson | 2008-08-16 00:00:54 +0200 (Sat, 16 Aug 2008) | 1 line add some tests for sphinx.application ........
This commit is contained in:
@@ -3,15 +3,18 @@ Introduction
|
||||
|
||||
This is the documentation for the Sphinx documentation builder. Sphinx is a
|
||||
tool that translates a set of reStructuredText_ source files into various output
|
||||
formats, automatically producing cross-references, indices etc.
|
||||
formats, automatically producing cross-references, indices etc. That is, if
|
||||
you have a directory containing a bunch of reST-formatted documents (and
|
||||
possibly subdirectories of docs in there as well), Sphinx can generate a
|
||||
nicely-organized arrangement of HTML files (in some other directory) for easy
|
||||
browsing and navigation. But from the same source, it can also generate a
|
||||
LaTeX file that you can compile into a PDF version of the documents.
|
||||
|
||||
The focus is on hand-written documentation, rather than auto-generated API docs.
|
||||
Though there is limited support for that kind of docs as well (which is intended
|
||||
to be freely mixed with hand-written content), if you need pure API docs have a
|
||||
look at `Epydoc <http://epydoc.sf.net/>`_, which also understands reST.
|
||||
|
||||
.. XXX web app
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user