caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
2.1 KiB
title, intro, redirect_from, product, versions
| title | intro | redirect_from | product | versions | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Setting a Markdown processor for your GitHub Pages site using Jekyll | You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site. |
|
{% data reusables.gated-features.pages %} |
|
People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site.
{% data variables.product.prodname_pages %} supports two Markdown processors: kramdown and {% data variables.product.prodname_dotcom %}'s own extended CommonMark processer, which is used to render {% data variables.product.prodname_dotcom %} Flavored Markdown throughout {% data variables.product.product_name %}. For more information, see "About writing and formatting on {% data variables.product.prodname_dotcom %}."
You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our CommonMark processor will always match the results you see on {% data variables.product.product_name %}.
{% data reusables.pages.navigate-site-repo %}
2. In your repository, browse to the _config.yml file.
{% data reusables.repositories.edit-file %}
4. Find the line that starts with markdown: and change the value to kramdown or GFM.
{% data reusables.files.write_commit_message %}
{% data reusables.files.choose-commit-email %}
{% data reusables.files.choose_commit_branch %}
{% data reusables.files.propose_new_file %}