Skip to main content
T
trickyblain3
Known Participant
June 28, 2017
Answered

FM17 Publish HTML Nested Headers

  • June 28, 2017
  • 1 reply
  • 966 views

Hello,

I am trying to break my unstructured book file up into html5, and would like to have nested headers, help file style

i.e.,

Chapter Title

     Heading 2

     Heading 2

          Heading 3

I read some postings from previous versions that say you have to adjust paragraph styles in the source file. This seems like an odd way of going about it. As this is a mutlchannel book (it's published in print form as well), I'd rather not go messing with the template or creating conditional text across all 1,000 plus pages.

Is there a anything in the publish settings that can do this?

Thanks.

This topic has been closed for replies.
Correct answer Matt-Tech Comm Tools

Sorry for the late replay, just back from vacation. It's from a book with around 34 files, including a TOC. I tried using another layout and it still does not nest.


Is your TOC showing the nesting you like?

Try building a test book with test chapters...you should find it works as expected, and might shed some light on the differences.

1 reply

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity Expert
Community Expert
June 29, 2017

Are you talking about publishing as HTML5 with a TOC that breaks each title, H2, H3 out into separate topics? Or are you just referring to the appearance of the headers within a topic? The former you achieve with a TOC and pagination; the latter is done via CSS.

T
trickyblain3Author
Known Participant
June 29, 2017

Yes, the breaking TOC. It is currently listing every topic within all chapters, while I'd like to have them nested within chapters.

Thanks

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity Expert
Community Expert
June 29, 2017

What does your source FM TOC look like? You have to have enough indenting in your TOC so that the publishing engine can understand how to "style" the resulting HTML5 TOC...There's a blog post on the Adobe Tech Comm site that describes this in the FM to RH workflow (applies to FM to HTML5 workflow too, since the "engine" is RH under the hood).

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices