ソースを参照

Docs: Replaced duplicatedFramework Support guides with imports from Builds. [skip ci]

Anna Tomanek 7 年 前
コミット
b7dc71f3aa

ファイルの差分が大きいため隠しています
+ 1 - 51
docs/framework/guides/support/browser-compatibility.md


+ 1 - 43
docs/framework/guides/support/getting-support.md

@@ -4,46 +4,4 @@ order: 30
 menu-title: Getting support
 ---
 
-# Getting support
-
-## GitHub
-
-You can report issues and feature requests on [GitHub](https://github.com/ckeditor/ckeditor5). This is also a good place to discuss architecture decisions and things which are not yet covered by the documentation.
-
-[Each CKEditor 5 repository](https://github.com/ckeditor?utf8=%E2%9C%93&q=ckeditor5&type=&language=) handles its issues independently. Unless you are sure where your ticket belongs, it is best to report it in the [main repository](https://github.com/ckeditor/ckeditor5).
-
-Refer to {@link framework/guides/support/reporting-issues Reporting issues} guide for more details.
-
-## Stack Overflow
-
-[Stack Overflow](https://stackoverflow.com) is the best place for developers to share their problems and solutions.
-
-Make sure to tag your questions with ["ckeditor"](https://stackoverflow.com/questions/tagged/ckeditor) and ["ckeditor5"](https://stackoverflow.com/questions/tagged/ckeditor5) to reach the widest audience.
-
-## Gitter
-
-[CKEditor 5 Gitter channel](https://gitter.im/ckeditor/ckeditor5) is the place where you can discuss all matters which do not fit GitHub and Stack Overflow.
-
-Gitter is convenient for asking quick questions, however, it is not the best place for more complex topics which might interest other developers (Gitter logs are indexed via Google but rather poorly). Therefore, try to avoid lengthy discussions on topics which would make sense to be reported either on GitHub or Stack Overflow.
-
-DOs:
-
-* Is it a known bug that "..."?
-* Do you plan to tag the new release this week?
-* I can't find XYZ's documentation. Is it available somewhere?
-* I'm in Warsaw. Anyone for a coffee?
-
-DON'Ts:
-
-* How to extend the selection to the end of the block?
-* Could you implement support for XYZ?
-* I can't make X and Y work together in my app. I developed this plugin and...
-* The editor crashes if I press Enter. Please help.
-
-And most importantly, be kind to everyone.
-
-## Commercial support
-
-CKEditor 5 also comes with commercial licensing benefits, such as direct support from the core CKEditor development team. Commercial licenses are designed with professionals and enterprises in mind.
-
-For more information, check the [CKEditor 5 Pricing page](https://ckeditor.com/ckeditor-5-builds/pricing/).
+{@importguide builds/guides/support/getting-support}

+ 1 - 19
docs/framework/guides/support/reporting-issues.md

@@ -8,22 +8,4 @@ category: framework-support
 order: 40
 ---
 
-# Reporting issues
-
-If you feel you found an issue in CKEditor 5, we will be grateful for letting us know. Before you create a bug report, however, please read our guidelines on how to do it properly and most efficiently.
-
-## Reproduce on official examples
-
-To eliminate the chance that the issue might be caused by some third-party software or your customizations, try to reproduce the issue on the {@link examples/index official examples} first.
-
-The examples are always running the latest editor version. Please note that if the problem was fixed in one of the releases that succeeded the version you are using, you will need to upgrade your CKEditor 5 installation as we do not backport fixes.
-
-Most of the issues are reproducible on the demo. If you have a different case though, no problem. Go ahead with the next steps.
-
-## Reporting issues
-
-All issues should be reported in the [CKEditor 5 repositories](https://github.com/ckeditor?q=ckeditor5) on GitHub.
-
-Issues related to builds are usually caused by issues in the CKEditor 5 Framework components and plugins included in the build. You may report issues directly into the repositories that you think are related to them (like plugins) but, if you are unsure, the [`ckeditor5` issues page](https://github.com/ckeditor/ckeditor5/issues) should be used as the fallback place for any issue. The CKEditor 5 team will then move the issue to the right place or give you further instructions, if necessary.
-
-Issues with third-party plugins should be reported directly to their developers.
+{@importguide builds/guides/support/reporting-issues}