- Issue created by @wim leers
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This is a follow-up for 📌 `StringSemanticsConstraint::MARKUP`: agree how SDC prop JSON schema can convey it should be markup, and Needs review and ✨ [later phase] [PP-1] Allow customization of the `xb_html_block` and `xb_html_inline` Text Formats + Text Editors Postponed .
In the future, we could expand this, by adding support for the x-allowedTags that @effulgentsia proposed in
#3467959-30: SDC and code component props should be able to receive HTML, editable in CKEditor 5 →
.
If/when that is present, we'd not use the aforementioned text formats, but instead use x-formatting-context solely as a hint for how to offer in-place editing, and generate an in-memory-only FilterFormat + Editor config entity object based on those restrictions, with corresponding CKEditor 5 plugins at their default settings, and with buttons added to the toolbar if they are needed for those HTML tags (thanks to \Drupal\ckeditor5\SmartDefaultSettings::addToolbarItemsToMatchHtmlElementsInFormat().
And/or alternatively: we could introduce a x-ckeditor5 whose value must be a value that passes the validation logic for type: editor.settings.ckeditor5. That would allow complete control by the SDC developer, at the cost of very complex metadata.
The point of all this: thinking through what it'd mean to go much further in allowing SDC developers to specify the authoring experience for Content Creators.
TBD
TBD
Postponed
0.0
Shape matching
