summaryrefslogtreecommitdiff
path: root/doc/build/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* - mako_layout isn't used, remove itMike Bayer2014-09-071-3/+3
| | | | - to check for epub look at "builder"
* Docs: use the base layout when mako_layout=='epub'pr/133hiaselhans2014-09-071-1/+1
| | | | | | - https://readthedocs.org/projects/sqlalchemy/downloads/epub/latest/ renders with the full template which is unreadable on e-readers - in the makefile the template-variable mako_layout is set for target: epub which makes mako use only the base layout. - this is the more elegant solution as proposed to #133
* integrate new readthedocs/sqla.org doc buildMike Bayer2012-01-231-8/+0
|
* fix the gettext to be the same way sphinx-quickstart gives youMike Bayer2012-01-081-3/+7
|
* add support to generate gettextMike Bayer2012-01-071-0/+4
|
* - add a latex Makefile to texinputs that gets copied on latex build,Mike Bayer2011-07-071-0/+3
| | | | | | | | | ensures pdflatex/latex errors are totally ignored - fix all SQL/code examples in the inherits doc to be within 79 chars. will need to do this for all the docs to get pdf to not look crappy. - add an abspath to the "templates" dir, not sure of the rationale here but is harmless, [ticket:2211] - integrate pdf build with site-mako build
* - add helpstring for site-makoMike Bayer2010-11-141-0/+1
|
* - add Sphinx 1.0 makefile and config options, [ticket:1929]Mike Bayer2010-09-291-19/+110
|
* we work with sphinx 0.6.1 nowMike Bayer2009-04-251-1/+1
|
* add collections module to API ref for completeness. links to the mapper ↵Mike Bayer2009-03-211-1/+1
| | | | | | documentation which is less wordy.
* - VERSION moves just as a string in __version__Mike Bayer2008-12-101-0/+1
| | | | | - added modified sphinx.sty with plain Verbatim section - link to pdf doc in site
* Enabled sphinx doctests.Jason Kirtland2008-12-061-0/+2
|
* - merged -r5338:5429 of sphinx branch.Mike Bayer2008-12-061-0/+48
- Documentation has been converted to Sphinx. In particular, the generated API documentation has been constructed into a full blown "API Reference" section which organizes editorial documentation combined with generated docstrings. Cross linking between sections and API docs are vastly improved, a javascript-powered search feature is provided, and a full index of all classes, functions and members is provided.