Acknowledge that the available parsers are not compatible with GitHub…

[jsoref]

…'s markdown

Why:

Closes: #34334

What's being changed (if available, include any code snippets, screenshots, or gifs):

before

after

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[jsoref]

This PR is frustrating. It's virtually impossible for me to imagine any text that properly explains what's going on and I really wish the GitHub product team would take responsibility for writing the text instead of asking a community member to try to politely say that their stuff doesn't do what it used to claim to do.

The year is a rough estimate and is partially designed to give people a sense of how out of date the two systems might be. I know that stuff from 2021 isn't supported. For all I know it was out of date in 2016 or 2010.

• Table of Contents was a 2021 feature

[nguyenalex836]

@jsoref Thanks so much for opening a PR! I'll get this triaged for review ✨

[nguyenalex836]

@jsoref Hello! 👋 After reviewing your PR, our team would like to update the wording to read:

You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor.

This will provide the reader sufficient information without overloading them with too much context. Let us know if you have any concerns 💛 Otherwise, we can update this PR in a few days and get this merged ✨

[nguyenalex836]

@jsoref Thank you for updating your PR! Getting this merged shortly 💛

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