Login

Learning&Support

Documentation

Export

Twixl Support Team Updated: - Created :

Export a single article or a complete publication or separate articles.

In general

Once you have finalized your design, and have added the interactive elements you wanted to include, you can select "Export article" or "Export Publication…", available from the Twixl Publisher palette.

Export from InDesign

Choose a destination for the export package and click OK. The Twixl Publisher plug-in will now export all contents (possibly different versions for landscape and portrait, or for different platforms…

1. .article file

One InDesign document -> .article file

If you are exporting one article, then a package file with the extension .article will be generated.

2. .publication

Complete InDesign book -> .publication file

For a complete publication export, a package file with the extension .publication will be created.

 

TIP ABOUT .PUBLICATIONS AND THE TWIXL DISTRIBUTION PLATFORM:

A .publication file can also be used for an article-based app, because you can import .publications on the Twixl Distribution Platform.

3. separate .articles

Complete InDesign book -> separate .article files

You can also export all member of your book (.publication ) as separate .articles .

TIP ABOUT EXPORTING AS SEPARATE ARTICLES:

InDesign has always been very buggy when it's about exporting book-files. Most of the times they are caused by too many book-members, too many fonts, etc. This also influences export-actions from Twixl Publisher. If your InDesign book fails to export, you can also use this functionality to export separate articles and avoid crashes. You can even combine them into a .publication afterwards, using the Twixl Publisher Publication Composer!

ABOUT WINDOWS:

On Windows the package file will appear as a folder.

PREFLIGHT:

When exporting an article or a publication, Twixl Publisher will always start a preflight check first. If the plug-in detects a problem, depending on the severity, you may or may not choose to continue the Export.

About Web Resources and different ways of exporting

Web Resources are used to embed content (mostly html-content) in a .publication or .article . They are also used in case of share content (e.g. movie that is used a lot in different .articles). Different Export options have different consequences. We explain them briefly here:

1. How are Web Resources being exported?

  1. Exporting a .article that is part of an InDesign-book:  The Web Resources folder of the InDesign-book will be completely integrated in the export of your .article
  2. Exporting a .article that is not part of an InDesign-book and was created independently: The Web Resources folder of the InDesign-article will be completely integrated in the export of your .article
  3. Exporting as separate .articles (all articles of an InDesign-book): Each article will include a complete copy of the Web Resources folder from the InDesign-book.

2. Which choice to I need to make?

If your Web Resources folder doesn't contain a lot of huge files, you can choose for the automatic management: exporting a complete .publication or exporting as separate .articles will do just fine.

If all of your .articles will contain a lof of huge files in your Web Resources folder, it's best to create separate InDesign-articles and export all of them separately. You can also combine them in a book-file afterwards, but you need to start with the creation of separate Articles (separate InDesign-files):

  • Create all new Articles (via the Twixl Publisher plugin)
  • Populate your Web Resources with the necessary files, only needed for each specific .article
  • Group all InDesign files in an InDesign .publication (an InDesign-book file)
  • Use the Export as Articles so that you get an optimised .article export for each article.

Export as PDF or JPG

Export as PDF or JPG

Twixl Publisher releases before version 4.2 always converted the content to JPG files (or PNG files for transparent elements).

As of version 4.2 the default export format is PDF. The advantage of this is two-fold:

  • The publication package size will become much smaller.
  • It is no longer necessary to generate both a non-retina and retina iPad version, or three different phone renditions.

 

Was this article helpful?

1 out of 2 found this helpful