Highlighted

RH 2019: Upgrading a RHTML5 project with screen layout to new UI with skin

Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

I am maintaining several help projects created with older versions of RH where the RHTML5 laoyout was configured using a screen layout. I can continue to maintain these projects with RH 2019 classic, but if I try to upgrade them to RH 2019 with new UI, the screen layout is converted to a skin which obviously looks completely different than the old layout.

 

What is the recommended upgrade path in such cases? I would like to be able to use the new UI, as that is what will be maintained in the future, but how do I get there?

 

I have tried searching for information, but I wasn't able to find any, but I hope my situation is not unique.

TOPICS
New UI

Views

207

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

RH 2019: Upgrading a RHTML5 project with screen layout to new UI with skin

Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

I am maintaining several help projects created with older versions of RH where the RHTML5 laoyout was configured using a screen layout. I can continue to maintain these projects with RH 2019 classic, but if I try to upgrade them to RH 2019 with new UI, the screen layout is converted to a skin which obviously looks completely different than the old layout.

 

What is the recommended upgrade path in such cases? I would like to be able to use the new UI, as that is what will be maintained in the future, but how do I get there?

 

I have tried searching for information, but I wasn't able to find any, but I hope my situation is not unique.

TOPICS
New UI

Views

208

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Feb 06, 2020 1
Adobe Community Professional ,
Feb 06, 2020

Copy link to clipboard

Copied

Which output and layout are you using?

 

If it's a multiscreen HTML5 output, then I'm afraid you're out of luck and will need to customise a skin in the New UI version.

 

If a responsive HTML5 layout, I had thought those skins transferred better, but I haven't tested it myself, so perhaps someone else can comment.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

The output is Responsive HTML5, and the layout is a custom layout that was created before I started working with these projects.

 

I understand that the old screen layouts had other properties than the newer skins, and that there is no one-to-one relationship when upgrading. Maybe the best solution would be to create a completely new skin based on the old screen layout and apply that.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Adobe Community Professional ,
Feb 06, 2020

Copy link to clipboard

Copied

If your skin was a responsive skin and only customised through the skin editor, the theory is it should upgrade. Only a test will tell for sure.

 

Otherwise you will need to select one of the supplied skins and customise that.


www.grainge.org

www.grainge.org for free RoboHelp & Authoring info. Use the blue Reply button at the top to help me help you.
The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

Hello!

I actually have a similar question. We customized the heck out of our screen layout in RH2017 for Responsive HTML5 output. Not only did we make changes using the screen layout editor, we also needed to manually edit the layout.css file (from the ../!ScreenLayout!/Azure_Blue folder) to have out screen layout conform to our corporate styling. Some screen elements were just NOT available to customize via the screen layout editor. Anyways, everything compiled fine and was happy. We edited the layout.css once and never needed to touch it again.

 

However, when we migrated to RH2019 Reimagined Version, we are now BACK to editing skins, and the layout.css file is NOWHERE TO BE FOUND in any of the source file folders. In order to get the output to look the way we like, we have to generate the help and replace the generated layout.css file from the new output folder with the one from our RH2017 ../!ScreenLayout!/Azure_Blue folder!!! Frustrating!

 

As you can see, this is NOT the desired experience we'd expect from an upgraded app; it actually seems to have taken a step BACKWARDS. Can anyone tell me which file(s) that I can edit to fully manipulate the styling in the TOC and Header manually, so we can get our output to look the way it should without the constant post-generation swapping of layout.css in the output folder?

 

Thank you so much!!

TabbyW

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 1
Adobe Community Professional ,
Feb 06, 2020

Copy link to clipboard

Copied

On the Layout tab of the skin, there's a User Assets section. I think the intention is that you add your tweaks to your own css file and attach it there, rather than playing with the proper skin css. That would mean Adobe don't have to worry about wiping out your customisations if they update the skin css.

 

If you can, I'd suggest picking out just your customisations from the old layout.css. You could attach the whole old file, but I'm not sure how the two complete css files would play together.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 1