Hello, Thank you for your feedback. Could you please provide us more details about the context of this problem? What version of oXygen XML and build number are you using (from menu Help > About )? Does this issue occur when you duplicate the default DITA Map WebHelp Responsive scenario? Or the trans...

Hi,

Could you please provide us more details about your use-case and what would you like to achieve? Do you need to change the CSS for imagemap in Author mode (when you edit the documents) or in an output (for instance, WebHelp Responsive)?

Regards,
Ionela

Hi, Thank you for your feedback. In version 23.1 of oXygen XML, the rendering of DITA <note> elements in the WebHelp output was redesigned to make the content within the note even more noticeable. From the screen-shots you've provided it seems that you are using a custom template with some CSS custo...

Hi,

Thank you for your feedback and for letting us know about this issue.

Unfortunately, the WebHelp Classic scenario is deprecated and it won't be further improved.
But, the license allows you to implement the fix on your side and modify the WebHelp Classic sources.

Regards,
Ionela

Hi,

Just to double check, are you trying to customize the static labels? If yes, you can follow this procedure from our user manual:
How to Localize the Interface of WebHelp Responsive Output

Regards,
Ionela

Hi Nicolas, Unfortunately, there isn't an out-of-box way to obtain a zip achieve with the WebHelp Responsive output. You could try to achieve this using a customization. If you obtain the WebHelp Responsive output from command line you can develop a custom script that first runs the WebHelp transfor...

Hi, Most likely, these warnings occur if the language set on your DITAMap it is not one of the languages for which the WebHelp output offers localization (English, German, French, Japanese, Chinese). To solve this issue, you need to add this language and localize the WebHelp output. The complete pro...

Hi Frank, When upgrading your oXygen XML WebHelp plugin to v22 it is recommended to follow the procedure described in our user-manual: Upgrading WebHelp Responsive To answer your actual question, the page templates fragments directory is used internally during the WebHelp output generation, so it ha...

Hi, To further investigate this issue on our side, so we would need some more details. Therefore, could you please send us the entire transformation console log. For this, you can set the 'Show console output' option to 'Always': DITA Logging Preferences > Show console output Also, it would be very ...

Hi, As it is a new project, the first thing you need check is the integrity of your DITA map, to make sure that your maps and topics are valid, and all the relationships between them are working. You can do this by using the 'Validate and Check for Completeness' action from the DITA Map menu (there ...

Hi, Usually, it is not recommended to modify built-in files from Oxygen XML WebHelp plugin. Could you please provide us more details about your use-case on our email address ( support AT oxygenxml DOT com ) to discuss internally about a possible solution to achieve the result you need. Regards, Ionela

Hi,

Thank you for your suggestions. I have added them to the existing feature request logged on our tracking tool.

Regards,
Ionela

Hi,

Thank you for your feedback.

Unfortunately, in the current WebHelp implementation this is not possible. We already have this feature logged to our tracking tool and I have added your feedback to it.

Regards,
Ionela

Hi,

Unfortunately, this feature is not scheduled to be implemented in the short term.

Regards,
Ionela

Hi,

Thank you for your feedback.

The warnings you have indicated do not affect the WebHelp functionality as that file is used just for development. However, I have logged an issue to our tracking tool to be further investigated and resolved by our development team.

Regards,
Ionela

Hi, The parameter you have indicated refers to the Expand/Collapse All Sections button located next to the navigation links. Please see the screen-shot below: ExpandCollapse.png Indeed, the title and the description of the parameter is not very clear. Unfortunately, there isn't a way to turn off col...

Hi, It is not recommended to modify the context-help.js or other built-in files from the oXygen XML WebHelp deployment. The mechanism to accomplish this is to implement your own JavaScript and include it to the WebHelp output using the procedure described in our user manual: You can add custom HTML ...

Hi, Just to make sure I have correctly understood the use-case, would you like to have a different topic title from the ditamap in the navigation and breadcrumb? If yes, you can achieve this by using a navigation title , this way you set a different topic title for the navigation comparing with the ...

Hi, Unfortunately, currently it is not possible to modify this behavior as this is how it works by design. I have logged your feedback as an improvement request to our issue tracking tool to have an option that might deactivate link created by the topichead. This will be analyzed by our development ...

Hi Syed,

Thank you for your feedback.
You can try to achieve this by implementing a JavaScript customization for the WebHelp Responsive output:
How to Insert HTML Content

I have also added an improvement request with your feedback to be further analyzed by our development team.

Regards,
Ionela

Hi Catherine, You can try to add under the topic title the information you have indicated using webhelp.fragment.after.logo_and_title placeholder. As a starting point you can check our sample from GitHub Bookmap copyright info with macros For the FeedBack we have a new SAS platform called Oxygen Fee...

Hi,

Thank you all for your feedback.
We have an improvement request logged to our issue tracking tool to implement this for a future version of oXygen XML WebHelp. This will be analyzed by our development team. I have added your votes and comments to it.

Regards,
Ionela

Hi,

Thank you for your feedback. I have added your vote and comments to the improvement request.

Regards,
Ionela

Hi Catherine,

Unfortunately, we do not have experience with GitLab CI.
But, as WebHelp Responsive can be run from the command line, if the integration server you've mentioned offers support to run the output generation script you can try to automate the publishing process using it.

Regards,
Ionela

Hi, In case you need customize WebHelp Responsive output to include a logo in the title area that redirects you to the home page (similar with what we have in our user manual) you can achieve this by setting the following paramters: ' webhelp.logo.image ' and ' webhelp.logo.image.target.url '. For m...

Hi Catherine,

I think this procedure from our use manual suits to your use-case. You can try to automate the WebHelp Responsive generation using Travis CI:
Automating DITA to WebHelp Responsive Output with Travis CI

Regards,
Ionela

Hi,

Thank you for your feedback and these suggestions.
I have added your comments to the improvement request from our issue tracking tool.

Regards,
Ionela

Hi Justin.

Thank you for your feedback.
Sure, I have added your vote and comments to this issue.

Regards,
Ionela

Hi Justin,

Thank you for these details.
I have added all your feedback to our issue tracking tool as an improvement request regarding a dark mode for the WebHelp Responsive output.
This will be analyzed by our development team.

Regards,
Ionela

Hi,

Thank you for your feedback.
I confirm this is a bug on our side and I have logged it to our issue tracking tool to be further analyzed by our development team. The issue number is: DCP-414.

Regards,
Ionela