8
0
Piotr Jasiun 7 лет назад
Родитель
Сommit
60a7c105e0

+ 4 - 4
docs/builds/guides/development/custom-builds.md

@@ -50,7 +50,7 @@ git remote add upstream https://github.com/ckeditor/ckeditor5-build-classic.git
 </info-box>
 
 <info-box warning>
-	It is important that you use the `stable` branch of a build, not the `master` branch. The `master` branch might contain changes which are not yet compatible with the versions of CKEditor 5 source packages which were published on npm.
+	It is important that you use the `stable` branch of a build, not the `master` branch. The `master` branch might contain changes which are not yet compatible with the versions of CKEditor 5 source packages that were published on npm.
 </info-box>
 
 ## Build anatomy
@@ -72,13 +72,13 @@ In order to customize a build you need to:
 
 ### Installing dependencies
 
-First, you need to install dependencies which are already specified in build's `package.json`:
+First, you need to install dependencies which are already specified in the build's `package.json`:
 
 ```bash
 npm install
 ```
 
-Then, you can add missing depencies (i.e. packages you want to add to your build). The easiest way to do so is by typing:
+Then, you can add missing dependencies (i.e. packages you want to add to your build). The easiest way to do so is by typing:
 
 ```bash
 npm install --save-dev <package-name>
@@ -87,7 +87,7 @@ npm install --save-dev <package-name>
 This will install the package and add it to `package.json`. You can also edit `package.json` manually.
 
 <info-box hint>
-	Due to a non-deterministic way how npm installs packages, it is recommended to run `rm -rf node_modules && npm install` when in doubt. This will prevent some packages from getting installed more than once in `node_modules/` (which might lead to broken builds).
+	Due to the non-deterministic way how npm installs packages, it is recommended to run `rm -rf node_modules && npm install` when in doubt. This will prevent some packages from getting installed more than once in `node_modules/` (which might lead to broken builds).
 
 	You can also give [Yarn](https://yarnpkg.com/lang/en/) a try.
 </info-box>

+ 1 - 1
docs/builds/guides/development/installing-plugins.md

@@ -127,7 +127,7 @@ For example, if you wish to install the text alignment feature:
 npm install --save-dev @ckeditor/ckeditor5-alignment
 ```
 
