Lines Matching full:markdown

1 # Contributing to Python-Markdown
3 The following is a set of guidelines for contributing to Python-Markdown and its
4 extensions, which are hosted in the [Python-Markdown Organization] on GitHub.
11 [Python-Markdown Code of Conduct]. By participating, you are expected to uphold
12 this code. Please report unacceptable behavior to <python.markdown@gmail.com>.
16 The core Python-Markdown code base and any built-in extensions are hosted in the
17 [Python-Markdown/markdown] project on GitHub. Other extensions maintained by the
18 Python-Markdown project may be hosted as separate repositories in the
19 [Python-Markdown Organization] on GitHub and must follow best practices for
22 The [Python-Markdown/markdown] project is organized as follows:
38 Make sure you're running the latest version of Python-Markdown before reporting
45 expectations align with the rules and/or other implementations of Markdown.
54 implemented as third party extensions outside of the core Python-Markdown
56 allows us to keep the maintenance overhead of Python-Markdown to a minimum, so
72 [Python-Markdown/markdown] project for pull requests. All pull requests should
104 In an effort to maintain consistency, Python-Markdown adheres to the following
164 The documentation is built from the [Markdown] source files in the [`docs`
166 the basic Markdown syntax, the following extensions are supported: [extra],
202 If you are linking to another document within Python-Markdown's documentation,
208 [authentication]: reference.md#Markdown
212 documentation on GitHub. If your Markdown editor makes links clickable, they
219 Python-Markdown's [Admonition Extension]:
244 To start developing on Python-Markdown is it best to create a [fork] of the
278 To be able to run the Markdown library directly while working on it, install the
292 python -m markdown
311 However,  Python-Markdown supports multiple versions of Python. Therefore, a
340     Python-Markdown provides [test tools] which simply testing Markdown syntax.
346 Python-Markdown follows [Semantic Versioning] and uses the
349 tuple defined in [`markdown/__meta__.py`][markdown/__meta__.py]. The contents of
401 3. Update the version defined in [`markdown/__meta__.py`][markdown/__meta__.py].
413    [Python-Markdown/markdown] repository. The new tag should trigger a GitHub
423       assumes that local clones of the [Python-Markdown/markdown] and
424       [Python-Markdown/Python-Markdown.github.io] repositories are in sibling
425       directories named `markdown` and `Python-Markdown.github.io` respectively.
427             cd Python-Markdown.github.io
428             mkdocs gh-deploy --config-file ../markdown/mkdocs.yml --remote-branch master
479 [Python-Markdown Organization]: https://github.com/Python-Markdown
480 [Python-Markdown Code of Conduct]: https://github.com/Python-Markdown/markdown/blob/master/CODE_OF_…
481 [Python-Markdown/markdown]: https://github.com/Python-Markdown/markdown
482 [issue tracker]: https://github.com/Python-Markdown/markdown/issues
483 [syntax rules]: https://daringfireball.net/projects/markdown/syntax
489 [Markdown]: https://daringfireball.net/projects/markdown/basics
490 [docs directory]: https://github.com/Python-Markdown/markdown/tree/master/docs
511 [markdown/__meta__.py]: https://github.com/Python-Markdown/markdown/blob/master/markdown/__meta__.p…
513 [PyPI]: https://pypi.org/project/Markdown/
514 [Python-Markdown/Python-Markdown.github.io]: https://github.com/Python-Markdown/Python-Markdown.git…