Thank you, Julien, for your reply.

I have heard about DITA-OT Project Files, but have no experience with them. Before I dig deeper into this matter:

Regards, Frank  

 

Von: Oxygen XML Editor Support (Julien Lacour) <support@oxygenxml.com>
Gesendet: Mittwoch, 15. April 2026 09:50
An: Frank Dissinger <frank.dissinger@cgs-oris.com>
Betreff: Re: [OXYGEN-47705] [oXygen-user] First steps with WebHelp Responsive

 

Hello Frank,

The transformation scenario represents the actual output you want to generate (such as WebHelp Responsive, CHM, PDF, etc.) while the publishing template is a customization package passed as parameter to the scenario. You can find more details about publishing templates here.

As you need to produce different outputs using different colors, logos, etc. I think the correct use-case is to have multiple transformation scenarios. One solution to keep them in a single location is to create deliverables in a DITA-OT Project file.
Another possibility is to create a scenario using the ${ask} editor variable to set some parameters such as logo or CSS.

If you are at ease with Ant, you could try to create a custom DITA-OT plugin with your own transtype that further calls the WebHelp Responsive transformation after setting the variables.

Regards,
Julien

On 4/14/2026 5:33 PM, Frank Dissinger wrote:

Hello all,

 

I am a bit confused. There are transformation scenarios and publishing templates.

What is each used for?

Where are these things stored? I want to add them to our source code repository to have a version history and backup.

 

I need to create WebHelp Responsive for various products in various languages.

There is a shared company logo for all products. If we create OEM versions one day, however, the company logo will vary.

There is a separate product logo for each product.

There is a separate project folder for each product and language, which holds the root ditamap that will be processed.

There is a separate output folder for each product and language.

There is a special color for each product. This color should be set for:

  1. The background of the Search panel in the main
  2. The shortdesc element that follows a topic title; figure titles; table titles (to be handled via CSS variables)

 

I wouldn’t like to have a separate transformation scenario for every single publication. I would like to maintain only a minimum of files. How should I organize this?

 

Ideally, all this information could be retrieved automatically from the ditamap being published.

Can Oxygen create custom editor variables from ditamap information?

Or can I start the transformation from a script that prompts the user for this information? Or call a script from the scenario?

 

For CHM output, which I did previously, I created an ANT script which asked for the product and language and, based on user input, set the name of the ditamap to process, the language, output directory, location of resources such as logos, etc.

 

Best regards

Frank Dissinger

Documentation Manager

..........................................

CGS ORIS GmbH

Email frank.dissinger@cgs-oris.com | Web www.cgs-oris.com

Address Kettelerstrasse 24 | 63512 Hainburg | Germany

Phone +49 6182 9626-0 | Fax +49 6182 9626-99

Commercial register Offenbach, HRB no. 21495

Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji