aboutsummaryrefslogtreecommitdiffstats
path: root/docs/index.txt
Commit message (Collapse)AuthorAgeFilesLines
* Better clarify the 4 space indentation rule.Waylan Limberg2013-02-211-7/+5
| | | A better explanation for #193 that includes all block-level elements nested in lists.
* Update docs/index.txtWaylan Limberg2013-02-211-0/+4
| | | | | | Clarify that strict 4 space indentation applies to nested lists.  Closes #193. Hopefully, people will read this in the docs before filing bug reports in the future. One can dream.
* Various changes to docs for updated changes, clarity, and to fix typos.Waylan Limberg2013-02-191-5/+5
|
* Improved the goals in docs.Waylan Limberg2013-01-101-3/+5
|
* Added a "goals" section to the docs.Waylan Limberg2013-01-101-2/+15
| | | | | Now, when we receive feature requests that don't fit within the scope of the Python-Markdown project, we have something to point  to in response.
* Added a list of known differences to the docs.Waylan Limberg2013-01-101-8/+44
| | | | | | | | | | | Rather than constantly responding to new bug reports for known differences between Python-Markdown and other implementations, I've added this section to the docs to definitively state our position and point people to workarounds. I'm sure some people will still file reports, but at least I have something to point them to. If there are any I missed, I can always add them latter when they come up.
* Added siteindex to docs.Waylan Limberg2012-03-071-2/+2
|
* Add release notes, authors and change_log to docs.Waylan Limberg2012-03-071-0/+2
|
* Rename docs/*.md => docs/*.txtWaylan Limberg2012-03-071-0/+66
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.