Hello, A 404 Page should be part of the configuration of the HTTP server where the WebHelp Responsive output is deployed. Such a page it is beyond the scope the WebHelp output. The HTML pages that are part of the WebHelp ouptut are generated based on the topics contained by your DITA map source. Reg...

Hi Dan, WebHelp uses the following CSS rules to style the Copy button: .codeblock .copyTooltip{ background: #fafafa url("../img/Copy.png") no-repeat 85% 50%; background-size: 15px; width: 68px; height: 32px; margin-top: -7px; color: #888; border:1px solid #CCCCCC; right: 15px; position: ab...

Hello, You can generate the Publication TOC as JSON file by processing the temporary toc.xml file. For this you need to register an XSLT file on the com.oxygenxml.webhelp.xsl.createNavLinks XSLT extention point. I have created a sample Publishing Template that generates a toc.json file in the output...

Hi Dave, One other question--can I show the same metadata content in a concept? I've tried and I can't get this to work for concepts. The fragment I'm using: <div class="audience ${topic-xpath(/concept/prolog/metadata/audience[1]/@type)}"/> Yes you can show the same metadata in concept top...

Hi Catherine, Yes, it is possible to secure and restrict access to certain resources, but this is out of scope of the output generated by the WebHelp Responsive plugin. This should be the job of the HTTP server were your output is deployed. The WebHelp Responsive output is a collection of static res...

Hello, WebHelp Responsive allows you to insert custom HTML fragments in the output HTML pages. Such an HTML fragment can use special Macros that allow you to execute XPath expressions on the input DITA documents (map or topics). For example: Considering the following prolog content available in a DI...

Hi Justin,

You can fix the issue by increasing the "z-index" property of the pop-up menu in CSS.
For example: I have also updated our templates samples.

Regards,
Alin

Hello, There is no requirement to embed the fonts in the WebHelp output. You can reference Google Fonts in you CSS files. We have several built-in Publishing Templates that also use Google Fonts (Aquamarine, Ashes, Blue, etc). If your HTML pages contain the language information as an xml:lang attrib...

Hello, You could try to list the "expand.js" as a dependency in your module definition. For example: define(["expand"], function () { console.log("template module loaded"); }); Here is my console output (I have added some log in the expand.js module): http://www.oxygenx...

Hello,

For the WebHelp Responsive output, please have a look at this topic: https://www.oxygenxml.com/doc/versions/ ... s-amd.html

Regards,
Alin

Hello, I have updated the template as follows: - Main flex items in the header section (title, menu + index terms link, search input) will not wrap - The content within each item can still wrap independently (e.g.: menu items will warp on multiple lines if there is no enough space) - Title and searc...

Hello, For the completeness of this post, please provide more details about your configuration. - What type of WebHelp output (Responsive / Classic) are you trying to customize? - Which version of the associated plugin are you using? - What are you trying to achieve with your customization? Please n...

Hello, You need to customize the WebHelp Classic plugin in order to transfer the metadata information in the index.html page. You can do this by overriding the default XSLT templates that are used by the WebHelp transformations as described here: https://www.oxygenxml.com/doc/versions/21.0/ug-webhel...

Hello, FIrst of all I want to let you know that the WebHelp Classic plugin for DITA-OT that comes bundled in Oxygen 21.0 has been deprecated and removed from Oxygen distribution starting with version 23. The newly versions of Oxygen includes an enhanced version of DITA-OT plugin: WebHelp Responsive....

Hello, I have fixed the position of the footer section and pushed the changes to the samples repository. In footer-fix.css I have replaced: body { height: 100vh; } with body { min-height: 100vh; } Please let me know if the issue still occurs on your side. You can also remove the footer-fix.css file ...

Hello, You can use an XSLT Extension (https://www.oxygenxml.com/doc/versions/23.1/ug-webhelp-responsive/topics/whr-responsive-override-xslt-dita-xslt-import.html) in your Publishing Template to generate the additional content. You can use the following sample as inspiration: https://github.com/oxyge...

Hello Christina, The issue you are facing is because the oxygen:getParameter() function does not work properly. To fix it, first you have to declare the following parameters in your stylesheet: <xsl:param name="TEMP_DIR_URL"/> <xsl:param name="WEBHELP_PARAMETERS_URL" select="...

Hello, You can achieve this by contributing custom JS code (via an HTML Fragment ) to the generated WebHelp HTML pages. Please have a look at the following sample Publishing Template that provides a similar functionality: https://github.com/oxygenxml/oxygen-publishing-template-samples/tree/master/te...

Hello, You could achieve this by customizing the HTML Page Layout files, but we do not recommend this approach. A complete explanation is available in our User Guide (see the Warning note): https://www.oxygenxml.com/doc/versions/23.1/ug-webhelp-responsive/topics/html_page_templates.html The easiest ...

Hello,

You can try to use the following custom CSS rules to disable the unwanted hover effect: I have registered an issue to correct this behavior.

Regards,
Alin

Hello, It is not possible to generate an HTML page for a <topichead> entry. According to DITA Specification : The <topichead> element provides a title-only entry in a navigation map, which should appear as a heading when the map is rendered as a table of contents. In print contexts it should also ap...

Hello,

We have already fixed this issue in our current development stream. The fix will be available in Oxygen WebHelp 24.
Until then, we can provide a custom CSS rule to correct this behavior. Please let us know if you are interested.

Regards,
Alin

Hi,

Sorry for the delayed response. I did managed to reproduce the error in Oxygen 23.1.
I have submitted a task (ID: EXM-47764) to analyze what is the cause of this behavior.

Regards,
Alin

Hello, In my opinion this a classpath issue. You should check the order of Saxon libraries listed in the transformation's console output and check that the Saxon jar file from {OXYGEN-INTSALL_DIR}/lib is listed before the one bundled in your current DITA-OT. Please see this topic post . You can also...

Hello, It seems that you need to follow this procedure and update your transformation scenario. Cannot find a 1-argument function named Q{http://expath.org/ns/file}last-modified() The file:last-modified function is available only in Saxon EE and PE distributions and the DITA-OT bundled in Oxygen use...

Hello, The Publication TOC (Side TOC) is generated based on the structure of the expanded DITA map (that is the DITA map created in the WebHelp transformation's temporary directory). The profiling attributes declared at topic level are not being transferred by default to the associated topicref elem...

Hello,

What you want can be achieved using the following property: https://developer.mozilla.org/en-US/doc ... -transform

Regards,
Alin

Hello, In the DITA topic you can use the @outputclass attribute on a DITA element to generate a custom class on the associated HTML element in the WebHelp output. For example, the following DITA content: <p>And above all, <ph outputclass="red">remember</ph> that many flower gardens fail be...

Hello, Your HTML fragment is not well-formed because the associated DTD contains broken references. When performing an well-formedness test in Oxygen, the check fails with the following error: https://www.oxygenxml.com/forum/files/not-well-formed-broken-dtd.png Please remove the DTD declaration and ...

Hello, Please check that the content of your file (javascript.xhtml) is well-formed. If you contribute this file using a transformation parameter, you need to set that parameter to the absolute path of the file. If you contribute the file in your Publishing Template please provide more details about...