Everything is a plugin
summary
Claims that even core features as plugins implement typing and paragraphs, and that CKEditor 5 uses an MV+ model with a custom tree model, view and DOM bridging. Plugins appear as classes or plain functions; real implementations require schema converters commands and lifecycle hooks. Live code shows a highlight plugin wired from schema to view. Ecosystem adds collaboration and an AI Assistant for prompt generation and a CK Box asset manager with eight webhooks for integrations.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 0:54What is CKEditor and its plugin-based architecture
- 3:22CKEditor plugin system
- 4:29CKEditor architecture
- 5:54Creating CKEditor plugins
- 8:06Plugin UI components
- 9:31Model-View-Controller design in CKEditor
- 10:38Content modeling
- 12:40CKEditor model tree
- 13:45View layer role
- 15:11Data flow in CKEditor
- 16:59Editing layer logic
- 17:23Schema and commands
- 21:15Plugin live example
- 22:41CKBox features
- 24:31CKBox webhooks
- 24:51Closing remarks
related talks
26mEverything is a plugin
26mCollaboration + Creativity CKEditor 5's Advanced Features & GPT AI Assistant
15mExplore TinyMCE: From OS to ChatGPT AI Assistant with Vue
14mWeb Components for CMS
42mHeadless CMS
28mBuilding a Better LMS, One Tiny Block at a Time
23mSimplifying Rich Text Editor Setup with the CKEditor Builder
25mPlaying with Plugins