-Edit the code which initializes the editor:
+Edit the code that initializes the editor:
 
 ```js
 import ClassicEditor from '@ckeditor/ckeditor5-editor-classic/src/classiceditor';

+ 3 - 3
docs/builds/guides/development/plugins.md

@@ -12,11 +12,11 @@ order: 20
 
 Features in CKEditor are introduced by plugins. In fact, without plugins CKEditor is an empty API with no use. The builds provided with CKEditor 5 are actually predefined collections of plugins, put together to satisfy specific needs.
 
-Plugins provided by the CKEditor core team are available in [npm](https://www.npmjs.com/search?q=ckeditor5) (and [GitHub](https://github.com/ckeditor?utf8=%E2%9C%93&q=ckeditor5&type=&language=), too) in form of npm packages. A package may contain one or more plugins (e.g. the [`@ckeditor/ckeditor5-image`](https://www.npmjs.com/package/@ckeditor/ckeditor5-image) packages contains {@link features/image several granular plugins}).
+Plugins provided by the CKEditor core team are available in [npm](https://www.npmjs.com/search?q=ckeditor5) (and [GitHub](https://github.com/ckeditor?utf8=%E2%9C%93&q=ckeditor5&type=&language=), too) in form of npm packages. A package may contain one or more plugins (e.g. the [`@ckeditor/ckeditor5-image`](https://www.npmjs.com/package/@ckeditor/ckeditor5-image) package contains {@link features/image several granular plugins}).
 
 ## Common use cases
 
-Plugins can be pretty much anything. They are simply pieces of code, initialized by the editor if they are configured to be loaded. They can use the richness of the {@link api/index CKEditor 5 Framework API} to enhance the editor or to better integrate it with your application.
+Plugins can be pretty much anything. They are simply pieces of code initialized by the editor if they are configured to be loaded. They can use the richness of the {@link api/index CKEditor 5 Framework API} to enhance the editor or to better integrate it with your application.
 
 Common use cases for plugins are:
 
@@ -25,7 +25,7 @@ Common use cases for plugins are:
 * **Third-party services integration**, for injecting external resources into the content, like videos or social network posts.
 * **Handling image upload** and image manipulation features.
 * **Providing widgets** for easy integration with application structured data.
-* **Injecting analysis tools** that help enhancing the quality of the content.
+* **Injecting analysis tools** that help enhance the quality of the content.
 * And other infinite possibilities...
 
 ## Creating plugins

+ 11 - 11
docs/builds/guides/integration/advanced-setup.md

@@ -19,7 +19,7 @@ In order to start developing CKEditor 5 you will require:
 
 ## Bundler
 
-CKEditor 5 is currently built using [webpack](https://webpack.js.org) (>=3.x.x). All builds, examples and demos are generated using this bundler. It should also be possible to build CKEditor using other bundlers (if they are configured properly), such as [Rollup](https://github.com/rollup/rollup) or [Browserify](http://browserify.org/) but these setups are not officially supported yet. Also, the [`@ckeditor/ckeditor5-dev-webpack-plugin`](https://www.npmjs.com/package/@ckeditor/ckeditor5-dev-webpack-plugin) that allows to localize the editor is only available for webpack. More work on this subject will be done after v1.0.0.
+CKEditor 5 is currently built using [webpack](https://webpack.js.org) (>=3.x.x). All builds, examples and demos are generated using this bundler. It should also be possible to build CKEditor using other bundlers (if they are configured properly), such as [Rollup](https://github.com/rollup/rollup) or [Browserify](http://browserify.org/), but these setups are not officially supported yet. Also, the [`@ckeditor/ckeditor5-dev-webpack-plugin`](https://www.npmjs.com/package/@ckeditor/ckeditor5-dev-webpack-plugin) that allows to localize the editor is only available for webpack. More work on this subject will be done after v1.0.0.
 
 Therefore, **a prerequisite to this guide is that you are using webpack as your build tool**.
 
@@ -70,7 +70,7 @@ This scenario allows you to fully control the building process of CKEditor. This
 	Similar results to what this method allows can be achieved by {@link builds/guides/development/custom-builds customizing an existing build} and integrating your custom build like in scenario 1. This will give faster build times (since CKEditor will be built once and committed), however, it requires maintaining a separate repository and installing the code from that repository into your project (e.g. by publishing a new npm package or using tools like [Lerna](https://github.com/lerna/lerna)). This makes it less convenient than the method described in this scenario.
 </info-box>
 
-First of all, you need to install source packages that you will use. If you base your integration on one of the existing builds, you can take them from that build's `package.json` file (see e.g. [classic build's `package.json`](https://github.com/ckeditor/ckeditor5-build-classic/tree/master/package.json)). At this moment you can choose the editor creator and features you want.
+First of all, you need to install source packages that you will use. If you base your integration on one of the existing builds, you can take them from that build's `package.json` file (see e.g. [classic build's `package.json`](https://github.com/ckeditor/ckeditor5-build-classic/tree/master/package.json)). At this moment you can choose the editor creator and the features you want.
 
 Copy these dependencies to your `package.json` and call `npm install` to install them. The `dependencies` (or `devDependencies`) section of `package.json` should look more or less like this:
 
@@ -115,9 +115,9 @@ You may also want to install [`babel-minify-webpack-plugin`](https://github.com/
 
 ### Webpack configuration
 
-Now, you can configure webpack. There are a couple of things which you need to take care of when building CKEditor:
+You can now configure webpack. There are a couple of things that you need to take care of when building CKEditor:
 
-* Handling CSS files of CKEditor's theme. They are included in the CKEditor sources using `import 'path/to/styles.css'` statements, so you need [proper loaders](https://webpack.js.org/loaders/).
+* Handling CSS files of the CKEditor theme. They are included in the CKEditor sources using `import 'path/to/styles.css'` statements, so you need [proper loaders](https://webpack.js.org/loaders/).
 * Similarly, you need to handle bundling SVG icons, which are also imported directly into the source. For that you need the [`raw-loader`](https://webpack.js.org/loaders/raw-loader/).
 * Finally, to localize the editor you need to use the [`@ckeditor/ckeditor5-dev-webpack-plugin`](https://www.npmjs.com/package/@ckeditor/ckeditor5-dev-webpack-plugin) webpack plugin.
 
@@ -141,14 +141,14 @@ module.exports = {
 		rules: [
 			{
 				// Or /ckeditor5-[^/]+\/theme\/icons\/[^/]+\.svg$/ if you want to limit this loader
-				// to CKEditor 5's icons only.
+				// to CKEditor 5 icons only.
 				test: /\.svg$/,
 
 				use: [ 'raw-loader' ]
 			},
 			{
 				// Or /ckeditor5-[^/]+\/theme\/[\w-/]+\.css$/ if you want to limit this loader
-				// to CKEditor 5's theme only.
+				// to CKEditor 5 theme only.
 				test: /\.css$/,
 				use: [
 					{
@@ -241,7 +241,7 @@ This module will export an editor creator class which has all the plugins and co
 import ClassicEditor from './ckeditor';
 
 ClassicEditor
-	// Note that you don't have to specify the plugin and toolbar configuraiton — using defaults from the build.
+	// Note that you do not have to specify the plugin and toolbar configuraiton — using defaults from the build.
 	.create( document.querySelector( '#editor' ) )
 	.then( editor => {
 		console.log( 'Editor was initialized', editor );
@@ -387,7 +387,7 @@ In order to create an ES5 build of CKEditor 5 you can use [Babel](https://babelj
 npm install --save babel-loader babel-core babel-preset-env regenerator-runtime
 ```
 
