In this example, we remove the premium collaboration features as well as several other plugins that require credentials to work. Observe the config below to see this implemented. You can learn more about obtaining and activating license keys in the License key and activation guide. There are also some plugins, like the Productivity Pack, that require a license to run. Apart from that exception, the editor initialization is no different than the one described in the available builds documentation.īecause the superbuild contains a lot of plugins, you may need to remove the plugins you do not need with the removePlugins configuration option and adjust the toolbar configuration. In the superbuild, all editor classes are stored under the CKEDITOR object. You can also try out the predefined builds tailored for specific needs. We strongly advise using the Online builder approach or building the editor from source to create customized and efficient production-environment solutions. A good portion of that code may not be needed in your implementation, so using the superbuild should be considered for evaluation purposes and tests rather, than for the production environment. Please consider, that the superbuild contains a really whole lot of code. create( document.querySelector( '#editor' ) )Ī full webpage with embedded CKEditor 5 from the above example would look like this: Ĭall the ClassicEditor.create() method to display the editor. Load the classic editor build (here a CDN location is used). In your HTML page add an element that will serve as a placeholder for a CKEditor instance: Let us run a classic editor build as an example.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |