aboutsummaryrefslogtreecommitdiffstats
path: root/docs/release-2.0.txt
Commit message (Collapse)AuthorAgeFilesLines
* Switch docs to MKDocs (#602)Waylan Limberg2017-12-061-73/+0
| | | | | | | | | | | | | | | | | | | | | | | | Fixes #601. Merged in 6f87b32 from the md3 branch and did a lot of cleanup. Changes include: * Removed old docs build tool, templates, etc. * Added MkDocs config file, etc. * filename.txt => filename.md * pythonhost.org/Markdown => Python-Markdown.github.io * Markdown lint and other cleanup. * Automate pages deployment in makefile with `mkdocs gh-deploy` Assumes a git remote is set up named "pages". Do git remote add pages https://github.com/Python-Markdown/Python-Markdown.github.io.git ... before running `make deploy` the first time.
* Thorough spell check of the docs.Waylan Limberg2015-02-071-1/+1
|
* Add release notes, authors and change_log to docs.Waylan Limberg2012-03-071-4/+10
|
* Rename docs/*.md => docs/*.txtWaylan Limberg2012-03-071-0/+67
| | | | | | | | | 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.
* Renamed *.txt -> *.md in docs.Waylan Limberg2011-08-231-67/+0
|
* Upped version to 2.0.1-Final and added release notes.2.0.1Waylan Limberg2009-05-191-0/+67