aboutsummaryrefslogtreecommitdiffstats
path: root/docs/extensions/fenced_code_blocks.txt
Commit message (Collapse)AuthorAgeFilesLines
* Docs now use dot notation for all extensions.Waylan Limberg2014-08-291-1/+1
| | | | | | 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-0/+5
|
* docs: capitalization fixes, plural fixes, small wording improvementsJakub Klinkovský2014-02-151-6/+6
|
* docs: improved documentation of the extra/ extensionsJakub Klinkovský2014-02-151-19/+19
| | | | | | Simplified, unified style, added some undocumented options. NOTE: Footnotes/UNIQUE_IDS stays mostly undocumented
* Document hl_lines feature for fenced_code and codehilite extensions.A. Jesse Jiryu Davis2014-01-071-0/+25
|
* Fixed #110. Documented the 'fenced_code' extension's support for the ↵Waylan Limberg2012-06-281-0/+13
| | | | 'codehilite' extension.
* Rename docs/*.md => docs/*.txtWaylan Limberg2012-03-071-0/+69
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.