inserted in every other layout in the layout family. This is much easier than manually
adding the new page to each layout one-at-a-time.
When you create a layout family, QuarkXPress displays the project in a split view. You
don't have to work on the layout in split view, but it can be helpful when you're trying to
keep different editions of a page consistent.
Another helpful feature for App Studio issues is the shared content feature. This feature
lets you put copies of a picture or a chunk of text into different layouts, and then
automatically keep the copies synchronized. So, for example, if you correct a name on
page five of one layout, the name can be automatically corrected in all of the other layouts
too. For more information, see "Working with shared content" in A Guide to QuarkXPress
and "Synchronizing content between orientations."
Understanding App Studio publishing
How does content make it onto your customers' iPad? To understand how App Studio
issues are delivered to App Studio apps, you must understand how the Quark App Studio
Publishing Portal (http://appstudio.quark.com) works.
Each App Studio app you create can host one or more titles or collections.
• A title is a periodical, such as a magazine or newspaper.
• A collection is a group of related non-periodical issues. For example, if you are releasing a
group of related books that you want to make available in a particular app, you could put
them into a collection.
Assuming that the app template you use supports it, you can publish one or more titles
and/or collections in an app. Also, you can distribute a particular title or collection through
more than one app.
An issue is a particular member of a title or collection. For example, if you release a given
title monthly, you would be creating twelve issues of that title per year.
You can create an App Studio issue in QuarkXPress, export it from QuarkXPress as an App
Studio issue (.zave) file, and then upload the .zave file to your Web server. Your customers
can then purchase and download the issue from within your app.
An App Studio issue file has a .zave suffix, but is actually a ZIP archive that contains all of
the assets and data used by the issue.
Each issue has an issue type. The issue type represents a particular type of issue with its
own price point. For example, for a title that represents a magazine, you might have one
issue type for regular issues, plus a second issue type for special issues that cost a little bit
more. (The issue type for regular issues is called the default issue type.) For a book collection,
you might have a default issue type for regular books, plus an additional issue type for
books that cost more because they have more pages or are by a particular author. You can
name issue types any way you like.
A GUIDE TO APP STUDIO 9.2 | 9
UNDERSTANDING APP STUDIO