CKEditor 5 Framework overview
CKEditor 5 is a project that allows you to quickly and easily initialize one of the many types of editors it offers in your application. At the same time, it is a framework for creating custom-tailored rich-text editing solutions. The former requirement is met thanks to the predefined CKEditor 5 builds. The latter — thanks to CKEditor 5 Framework.
CKEditor 5 Framework is a highly-flexible and universal platform that provides a set of components allowing you to create any kind of rich text editing solution. It enables the building of different, custom-tailored editors that suit specific needs. It also provides tools for the creation and integration of user-made features and for customizing existing ones.
This guide explains how the framework is built and how to start using it.
Please note that the CKEditor 5 Framework documentation is constantly updated and expanded, but it may still be lacking some things. Feel free to suggest documentation enhancements and share your feedback about the framework.
If the documentation is insufficient, do not be afraid to look into the source code of CKEditor 5 packages. For example, if you plan to create a new feature, check if a similar one already exists and try to take inspiration from its source code.
# When to use the framework?
The CKEditor 5 predefined builds can be customized, but certain types of customizations require using the framework.
- Writing your own features. New features are implemented using the framework.
- Customizing existing features. Changing the behavior or look of existing features can be done thanks to the framework’s capabilities.
- Creating new types of editors. You can create new editor types using the framework.
To sum up: you need to start using the framework as soon as existing builds do not meet your requirements or cannot be customized to the extent you need.
The framework was designed to be a highly flexible and universal platform for creating custom rich-text editing solutions. At the same time, it meets several goals that make implementing features as easy a task as possible.
- Plugin-based architecture. Everything is a plugin — even such crucial features as support for typing or
<p>elements. You can remove plugins or replace them with your own implementations to achieve fully customized results.
- Schema-less core. The core makes minimal assumptions and can be controlled through the schema. This leaves all decisions to plugins and hence to you.
- Collaboration-ready. Or rather, real-time collaboration is ready for you to use! The editor implements Operational Transformation for the tree-structured model as well as many other mechanisms which were required to create a seamless collaborative UX. Additionally, we provide cloud infrastructure and plugins enabling real-time collaborative editing in your application! Check the collaboration demo.
- Custom data model. The editing engine implements a tree-structured custom data model, designed to fit multiple requirements such as enabling real-time collaboration and complex editing features (like tables or nested blocks).
- Virtual DOM. The editing engine features a custom, editing-oriented virtual DOM implementation that aims to hide browser quirks from your sight. No more
- TypeScript. The project is written in TypeScript and provides native type definitions. This helps create better, more reliable code that’s easier to understand and maintain.
- Granular, reusable features. Features are implemented in a granular way. This allows for reusing and recomposing them which, in turn, makes it possible to customize and extend the editor. For instance, the image feature consists of over 10 plugins at the moment.
- Extensibility. The entire editor architecture was designed for maximum flexibility. The code is event-based and highly decoupled, allowing you to plug in or replace selected pieces. Features do not directly depend on one another and communicate in standardized ways.
- A beautiful UI. Text editing is not only about typing — your users will need a UI to create links or manage images. We believe that a proper UX needs to be carefully designed and we did not skip this part. Having second thoughts about the proposed UI? No problem at all! You can always create your custom interface for CKEditor 5 thanks to its decoupled UI.
- Quality. All official packages have extensive test suites (100% code coverage is merely a step to that). All code has extensive API documentation.
- Minimal configuration. To avoid bloat, features have minimal configuration. Deeper changes in their behavior can be done by recomposing them with custom features.
- 8+ years of support. It is not yet another framework to be gone next year or a hyped proof-of-concept to fail in a real-life scenario. We have over 20 years of experience in creating rich-text editors and continue working day in and day out on improving your future-proof rich-text editor of choice.
# Framework structure
There are a few groups of packages:
- Core libraries – A set of packages which are the root of the framework.
- Editors – Packages that implement various types of editors.
- Features – Packages that implement end-user features.
- Themes – Packages that implement editor themes.
- Builds – Packages containing CKEditor 5 builds.
# What’s next?
To start using the framework refer to: