You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to have a new package: @plone/editor that contains the CMSUI as a standalone app.
Motivation
This will allow the completely detach of the CMSUI from the public UI. This will allow the public build to be far more lightweight and simplify the requirements and the performance of it.
You could then deploy the CMSUI as a separate app, or have it in a desktop app or mobile app.
This can allow to integrate the CMSUI in any existing React app, by pulling it and instantiate it properly.
We will try to overcome at the same time some problems that we have in the current editor implementation and separate the "Form" component from the Block Engine. Also we should have a close attention to the performance of the block rendering and updates.
It's still due to be decided how the editor will get the custom CSS from a project and apply it to the editor. Probably using the project add-on and load it along (as you'll do it in the public UI side).
The nature of the add-ons will allow us to have hybrid add-ons working in the public UI (whatever it is) and the editor app.
Deliverables
@plone/editor package.
Documentation on how to use it, configure it and deploy it.
PLIP (Plone Improvement Proposal)
Responsible Persons
Proposer: Víctor Fernández de Alba (@sneridagh)
Seconder: Piero Nicoli (@pnicolli)
Abstract
The goal is to have a new package:
@plone/editor
that contains the CMSUI as a standalone app.Motivation
This will allow the completely detach of the CMSUI from the public UI. This will allow the public build to be far more lightweight and simplify the requirements and the performance of it.
You could then deploy the CMSUI as a separate app, or have it in a desktop app or mobile app.
This can allow to integrate the CMSUI in any existing React app, by pulling it and instantiate it properly.
Assumptions
No assumptions.
Proposal & Implementation
The editor will have to be SemanticUI free:
Using
@plone/components
we will implement a UI using BMv3:We will try to overcome at the same time some problems that we have in the current editor implementation and separate the "Form" component from the Block Engine. Also we should have a close attention to the performance of the block rendering and updates.
It's still due to be decided how the editor will get the custom CSS from a project and apply it to the editor. Probably using the project add-on and load it along (as you'll do it in the public UI side).
The nature of the add-ons will allow us to have hybrid add-ons working in the public UI (whatever it is) and the editor app.
Deliverables
@plone/editor
package.Documentation on how to use it, configure it and deploy it.
Risks
No risks.
Participants
Víctor Fernández de Alba (@sneridagh)
The text was updated successfully, but these errors were encountered: