Robohelp toc

​@Amebr was the expert on this type of issue but looking through her posts, this issue doesn’t seem to be covered. However, in a post about another issue where a file needed to be uploaded after generating the answer was to create a script that uploads it.

Overall it’s messy. It’s the template that needs to be customised rather than the preset if that makes any difference. I wish you luck on this one.

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

I understand why you don’t want to change to frameless but that is what is making your customisation of the TOC difficult. Responsive skins have very little built in customisation.

First question is are you changing the customisation of Azure Blue to the phone settings? Looking through the settings Sidebar seems to be the most obvious but even that does not allow a width setting.

There is only option that I can think of to try and that is to go behind the scenes. What you do is reduce the browser window size so that it switches to phone size. Then right click in the area and select Inspect. That will show you the code and you may find a width setting.

What you then do is put that setting into a CSS file but then you hit the next issue. In Frameless there is an option to upload that when generating. I can’t see the same option for Responsive.

I think this may have been covered in the past so I will have a look.

Alternatively try Support but I’m not sure they can help with this sort of customisation as it’s working as designed.

See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

You don’t mention what version of RH you’re running - try to lead with that. Responsive HTML5 output should change shape and layout depending on the screen size. Are you getting the same response when using the sample project? Have you tried testing with another layout?