DITA: Webhelp skins
You can customize the webhelp output through the webhelp skin builder. This is an external resource that allows you to create a custom stylesheet that you can then specify in your transform. It works pretty slick.
To access the webhelp skin builder, go to http://www.oxygenxml.com/webhelp-skin-builder/. Select DITA, select a basic template to begin with, and then start customizing it. Download the CSS file to your computer.
In Oxygen, when you configure your transformation scenario, duplicate the existing webhelp option, and then edit it. On the Skins tab, select your custom CSS file.
Sponsored
You can add further customizations to this skin by simply adding the CSS styles in the stylesheet.
If you want to actually customize the webhelp output for the default webhelp (and apply it to all webhelp outputs), you can do so by modifying the stylesheet located here: /Applications/oxygenAuthor/frameworks/dita/DITA-OT/plugins/com.oxygenxml.webhelp/oxygen-webhelp/resources. Modify the webhelp_topic.css stylesheet.
You should also be able to add a custom stylesheet through the Parameters tab on the transformation scenario. In the args.css parameter, specify a file.
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.
If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.
Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.