In an increasingly fast paced world, it is more important than ever to create content that can be considered 'channel neutral' and to output this content to different channels.
In Studio this can be done by creating a Digital article and publishing it to multiple digital output channels as well as to print.
One of the digital channels to output to is Pugpig. To make publishing from Studio to Pugpig possible, Pugpig needs to be set up as a custom Publish Channel in Studio.
How this is done is explained in this article.
About Pugpig
For information about Pugpig, see the Pugpig website.
Requirements
To take advantage of the full Pugpig format and Pugpig functionality included with Studio, the following is required:
- Studio Server 10.10.0 or any higher version of Studio Server 10.
- A Web server to publish the article to from where it is pushed to Pugpig, such as Studio Server or any other place where it can be hosted and accessed publicly.
- Access to the Pugpig distribution center.
How it works
An article for Pugpig is a set of files in JSON, HTML, and PSV format.
These files are hosted on your existing content management system (CMS) and then pushed to Pugpig using the Pugpig RSS feed.
In Studio, a channel is set up which users can select when publishing an article from within the Digital editor.
Configuration
Configuration steps are required in Pugpig and Studio.
- Obtaining access to the Pugpig distribution service
- Setting up a Pugpig app
- Setting up a Pugpig RSS feed
- Setting up a channel in Studio
- Setting up metadata fields
- Setting up a style
- Testing the environment
|
Info: Use the filer to only show information for one step. |
1. Obtaining access to the Pugpig distribution service
The Pugpig distribution service is a paid platform and requires a license to access it.
This license is distributed and maintained by Pugpig. For more information visit www.pugpig.com.
2. Setting up a Pugpig app
Pushing articles from Studio to Pugpig’s distribution center requires the Pugpig app (also known as an SDK or App Container) to be set up.
This is done by the Pugpig team.
For more information, see the Pugpig Software & Service Specification.
3. Setting up a Pugpig RSS feed
When an article is published from Studio, it is first placed on a Web server from where it is then pushed to Pugpig. Pushing the article to Pugpig is done by making use of the Pugpig RSS feed. This feed needs to be set up and the resulting URL is later needed for configuring Studio.
Follow the steps for setting up a Pugpig RSS feed and note down the URL.
4. Setting up a channel in Studio
In Studio, every custom channel is configured with an 'endpoint' that Studio sends messages to when the article is published.
In the context of publishing to Pugpig, having this endpoint makes it possible for Digital articles to be pushed from Studio to Pugpig.
To set this up, follow all steps in Configuring Studio for publishing to a custom Publish Channel. For setting up the custom channel in Studio, use the following settings:
- Name: The name you want to give this channel. This name will appear in the list of Publish channels that the user can choose from.
- Target name: The name of the type of target you want to publish to. The user interface will group channels with the same Target name in the Publish dialog.
- Endpoint URL: The Pugpig RSS feed as set up earlier.
- Reference images by ID only (actual images will not be sent). Select this option when only a reference to any images in the story need to be included, not the actual images.
- Export formats. Make sure that the formats JSON, HTML and PSV are selected.
- Custom data. Not required.
- Maximum width and height for images in Assets. (See Optimizing images for publishing a Digital article in Studio) Assets images that are published to a digital channel and which have a format bigger than 2500 x 2500 pixels are automatically downsized to that format. To change this format, set a custom width and/or height.
5. Setting up metadata fields
The Pugpig publication requires various types of information such as the title, authors, page number, and so on.
This information is added as a property in the Properties dialog for the article in Studio and is mapped to the corresponding metadata field of Pugpig during the publishing process.
The metadata fields used are a combination of default metadata fields and custom metadata fields.
Default metadata fields
The following default metadata fields are mapped to fields in Pugpig:
| Studio Server field name | Field type | Pugpig metadata field / remark |
|---|---|---|
| Name | Static property | Page Title (when the Headline field is not used) |
| Used In (Issue > Name) | Static property | Edition > Title |
| Formatted (Modified On) | XMP properties | The timestamp of the last time the file was edited in Studio. |
Custom metadata fields
Pugpig requires additional information other than what is provided through the above mentioned default fields. Providing this information is done through custom metadata fields.
It is recommended to set up the custom metadata fields described below.
Note: Based on your publication the needs and fields can vary.
Step 1. Set up the following custom metadata fields as described in Adding a custom metadata property in Studio Server.
| Field name | Field display name | Field type | Pugpig metadata field / remark |
|---|---|---|---|
| C_HEADLINE | Headline | String | Page Title (if empty, the Name field is used) |
| C_BYLINE | Byline | String | Author |
| C_PAGE_NUMBER | Page Number | String | Rank |
| C_ON_SALE_DATE | On Sale Date | Date | Issued |
| C_PAID | Paid |
List Value List: None (default) Free Paid |
Defines if the article is provided free or paid. This setting is overridden by the subscription server. |
| C_SECTION | Section | String | Section |
| C_TEASER | Teaser | String | Sort Order |
| C_AN_ARTICLE_ROLE | Article Role |
List Value List: None (default) Feature Replica advertisement |
Defines if the article is displayed as Edit or Advert. A blank space equals Edit, and is generally selected by default. |
| C_TOC | Hide from TOC | Boolean | Hides the article from displaying in the Table of Contents. Field name is 'Hidden'. Requires a value of '1' to be sent as 'hide from TOC'. |
| C_PP_COVER | Cover | Boolean |
Sets the article as the cover. Requires a value of '1' to be sent as the cover. Default value: 0. |
| C_PP_STATUS | Pugpig Status |
List Value List: Draft Final |
Defines if the article should appear in the preview App or is ready for 'live production'. If On Sale date and Status are both met, the issue will go live. |
| C_PP_ISSUE_ID | Issue ID | String | Feeds into the Brands subscription server. |
Step 2. Add the above created custom meta fields to the Properties dialog box as described in Adding a property to a dialog box in Studio Server.
6. Setting up a style
Creating a Digital article in Studio is done by basing it on a template. This template contains a Style that controls the look and feel of how the Story should visually display.
Each specific publication in Pugpig can utilize a dedicated style. Set this up by following the steps in Styling a Story in the Digital editor of Studio by using Styles.
Tip: WoodWing Digital Services provides a service for outsourcing the production of a digital magazine, including the creation of custom templates for your brand. For more information, see the WoodWing website.
7. Testing the environment
To test to see if the system is set up correctly, follow the steps as outlined in Publishing to Pugpig using Studio.
Using the Pugpig test app, obtained by working with Pugpig’s team, you will be able to publish stories to the Pugpig distribution center. Stories will be viewable on desktop in the distribution center or on the mobile test app. For more information on publishing with a Pugpig test app, contact Pugpig directly.
Comments
0 comments