Page History
...
| Note |
|---|
Content connectors are based on the deprecated Vaadin 7, which has been replaced with Vaadin 8 since Magnolia 6.0. They are part of the Magnolia 5 UI framework. For the architectural changes in Magnolia 6, see UI framework and development pattern changes in Magnolia 6. For Vaadin 8 data binding, refer to Data source definition and Item providers. |
| HTML Wrap | ||||
|---|---|---|---|---|
| ||||
Related topics: |
The content you manage in Magnolia is typically stored in the JCR repository, but it doesn't have to be. A content connector defines where the content resides. With a content connector you can decouple content management from content storage. You can store content in a database, cloud storage or a Web service. You can create a connector that lets authors choose image assets from Flickr, for example. Authors benefit as they can manage all content in familiar Magnolia content apps. They don't have to leave Magnolia just because the content resides somewhere else.
...
Overview
Content Tools