It is important to consider the implications regarding the workflow content authors will use when publishing content to a website via
API driven solution.
- Author does not require a WYSIWYG experience when editing and updating a particular component
- Re-usable, presentation-agnostic content, composed of structured data elements (text, dates, references, etc.
- Implemented as a DAM asset
- Used via the GraphQL Assets APIs for 3rd party consumption e.g. Trader
Content fragments drive the data model. Usually managed via AEM assets.
IFRAME in AEM author instance enables the wysiwyg expereince.
Usually managed via AEM Sites
Developer activates areas of a website for content authors to use AEM components
This is the high level architecture to allow AEM to integrate with an existing angular site.
Remote SPA Iframe Model
You must be logged in to post a comment.