Page 1 of 1

Transformation scenario - where to put the custom template file

Posted: Tue Dec 10, 2019 10:15 pm
by mjlorenzi
I am looking through the Creating a Publishing Template to Customize WebHelp and PDF Output using CSS training video. This all makes sense for the most part and is easy to follow.

The one question I have is where to store the newly created custom template files? The video suggests naming the template to match similar to the name of the project, then placing the new template into your project folder - for ease of access.

Again, this all makes sense. But this infers that you will have a dedicated custom transformation scenario for each project. Would a transformation scenario not be more global and apply to many documentation projects?

I suppose there is nothing wrong with placing a dedicated template in the project folder of a specific project, but where would I store my template files if I wish them the apply to 99% of my projects? Is there a right or wrong place to put them? I like the idea of accessing the files in the Project View tab, but don't wish to nest my transformation template into a specific projects folder.

Would I be best off creating a dedicated projects folder for transformation templates? Just looking for best practices. Thanks!

Re: Transformation scenario - where to put the custom template file

Posted: Thu Dec 12, 2019 3:37 pm
by Costin
Hi mjlorenzi,

There is an alternative to store the publishing templates either in the oXygen's preferences, or in at Project level.
You should go into oXygen's menu Options > Preferences > DITA > Publishing and you could add whatever publishing templates locations in that list.
You could also reach that preferences page using the "Configure Publishing Templates Gallery" button from the Templates tab of the transformation scenario.
See the fragment between 5:38 - 6:00 from the video demonstration.
Going further, at the bottom of that preferences window, you could choose to save the publishing templates gallery preferences at global level - in the oXygen options file, or make them project specific, saving them at Project level.