markdown/.git - A Python implementation of John Gruber’s Markdown with Extension support.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Switch docs to MKDocs (#602)	Waylan Limberg	2017-12-06	1	-126/+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 Limberg	2015-02-07	1	-5/+6
\|
*	HeaderId Extension marked as Pending Deprecation.	Waylan Limberg	2015-01-01	1	-1/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Use the Table of Contents Extension instead. The HeaderId Extension will raise a PendingDeprecationWarning. The last few features of the HeaderID extension were mirgrated to TOC including the baselevel and separator config options. Also, the marker config option of TOC can be set to an empty string to disable searching for a marker. The `slugify`, `unique` and `stashedHTML2text` functions are now defined in the TOC extension in preperation for the HeaderId extension being removed. All coresponding tests are now run against the TOC Extension. The meta-data support of the HeaderId Extension was not migrated and no plan exists to make that migration. The `forceid` config option makes no sense in the TOC Extension and the only other config setting supported by meta-data was the `header_level`. However, as that depends on the template, it makes more sense to not be defined at the document level.
*	Code exampeles in extension docs now show best practices.	Waylan Limberg	2014-08-29	1	-2/+3
\| \| \| \| \|	This is in anticipation of #335. The reference and extension api docs still need to be updated, but that will happen with change in the code.
*	Docs now use dot notation for all extensions.	Waylan Limberg	2014-08-29	1	-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 Limberg	2014-02-16	1	-4/+4
\|
*	docs: capitalization fixes, plural fixes, small wording improvements	Jakub Klinkovský	2014-02-15	1	-2/+2
\|
*	docs: update header_id documentation	Jakub Klinkovský	2014-02-15	1	-10/+16
\|
*	Removed the html_tidy extension. See 2.3 release notes for explaination.	Waylan Limberg	2013-03-13	1	-2/+2
\|
*	Rename docs/.md => docs/.txt	Waylan Limberg	2012-03-07	1	-0/+111
	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.