Path to extensibility

Created on 11 February 2021, almost 4 years ago
Updated 23 November 2023, about 1 year ago

Problem/Motivation

The core CKEditor implementation defines a plugin type, CKEditorPlugin, that can be used to extend the core functionality. Several subsystems, including the Media Library module leverage this in order to provide additional functionality.

Currently, there is no parallel path set up for TinyMCE.

Proposed resolution

Very rough idea - please revise as needed! If this looks good, maybe we can open some sub-issues to nail down each in greater detail.

  • Create a plugin-based approach to extensibility, using the CKEditor core module as a guide
  • Write some tests for the plugin, plugin manager, annotations, etc...
  • Create several default implementations that ship with the TinyMCE module.
  • Write up some examples and documentation surrounding the new extensibility.

Remaining tasks

TBD

User interface changes

TBD

API changes

New plugin type, plugin manager, etc...

Data model changes

TBD

🌱 Plan
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States luke.leber Pennsylvania

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¬πŸ‡§United Kingdom 2dareis2do

    It looks as this issue is stuck after about 3 years. What is the status of this?

    From what I can tell TinyMCE is a superior product that ckeditor and also includes support for running inside a web component, something I would be quite keen to try in an attempt to improving the editor experience.

    https://www.drupal.org/project/drupal/issues/3403357 ✨ Add option to load ckeditor 5 as a web component Active

    What are the prospects of adding media entity support with tinymce in the foreseeable future? What are the blockers here?

Production build 0.71.5 2024