In Oxygen 20.1, why is webhelp classic deprecated?

[mdslup]

I use the webhelp classic transformation scenario for my doc sets. I love the output, as do my customers (and my boss!).

Why is this deprecated in 20.1?

[ionela]

Hello,

Thank you for your feedback.

We have decided to focus our resources on the development and enhancement of the WebHelp Responsive output generation rather than the Classic one. The DITA Map WebHelp Classic transformation scenario is included in the oXygen XML Editor/Author, but we won't add further functionality or features for it (that's why we've decided to mark this scenario as deprecated).

Regards,
Ionela

[mdslup]

OK. Will it continue to exist in future versions of Oxygen, or will it be removed in a later release?

The webhelp responsive is definitely amazing, so I get it. But the webhelp classic definitely does have a place, in my opinion.

[mdslup]

OK thanks. Is the plan to leave the webhelp classic in future versions of Oxygen or to remove it?

Can I ask that you do not remove it? It definitely has value!

[ionela]

Hi,

Thank you once again for your feedback.
We do not plan to completely remove the DITAMap WebHelp Classic transformation scenario (at least not on the short term).
We've just marked the scenario as deprecated as it won't be further improved and we would like to encourage our users to switch to the Responsive version.

Regards,
Ionela

[mdslup]

Hi Ionela,

I've thought more about it and wanted to point why I think the classic webhelp is actually more beneficial to users.

Here's a screenshot of my manual generated from classic webhelp. Here's a good benefit of this view: Note that the left side of the screen always shows me where I am, within the hierarchy of the entire manual. In this case, I'm in a topic that is nested inside another topic, that is nested inside the main map. And I can get to any other topic just by navigating through the tree on the left side.

https://i.imgur.com/o7keRJJ.jpg

Here's the exact same manual in responsive view. Notice that it is now no longer as clear where I am within my document's hierarchy. I can tell I'm in a topic nested within a topic by looking at the hierarchy on the left side, but then it's unclear that the "Wi-Fi Setup" is the same level of my manual's hierarchy as the "Wi-Fi setup" in the top menu. It's just not as intuitive where I am within the document structure.

https://i.imgur.com/L3qap0M.jpg

I admit that I'm very accustomed to the webhelp classic view and I also admit that the responsive view works better on phones. But when authoring complete manuals, I do think the webhelp classic is more intuitive and I plan to use it for a long time.

Thanks,

mdslup

[ionela]

Hello,

Regarding the navigation issue you've indicated a possible workaround would be to use the 'webhelp.publication.toc.links' parameter set to 'all' for the DITAMap WebHelp Reponsive transformation scenario. The default value of this parameter is 'chapter', but if you change its value to 'all' the publication side TOC includes all links:
Publication TOC links

We generate the Oxygen XML user manual with the parameter set to 'all'
Oxygen XML Editor User manual

Regards,
Ionela

[mdslup]

Oh, that's super helpful! Thanks.