Digital Publishing Suite
From Ledet Training Wiki
(→Best practices for creating Digital Publishing Suite documents) |
(→Buttons) |
||
| (One intermediate revision not shown) | |||
| Line 30: | Line 30: | ||
===Hyperlinks=== | ===Hyperlinks=== | ||
| - | Hyperlinks can be to URL's, email addresses | + | Hyperlinks can be to URL's, email addresses, and Navto links to a different pages within a stack or a file on the mobile device. If a hyperlink is to an app in the app store, use itms:// but turn off View in Context. If linking to a page within a stack, numbering starts at 0, so navto://article#1 will link to the second page of the article. |
===Buttons=== | ===Buttons=== | ||
| - | Buttons can only have a single action associated with | + | To use Buttons in a DPS .folio document, use the Window>Interactive>Buttons panel. Buttons can only have a single action associate, which must be associated with the On Release event. Supported Actions are: |
* Go To Destination | * Go To Destination | ||
* Go To First Page | * Go To First Page | ||
Latest revision as of 13:33, 11 February 2011
Adobe Digital Publishing Suite (DPS) is an enterprise level content publishing system designed to allow publishers to make content available on mobile devices. It is based on Adobe InDesign. It is best suited to publishers seeking to publish interactive content in a magazine format.
Contents |
[edit] Parts of the Adobe Digital Publishing Suite
The Suite includes several components. Adobe InDesign is the central component of the workflow. InDesign users work with an Overlay Creator panel to add rich tablet based functionality to their layouts. An Adobe AIR based application called Content Bundler is then used to convert InDesign files to a .folio format file. The Content Bundler requires the Digital Publishing Plugin for Adobe InDesign in order to convert InDesign files to .folio files. This file is read by the Adobe Content Viewer which can be custom branded as an Apple (or other mobile provider) application. The Adobe Desktop Viewer is a preview application capable of reading .folio files prior to publishing them to a mobile device.
[edit] Design of Digital Publishing Suite documents
Each article (or ad) within a .folio issue is called a stack. The design of each stack should have a horizontal (1024x768px) and a vertical (768x1024px) design. Stacks can be created as either inDesign documents or as HTML files.
When a document is bundled, all non-interactive page items are flattened into a single image file. Interactive items appear on top of the flattened image as overlays. Interactive objects can include video, audio, 360-degree photographic views, panoramas, hyperlinks, image pans, and slideshows.
[edit] Folder structure for bundler
In order for Content Bundler to correctly create a .folio issue, a certain folder structure and naming conventions must be followed. Each stack must have its own folder inside a folio folder. Inside these stack folders, horizontal InDesign documents must be named with an _h suffix and vertical InDesign documents must be named with an _v suffix. (For example, "article1_h.indd" and "article1_v.indd")
[edit] Best practices for creating Digital Publishing Suite documents
- Turn off facing pages.
- Use pixels for unit of measurement.
- Choose Web from the Intent pop-up menu when creating a new document.
- Use properly sized JPEG and PNG files for all interactive assets. All non-interactive assets are compressed and converted into a single image, but overlay resources are not downsampled. Most overlay resources should use JPEG images with medium (50-80%) compression for smallest file sizes, rather than PNG. For small text, PNG should be used.
- Use guides for object alignment.
- Create shared text using an InCopy .icml file (Edit>InCopy>Export>Selection, then Place)
- Use RGB color images
- Do not run objects into the bleed area.
- Use Smooth Scrolling for long articles.
[edit] Interactivity in Digital Publishing Suite
Digital Publishing Suite .folio files can contain audio, video, slideshows, hyperlinks (to web pages, email addresses, or local files on the mobile device), image pans, scrollable content, 360 views, panoramas, and web views. These interactive features are edited using the Overlay Creator panel.
[edit] Multi-State Objects
Multi-State Objects (MSOs) are used to create slideshows.
[edit] Hyperlinks
Hyperlinks can be to URL's, email addresses, and Navto links to a different pages within a stack or a file on the mobile device. If a hyperlink is to an app in the app store, use itms:// but turn off View in Context. If linking to a page within a stack, numbering starts at 0, so navto://article#1 will link to the second page of the article.
[edit] Buttons
To use Buttons in a DPS .folio document, use the Window>Interactive>Buttons panel. Buttons can only have a single action associate, which must be associated with the On Release event. Supported Actions are:
- Go To Destination
- Go To First Page
- Go To Last Page
- Go To URL
- Go To Page
- Go To State
- Go To Previous State
- Go To Next State
[edit] Audio
MP3 files are supported. Looping and streaming is not supported.
[edit] Video
Looping and streaming is not supported.
[edit] Panoramas
The Panorama tools, also known as PanoTools are a set of free programs and libraries for re-projecting and blending multiple source images into immersive panoramics of many types.
