Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (for example, React). Learn more.
Content Management actions are the building blocks that help to create and manage content within an application. The following actions are performed on content within the application.
Collections represent a well defined bucket filled with content such as articles or banners that suits the cover’s theme.
The general workflow to create a collection is as follows:
Existing Mobile On-Demand content may be downloaded (Imported) from Mobile On-Demand to AEM. This allows local content editing and viewing.
Importing does not include images.
The workflow to import a new Collection
Associate a Mobile On-Demand connection first.
Use the built in AEM drag and drop editor to add or change an article. Components such as text and images can be added/removed. Images from DAM Assets can be inserted.
The workflow to edit a collection:
Collections have numerous properties such as titles, descriptions, images. This action is used to view and modify such properties. Optionally, these changes can be uploaded to Mobile On-Demand upon save.
The general workflow to view/edit a collection:
From Mobile, choose your Mobile On-Demand app from the catalog.
Choose a collection from the Manage Collections tile.
Select Properties from the action bar.
View all available meta data for that article.
Edit the meta data if desired and click Save when done.
Optionally, upload the changes immediately to Mobile On-Demand.
The uploading action copies the selected content and adds it to a Mobile On-Demand project. Already existing Mobile On-Demand content is replaced by the new version.
The general workflow to upload a collection:
This operation deletes the selected collection from Mobile On-Demand, and optionally from the local AEM instance.
The general workflow to delete a collection:
Collections are essentially a category of related content. They gather content such as articles, banners together into packages that define the navigation structure of your application. Collections can be nested.
Content must be uploaded to Mobile On-Demand before it can be added to a collection.
Collections are essentially a category of related content: They gather content such as articles, banners together into packages that define the navigation structure of your application. Collections can be nested.
One you learn about managing collections, see