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

Hi Catherine, You can automate the WebHelp Responsive output generation from an automatic publishing system. In our user manual you can find more details about how you can generate the WebHelp Responsive output from a integration server (Travis/Jenkins): Generating WebHelp Responsive Output - Runnin...

Hi, Thank you for your feedback. In this case, for the DITA MAP WebHelp Responsive and DITA Map PDF - based on HTML5 & CSS transformations you can set the parameters in the scenario and then export the corresponding publishing templates. You can find more details about the publishing templates i...

Hi, Currently, there isn't a default dark mode theme that can be applied to the WebHelp Responsive output, but we do have various publishing templates which you can use: Publishing Templates You might choose for example, Hightech or Mechano template and further customize it if needed. You can choose...

Hi,

I'm sorry, but currently this is not possible. I have added your feedback as a feature request to our issue tracking tool.

Regards,
Ionela

Hi,

DITA-OT has trouble resolving references that are outside the directory where the published DITA map is found. For more details please check this topic from our user manual:
References Outside the Main DITA Map Folder

Regards,
Ionela

Hi, Unfortunately, we could not reproduce this problem on our side. If you are facing the same issue, please provide us a minimal valid sample DITA project so we can reproduce the problem on our side. You can send the sample on our support email address (support [AT] oxygenxml [DOT] com) or using ou...

Hi,

When you update your documentation and the WebHelp output is generated we recommend to deploy the entire output on the server (not just a part of if). This is the deployment procedure we recommended.

Regards,
Ionela

Hi Catherine, We are not aware of such an issue with the search functionality from v22. To reproduce this issue on our side, could you please provide us a minimal valid sample DITA project so we can reproduce the problem on our side? You can send the sample on our support email address ( support [AT...

Hi Catherine, It seems that you've modified the oXygen XML WebHelp plugin resources. To localize WebHelp interface you need to create your own extension plugin (without modified the built-in one), following this procedure from our user manual: How to Localize the Interface of WebHelp Responsive Outp...

Hi,

This message is shown by the browser (not by jQuery) and it depends on the language that is set in the browser.

Regards,
Ionela

Hi,

Unfortunately, in the current oXygen XML WebHelp implementation this is not possible, as the WebHelp output structure is generated from the DITAMap structure.
I have logged your feedback as an improvement request to be further analyzed by our development team.

Regards,
Ionela