Replies: 3 comments 2 replies
-
In case you are interested, I created a Why is that important? Consider elements, such as When using images in richtext, it even becomes more complicate than that. We then need a way to store the image's payload data somewhere on disk, whereas we want the metadata (width, height, alignment, etc.) inside the document. There is no one-fits-all solution for that, we want the customer to design their model describing the values they need. In django-formset version 1.4 this will be possible. One then can create his own form definition in Python and attach it to a TipTap control element. Clicking on that button will open a dialog window with the fields declared in the mentioned form. This can be used for any kind of extra control elements inside your richtext editor. The data submitted by those dialog forms, then is merged The latter has the advantage that no such thing as "text enabled plugins" are required anymore. |
Beta Was this translation helpful? Give feedback.
-
We will also have to json-ify the data bridge: #7850 |
Beta Was this translation helpful? Give feedback.
-
From my point of view, the most important part would be the possibility to add and edit plugins into placeholder via the Django Admin. This by it self enables everyone to use the Django CMS headless by implementing the API part on it's own. This could be a good first step into a fully headlines CMS. |
Beta Was this translation helpful? Give feedback.
-
Intro
Technical considerations
Beta Was this translation helpful? Give feedback.
All reactions