Responsive HTML Skin (Azure) does not generate edited fields in the output. RoboHelp 2020

Forum|Forum|4 years ago
June 30, 2021
5 replies
390 views

I have edited the Azure_Blue skin to my company branding (colour scheme, font, etc), and changed the Home logo in the Header bar. In the skin editor, everything shows as desired, however, when generating the output to Responsive HTML, the skin displays the default template, showing none of my changes.

This topic has been closed for replies.

Correct answer Jeff_Coatsworth

Did you select the customized version in the Output Preset?

Jeff_Coatsworth

Community Expert

I can't see how importing Word content into a new project would have any impact on what's being used in the Output Preset as the skin. If you pick a totally different skin the Preset's Layout section, does it change it in the output produced?

A

AbiBirchAuthor

Inspiring

Hi Jeff,
It is sorted now... The Responsive HTML > Layout parameter for 'Skin' was not pointing to the skin I edited... Thank you for your time, it is much appreciated.

Peter Grainge

Community Expert

If you open the customised skin in the skin editor does it still show your customisation?

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Jeff_Coatsworth

Community Expert

Was it an upgraded project from a prior version of RH?

A

AbiBirchAuthor

Inspiring

No...! Totally new project

Jeff_Coatsworth

Community Expert

You said that you customized the Azure_blue skin - you gave it a unique name didn't you?

A

AbiBirchAuthor

Inspiring

Hi Jeff, yes, it was given a unique name. I also generated from the default name (Azure_Blue) and both present the same result, i.e. no customization changes showing. I am probably doing something daft, but at the moment I can't see where?

A

AbiBirchAuthor

Inspiring

I'm not sure if this is relevant, however the issue appears to be on a project where I imported a Word document. This does not happen on other projects, where I have developed from scratch...