ckeditr5 README.md-CSDN博客

CKEditor 5 [外链图片转存失败(img-5GF1Tsng-1562216716351)(https://img.shields.io/twitter/url/http/shields.io.svg?style=social)]

[外链图片转存失败(img-DmAynX91-1562216716352)(https://badge.fury.io/js/ckeditor5.svg)]

[外链图片转存失败(img-qa1HMt7a-1562216716353)(https://travis-ci.org/ckeditor/ckeditor5.svg?branch=master)]
[外链图片转存失败(img-ltPDfYQ0-1562216716354)(https://automate.browserstack.com/automate/badge.svg?badge_key=d3hvenZqQVZERFQ5d09FWXdyT0ozVXhLaVltRFRjTTUyZGpvQWNmWVhUUT0tLUZqNlJ1YWRUd0RvdEVOaEptM1B2Q0E9PQ==–c9d3dee40b9b4471ff3fb516d9ecf8d09292c7e0)]
[外链图片转存失败(img-3GTt2BNW-1562216716355)(https://img.shields.io/david/ckeditor/ckeditor5.svg)]
[外链图片转存失败(img-TiHKy2M3-1562216716356)(https://img.shields.io/david/dev/ckeditor/ckeditor5.svg)]

[外链图片转存失败(img-kZ2Be2gN-1562216716358)(https://img.shields.io/badge/join-newsletter-00cc99.svg)]
[外链图片转存失败(img-UYJrdeOG-1562216716359)(https://img.shields.io/badge/follow-twitter-00cc99.svg)]

A set of ready-to-use rich text editors created with a powerful framework. Made with real-time collaborative editing in mind.

CKEditor 5 Classic rich text editor build screenshot

⚠ This package does not contain any source code

CKEditor 5 is distributed as four ready-to-use rich text editor builds which you can install from npm.

You can also customize the existing builds or build your own editors and features by using the CKEditor 5 Framework.

Quick start
- CKEditor 5 Builds
- CKEditor 5 Framework
Documentation and FAQ
Contributing and project organization
Releases
Packages
License

Quick start

CKEditor 5 Builds

CKEditor 5 Builds are a set of ready-to-use rich text editors. Every “build” provides a single type of editor with a set of features and a default configuration.

The following CKEditor 5 Builds are currently available:

Example

Creating an editor using a CKEditor 5 build is very simple and can be described in two steps:

Load the desired editor via the <script> tag.
Call the static create() method to create the editor.

In your HTML page add an element that CKEditor should replace:

<textarea name="content" id="editor"></textarea>

Load the classic editor build (you can choose between CDN, npm and zip downloads):

<script src="https://cdn.ckeditor.com/ckeditor5/<version>/classic/ckeditor.js"></script>

Call the ClassicEditor.create() method:

<script>
    ClassicEditor
        .create( document.querySelector( '#editor' ) )
        .catch( error => {
            console.error( error );
        } );
</script>

You’re ready to go!

To find out how to start with other builds check the Quick start guide in the CKEditor 5 documentation.

CKEditor 5 Framework

CKEditor 5 Builds allow you to quickly and easily initialize one of the many types of editors in your application. At the same time, CKEditor 5 is also a framework for creating custom-made rich text editing solutions.

To find out how to start building your own editor from scratch go to CKEditor 5 Framework overview section of CKEditor 5 documentation.

Documentation and FAQ

To find out more see the following CKEditor 5 documentation sections:

The documentation is far from being complete and will be constantly evolving (as will the editor) until it is ready for v1.0.0.

For FAQ please go to the CKEditor Ecosystem help center.
For a high-level overview of the project see the CKEditor Ecosystem website.

Contributing and project organization

Ideas and discussions

The main development repository of CKEditor 5 is located at https://github.com/ckeditor/ckeditor5. This is the best place for bringing opinions and contributions. Letting the core team know if they are going in the right or wrong direction is great feedback and will be much appreciated!

Development

CKEditor 5 is a modular, multi-package, multi-repository project. It consists of several packages that create the editing framework, based on which the feature packages are implemented.

The ckeditor5 repository is the place that centralizes the development of CKEditor 5. It bundles different packages into a single place, adding the necessary helper tools for the development workflow, like the builder and the test runner. Basic information on how to set up the development environment can be found in the documentation.

See the official contributors’ guide to learn how to contribute your code to the project.

Reporting issues and feature requests

Each repository handles its issues independently. However, it is recommended to report issues in this repository unless you know to which specific repository the issue belongs.