8
0
Piotrek Koszuliński 8 лет назад
Родитель
Сommit
0c38c965f1

+ 11 - 1
docs/builds/guides/development/custom-builds.md

@@ -84,8 +84,13 @@ Either way, every plugin that you want to include in the bundle should be includ
 'use strict';
 'use strict';
 
 
 module.exports = {
 module.exports = {
-	editor: '@ckeditor/ckeditor5-editor-classic/src/classic',
+	// The editor creator to use.
+	editor: '@ckeditor/ckeditor5-editor-classic/src/classiceditor',
+
+	// The name under which the editor will be exported.
 	moduleName: 'ClassicEditor',
 	moduleName: 'ClassicEditor',
+
+	// Plugins to include in the build.
 	plugins: [
 	plugins: [
 		'@ckeditor/ckeditor5-presets/src/essentials',
 		'@ckeditor/ckeditor5-presets/src/essentials',
 
 
@@ -100,6 +105,11 @@ module.exports = {
 		'ckeditor5-custom-package/src/customplugin',
 		'ckeditor5-custom-package/src/customplugin',
 		'../relative/path/to/some/othercustomplugin'
 		'../relative/path/to/some/othercustomplugin'
 	],
 	],
+
+	// UI language. Language codes follow the https://en.wikipedia.org/wiki/ISO_639-1 format.
+	language: 'en',
+
+	// Editor config.
 	config: {
 	config: {
 		toolbar: [ 'headings', 'bold', 'italic', 'custombutton' ]
 		toolbar: [ 'headings', 'bold', 'italic', 'custombutton' ]
 	}
 	}

+ 5 - 4
docs/builds/guides/integration/basic-api.md

@@ -13,9 +13,9 @@ Each CKEditor 5 build provides a class that handles the creation of editor insta
 
 
 The following are creator class names for each build:
 The following are creator class names for each build:
 
 
-* Classic Editor – {@link module:editor-classic/classiceditor~ClassicEditor}
-* Inline Editor – {@link module:editor-inline/inlineeditor~InlineEditor}
-* Medium-like Editor – {@link module:editor-medium-like/mediumlikeeditor~MediumLikeEditor}
+* Classic editor – {@link module:editor-classic/classiceditor~ClassicEditor}
+* Inline editor – {@link module:editor-inline/inlineeditor~InlineEditor}
+* Editor with balloon toolbar (Medium-like) – {@link module:editor-balloon-toolbar/balloontoolbareditor~BalloonToolbarEditor}
 
 
 Most of the examples in the documentation use the `ClassicEditor` class, but things should work in a similar way with other creator classes.
 Most of the examples in the documentation use the `ClassicEditor` class, but things should work in a similar way with other creator classes.
 
 
@@ -54,7 +54,8 @@ In the HTML code:
 In the script:
 In the script:
 
 
 ```js
 ```js
-ClassicEditor.create( document.querySelector( '#text-editor' ) )
+ClassicEditor
+	.create( document.querySelector( '#text-editor' ) )
 	.then( editor => {
 	.then( editor => {
 		console.log( editor );
 		console.log( editor );
 	} )
 	} )

+ 1 - 1
docs/builds/guides/integration/installation.md

@@ -49,7 +49,7 @@ The following are the main files available in all build distributions:
 
 
 * `build/ckeditor.js` – The main UMD distribution script, containing the editor core and all plugins. Compatible with ECMAScript 6 enabled browsers. A smaller download.
 * `build/ckeditor.js` – The main UMD distribution script, containing the editor core and all plugins. Compatible with ECMAScript 6 enabled browsers. A smaller download.
 * `build/ckeditor.compat.js` – The same as the above, for browsers not compatible with ES6.
 * `build/ckeditor.compat.js` – The same as the above, for browsers not compatible with ES6.
-* `ckeditor.js`: – The source entry point of the build. It can be used for complex bundling and development.
+* `ckeditor.js` – The source entry point of the build. It can be used for complex bundling and development.
 
 
 ## Loading the API
 ## Loading the API
 
 

+ 1 - 1
docs/builds/guides/integration/plugins.md

@@ -11,7 +11,7 @@ order: 40
 
 
 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.
 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 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) packages contains {@link TODOfeatures/image several granular plugins}).
 
 
 ## Common use cases
 ## Common use cases