13 December 2013
Note: If you have questions about this article, use the comments feature at the bottom of the article. Please don’t contact technical support with questions about Adobe Developer Connection articles.
Media Publisher is a module for the Adobe Experience Manager that allows the system to publish content to the Adobe Digital Publishing System. Once AEM and the module are configured and using the appropriate templates, you can publish folios to DPS. Articles can be uploaded directly to the Adobe Folio Producer service and can continually check to make sure articles are in sync with the latest changes.
Contact your Adobe representative for more information about AEM and Media Publisher access.
Prior to publishing any content to DPS, you must configure the system to be able to publish to a DPS account. AEM can easily publish content to many accounts, allowing you to manage content for many different apps, if that is your need. Minimally, you need an active Adobe ID account that is configured for DPS.
As a start you might want to publish to a test account and manage the folio on the Folio Producer Web site.. You can also publish directly to an application account. In either case, you would need to make the content live in the app in the Folio Producer by selecting the folio and clicking the Publish button.
To create a configuration in AEM to publish, follow the menus in AEM to “Adobe Digital Publishing Suite” in “Cloud Services.” Tools>Cloud Services> Adobe Digital Publishing Suite> Show Configurations
Create a new Configuration and name it something meaningful – as you or your users will refer to this name when publishing content to the folio producer. On the following screen, enter the account Adobe ID and password.
This assumes you have a default configuration with the demonstration content. Content that is published into DPS is structured into Folios. A folio is a group of articles. In order for an article to be created for inclusion into a folio, it does need to start from a template that was specifrically designed for DPS. The reason for this is that there is additional information and metadata that is required by the DPS service for it to be rendered properly in the app.
With the demo content, there are existing DPS templates that can be used. For further information on template creation please visit the AEM developer site here.
In the opening screen choose Publications and click the Plus sign at the top of the screen:
The figure above shows you where to go within AEM to create a new folio. It will then step you through the process of creating a folio by entering the appropriate information and properties on each screen. Folio Name, Folio Number, and Publication name are required; you will also have the opportunity to create a publishing configuration if you did not do so per above.
You also have the opportunity to specify orientation and cover preview images. Once done, click Create at the upper right.
Once the folio is created, you can add articles. The illustration below has two articles already created. To create an article, once again click the Plus sign and fill out the appropriate info. This will drive you to a page that where you choose a template. This page will be poplutated with as many templates that you as a user have access to.
Once you choose the template, you complete the creation process by naming the page and article.
You can return to this screen to edit or change the template or other information about the page by selecting the article and clicking the ‘i’ button. Among the settings that can be changed here is flagging an article as an ad or suppressing it from the TOC in the app.
When you have finished adding articles, you will want to push the folio to the Folio Producer service. This will allow you to view the content on a device using the Adobe Content Viewer when it is logged into the same account where the content was pushed.
To push the content to the folio producer, select the folio as in Figure 6 below and click the publish icon. Assuming you associated the folio with a publish configuration as previously described, your folio with enter a AEM workflow and be pushed to the DPS folio producer site. You can associate it with a configuration at this time too.
You will be notified upon completion in your AEM inbox.
You can add or edit an existing page by clicking on it amd dragging new content in from the column at left where the assets can be viewed. These assets can be photos, manuscripts, or movies. Templates define the type and treatment of content.
You also have the ability to edit content in context such as cropping photos or editing copy.
Using the sidekick, the window with the green menu bar, you can interact with the content and the page in several ways. One of them allows you to preview the content to the size of the destination device (see figure below).
You can push the incremental changes you made to the folio by selecting the page, selecting the publish button.
AEM in this configuration will not publish directly to your finished app. You must log on to the folio producer and publish from there. You can edit, add metadata, share a folio created in AEM from the folio producer site just as if you had created the folio using the InDesign toolset. You can in fact mix content here, some from InDesign and some from AEM should your business need require both high design from InDesign and flexible publishing from AEM.
For further information please see:
Comments are currently closed as we migrate to a new commenting system. In the interim, please provide any feedback using our feedback form. Thank you for your patience.