First steps with WebHelp Responsive
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: * The background of the Search panel in the main * 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<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://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 [cid:image001.png@01DCCC2A.18729F10]<https://www.cgs-oris.com/> _______________________________________________ oXygen-user mailing list -- oxygen-user@oxygenxml.com To unsubscribe send an email to oxygen-user-leave@oxygenxml.com
Hello Frank, we have to provide webhelp with different colour schemes, too. Since the configuration is done in CSS, you can use less files with colour variables and set these appropriately. If you save a less file in Oxy, the corresponding CSS file will be updated automatically. Best, Franz-Josef Franz-Josef Knelangen Leiter Dokumentation Main: +49 7634 5612-0 Facebook<https://www.facebook.com/akgsoftware/> | Xing<https://www.xing.com/pages/akgsoftware> | LinkedIn<https://www.linkedin.com/company/18590571> | YouTube<https://www.youtube.com/c/AKGSoftware-infrastructure> [cid:image002_01fef2d4-1f7d-4ea5-9727-748ef31e8852.png] AKG Software Consulting GmbH Uhlandstr. 12 D-79423 Heitersheim www.akgsoftware.de<https://www.akgsoftware.de/> Geschäftsführer: Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens Günther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg i. Br.) From: Frank Dissinger <frank.dissinger@cgs-oris.com> Sent: Tuesday, April 14, 2026 4:34 PM To: oxygen-user@oxygenxml.com Subject: [oXygen-user] First steps with WebHelp Responsive Externe E-Mail: Ist der Absender bekannt? Wird der Inhalt erwartet? - Vorsicht beim Öffnen von Anhängen und Klicken auf Links! 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: * The background of the Search panel in the main * 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<mailto:frank.dissinger@cgs-oris.com> | Web www.cgs-oris.com<http://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 [cid:image001.png@01DCCCDF.57180EC0]<https://www.cgs-oris.com/> _______________________________________________ oXygen-user mailing list -- oxygen-user@oxygenxml.com To unsubscribe send an email to oxygen-user-leave@oxygenxml.com
participants (2)
-
Frank Dissinger -
Franz-Josef Knelangen