-Then, add this item to webpack's [`module.rules`](https://webpack.js.org/configuration/module/#module-rules) section:
+Then, add this item to webpack [`module.rules`](https://webpack.js.org/configuration/module/#module-rules) section:
 
 ```js
 module: {
@@ -414,14 +414,14 @@ And load [`regenerator-runtime`](https://www.npmjs.com/package/regenerator-runti
 entry: [
 	require.resolve( 'regenerator-runtime/runtime.js' ),
 
-	// your entries...
+	// Your entries...
 ]
 ```
 
 <info-box>
-	This setup ensures that the source code is transpiled to ES5. However, it does not ensure that all ES6 polyfills are loaded. Therefore, if you would like to, for example, give [bringing IE11 compatibility](https://github.com/ckeditor/ckeditor5/issues/330) a try make sure to also load [`babel-polyfill`](https://babeljs.io/docs/usage/polyfill/).
+	This setup ensures that the source code is transpiled to ES5. However, it does not ensure that all ES6 polyfills are loaded. Therefore, if you would like to, for example, give [bringing IE11 compatibility](https://github.com/ckeditor/ckeditor5/issues/330) a try, make sure to also load [`babel-polyfill`](https://babeljs.io/docs/usage/polyfill/).
 </info-box>
 
 <info-box>
-	The [`babel-preset-env`](https://github.com/babel/babel-preset-env) package lets you choose the environment which you want to support and transpiles ES6+ features to match that environment's capabilities. Without configuration it will produce ES5 builds.
+	The [`babel-preset-env`](https://github.com/babel/babel-preset-env) package lets you choose the environment that you want to support and transpiles ES6+ features to match that environment's capabilities. Without configuration it will produce ES5 builds.
 </info-box>

+ 2 - 2
docs/builds/guides/integration/configuration.md

@@ -51,7 +51,7 @@ ClassicEditor
 	} );
 ```
 <info-box>
-Be careful when removing plugins using `config.removePlugins` from CKEditor builds. If removed plugins were providing toolbar buttons, the default toolbar configuration included in a build will become invalid. In such case you need to provide the updated toolbar configuration as in the example above.
+	Be careful when removing plugins from CKEditor builds using `config.removePlugins`. If removed plugins were providing toolbar buttons, the default toolbar configuration included in a build will become invalid. In such case you need to provide the updated toolbar configuration as in the example above.
 </info-box>
 
 ### List of plugins
@@ -83,7 +83,7 @@ ClassicEditor
 ```
 
 <info-box hint>
-	The above is a strict UI-related configuration. Removing a toolbar item does not remove the feature from the editor internals. If your goal with the toolbar configuration is to remove features, the right solution is to also remove their relative plugins. Check [Removing features](#removing-features) above for more information.
+	The above is a strict UI-related configuration. Removing a toolbar item does not remove the feature from the editor internals. If your goal with the toolbar configuration is to remove features, the right solution is to also remove their respective plugins. Check [Removing features](#removing-features) above for more information.
 </info-box>
 
 ### Listing available items

+ 1 - 1
docs/examples/index.md

@@ -9,7 +9,7 @@ meta-description: Navigate through CKEditor 5 examples to see what you are able
 # Examples
 
 <info-box>
-	Use the **navigation tree on the left** to navigate through CKEditor 5 examples.
+	Use the **navigation tree on the left** to navigate through CKEditor 5 examples. Visit the {@link features/index Features} section to see even more examples!
 </info-box>
 
 ## Related links

+ 8 - 1
docs/umberto.json

@@ -140,7 +140,14 @@
 		{
 			"name": "Features",
 			"id": "features",
-			"slug": "features"
+			"slug": "features",
+			"categories": [
+				{
+					"name": "Collaboration",
+					"id": "features-collaboration",
+					"slug": "collaboration"
+				}
+			]
 		},
 		{
 			"name": "API",