Publishing a Story in Content Station Aurora to a custom Publish Channel can be done by using any of the files that are provided in the output file (see Configuring Content Station Aurora for publishing to a custom Publish Channel).
Recommended is to use the file in PSV (Prism Source Vocabulary) format: a combination of XML (for the metadata, re-use rights, and so on) and HTML5 (for the Story content).
Overview
For an overview of how the components of a Digital article are defined as PSV classes, see the components boilerplate.
|
Note: Properties such as paragraph alignment will be added to the class attribute. Example: |
For more information about Digital article components, see Working with the components of a Digital article in Content Station Aurora.
Document history
- 8 August 2018: Replaced the PSV definitions by a link to the components boilerplate in which they are defined.
Comments
5 comments
you can add a new digital component?
Hi Roberto,
Great question, currently you cannot add new digital components. However we are working on a feature (custom components) which makes this possible. Expected is that this will be available in the upcoming months. Please have a look here to see what features are coming up and in progress.
Thanks,
Maarten
Hi, the PRISM Source Vocabulary seems to be a good choice for a document exchange format.
However, the example PSV file is not valid according to the PSV 1.0 (psv.xsd) XML schema file.
It seems like “psv:uniqueid” should be “psv:uniqueID” instead, and “psv:idblk” should be “psv:IDBlk”.
Is that just a typo in the documentation, or does Content Station actually use the lowercase tag names?
Thanks, Tim
Hi Tim,
Thanks for reporting this, it seems that the code references in the article are incorrect.
The tags are correctly capitalised in an exported file, so please use that as a reference while we work on updating the documentation.
Best regards,
Maarten van Kleinwee
Senior Technical Writer, WoodWing Software
Hi Maarten, thanks for the quick reply – good to know that the actual exports are correct!
Please sign in to leave a comment.