- Why are people eager to do this?
- What is the value?
- What approaches do people use?
- What are their pros and cons?
- What are the most important features of such an integration?
Community page on this topic:
How to integrate Angular and React components with page editor
Notes
Philip - want to use an existing webapp - the client is the center. The cms is not at the center. But the business user still needs to change labels. How to bring the easyness of the CMS into complex applications.
Exploring more sophisticated coupling between CMS and Webapp.
Jorg - why is it not convinient, now? (content apps, etc.)
Philip - can i edit straight from my app? That would be convenient for authors.
Tomas - Map with pins (drag and drop) you can have the editor.
Alberto - Processed resources needed for some of these things. (Need to ask about that)
Adrien presents his demo.
Adriens demo is described in this section. And it includes the link to the GIT repo
How to integrate Angular and React components with page editor#PageEditorHooks
Timing issues between vaadin/page/editor and angular.
Nice addition to the page editor - that you can have "green bar scanning" at will - or when the dom updates. (Page editor has some call.)
So what our library provides is:
Recreation of magnolia Area concept.
Next:
What about image variations?
What about personalization? There is a resolver, but it is not being used yet. Not in the PoC.
Problems:
What about auto-generation of components?
Jorg: What about all of the processes that happen in Server side Magnolia Rendering.
What abour server side rendering of frontend components?
Getting JSON from JCR into nashorn - then they can build something.
I dont understand the problem - properties.
Wants to re-use FF components. But render them on the server.