Introduction to CKEditor 5 architecture
This guide introduces the main pillars of the CKEditor 5 architecture. It is assumed that you have read the Framework’s overview and saw some code in the Quick start guide. This should help you go through the next steps.
# Main components
CKEditor 5 Framework comes with its 3 main pillars:
The core editor architecture is implemented by the
@ckeditor/ckeditor5-corepackage. It consists of some core classes and interfaces that glue everything together.
The main purpose of the core editor architecture is to lay the groundwork for implementing editor features. Therefore, it introduces concepts such as plugins and commands which simplify and standardize the way of implementing features.
The editing engine is implemented by the
@ckeditor/ckeditor5-enginepackage. It is the biggest and by far the most complex piece of the framework, implementing the custom data model, the view layer, conversion mechanisms, the rendering engine responsible for taming
contentEditableand a lot more.
The standard UI library is implemented by the
@ckeditor/ckeditor5-uipackage. It contains a simple MVC implementation whose main goal is to best fit the CKEditor 5 needs. Furthermore, it introduces basic UI components to be used by editor features.
Every day, we work hard to keep our documentation complete. Have you spotted outdated information? Is something missing? Please report it via our issue tracker.