From 76d121d484ec20f1abda2a48b17ddde7bab4e12e Mon Sep 17 00:00:00 2001 From: Tyler Kelly Date: Wed, 6 May 2020 16:41:59 +1000 Subject: [PATCH] s/markdown/kramdown/g and s/docs/docs-4x/g --- CONTRIBUTING.md | 8 ++++---- advanced/contributing-docs.md | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6cc4709..a85bdd5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,7 +4,7 @@ This page outlines how you can provide feedback and contribute to TinyMCE docume ## Contributor Code of Conduct -For our Contributor Code of Conduct, visit our [Contributor Covenant Code of Conduct on GitHub](https://github.com/tinymce/tinymce-docs/blob/develop/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). +For our Contributor Code of Conduct, visit our [Contributor Covenant Code of Conduct on GitHub](https://github.com/tinymce/tinymce-docs-4x/blob/develop/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). ## How to contribute to TinyMCE's documentation @@ -16,15 +16,15 @@ We welcome people with technical writing experience to help make TinyMCE's docs What is more important is your ability to articulate complex ideas. Our goal is to help developers understand TinyMCE's functionality as quickly as possible. -Simply branch the [docs GitHub repository](https://github.com/tinymce/tinymce-docs) and submit a PR, or reach out to the [TinyMCE docs team](https://github.com/tinymce/tinymce-docs-4x/issues/new?assignees=&labels=question&template=question.md) if you have a specific question. +Simply branch the [docs GitHub repository](https://github.com/tinymce/tinymce-docs-4x) and submit a PR, or reach out to the [TinyMCE docs team](https://github.com/tinymce/tinymce-docs-4x/issues/new?assignees=&labels=question&template=question.md) if you have a specific question. ## TinyMCE documentation tech stack -The documentation is built with Jekyll. Text files are written in [Markdown](https://help.github.com/articles/markdown-basics/) and published on [GitHub](https://github.com/tinymce/tinymce-docs). You will find the [repo here](https://github.com/tinymce/tinymce-docs). +The documentation is built with Jekyll. Text files are written in [kramdown](https://kramdown.gettalong.org/) and published on [GitHub](https://github.com/tinymce/tinymce-docs-4x). You will find the [repo here](https://github.com/tinymce/tinymce-docs-4x). ## Markdown & code syntax -The documentation is written in [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). If you are not familiar with Markdown [read this](https://help.github.com/articles/markdown-basics/). +The documentation is written in [kramdown Flavored Markdown](https://kramdown.gettalong.org/). If you are not familiar with kramdown [read this](https://kramdown.gettalong.org/quickref.html). ### Highlighting diff --git a/advanced/contributing-docs.md b/advanced/contributing-docs.md index 94e5930..a4130dd 100644 --- a/advanced/contributing-docs.md +++ b/advanced/contributing-docs.md @@ -11,7 +11,7 @@ This page outlines how you can provide feedback and contribute to TinyMCE docume ## Contributor Code of Conduct -For our Contributor Code of Conduct, visit our [Contributor Covenant Code of Conduct on GitHub](https://github.com/tinymce/tinymce-docs/blob/develop/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). +For our Contributor Code of Conduct, visit our [Contributor Covenant Code of Conduct on GitHub](https://github.com/tinymce/tinymce-docs-4x/blob/develop/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). ## How to contribute to TinyMCE's documentation @@ -23,15 +23,15 @@ We welcome people with technical writing experience to help make TinyMCE's docs What is more important is your ability to articulate complex ideas. Our goal is to help developers understand TinyMCE's functionality as quickly as possible. -Simply branch the [docs GitHub repository](https://github.com/tinymce/tinymce-docs) and submit a PR, or reach out to the [TinyMCE docs team](https://github.com/tinymce/tinymce-docs-4x/issues/new?assignees=&labels=question&template=question.md) if you have a specific question. +Simply branch the [docs GitHub repository](https://github.com/tinymce/tinymce-docs-4x) and submit a PR, or reach out to the [TinyMCE docs team](https://github.com/tinymce/tinymce-docs-4x/issues/new?assignees=&labels=question&template=question.md) if you have a specific question. ## TinyMCE documentation tech stack -The documentation is built with Jekyll. Text files are written in [Markdown](https://help.github.com/articles/markdown-basics/) and published on [GitHub](https://github.com/tinymce/tinymce-docs). You will find the [repo here](https://github.com/tinymce/tinymce-docs). +The documentation is built with Jekyll. Text files are written in [kramdown](https://kramdown.gettalong.org/) and published on [GitHub](https://github.com/tinymce/tinymce-docs-4x). You will find the [repo here](https://github.com/tinymce/tinymce-docs-4x). ## Markdown & code syntax -The documentation is written in [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). If you are not familiar with Markdown [read this](https://help.github.com/articles/markdown-basics/). +The documentation is written in [kramdown flavored markdown](https://kramdown.gettalong.org/). If you are not familiar with kramdown [read this](https://kramdown.gettalong.org/quickref.html). ### Highlighting