aboutsummaryrefslogtreecommitdiffstats
path: root/docs/extensions/toc.txt
Commit message (Collapse)AuthorAgeFilesLines
* Correct the documentation for the slugify functionDougal Matthews2014-12-221-4/+5
| | | | | The previous requirements are incorrect, the method needs to accept two parameters.
* Docs now use dot notation for all extensions.Waylan Limberg2014-08-291-2/+2
| | | | | | Except were "short names" are explained in the docs, all references to the buitlin extensions now use `markdown.extensions.*` in anticipation of #336.
* Cleaned up some minor issues with recent changes to docs.Waylan Limberg2014-02-161-5/+5
|
* docs: capitalization fixes, plural fixes, small wording improvementsJakub Klinkovský2014-02-151-2/+2
|
* docs: update toc documentationJakub Klinkovský2014-02-151-30/+43
|
* Mention new option in toc.txtDmitry Shachnev2013-09-291-0/+2
|
* Add documentation for smarty extensionDmitry Shachnev2013-07-261-2/+2
|
* Ensure toc attribute is available on Markdown class.Waylan Limberg2013-02-191-2/+19
| | | | | | This appears to have recently been broken with the fixes in #191. This time I've added tests to prevent future breakage and added documentation to explain the behavior.
* Rename docs/*.md => docs/*.txtWaylan Limberg2012-03-071-0/+56
The documentation uses features of Python-Markdown that are not supported on GitHub and it's better to get a source view of the docs anyway. For example, that way comments and bug reports can reference a specific line of a file. Of course, it makes sense for Github to render the README, so that is left with the `.md` file extension.