HTML5 layouts have a Use H1 headings for topic chunks setting that you can use to control how <h1> headings are applied to your content. Typically, you will use this feature for SEO purposes, as it can be better to have <h1> for the main heading on each page in the output.
To change how Paligo applies <h1> headings to your HTML5 output:
-
Select Layout in the top menu.
Paligo displays a list of Layouts. The list is empty if there are no custom Layouts in your Paligo instance.
-
Select the Layout you want to update or Create a Layout.
Tip
You can copy the URL of the Layout Editor and paste it into a new tab in your browser. This can be useful if you frequently switch between your Paligo content and the Layout settings.
-
Select TOC and chunking in the sidebar.
-
Set Use H1 headings for topic chunks to either:
-
Publication hierarchy - Paligo will apply the heading levels based on where the topic appears in the publication structure. This means that the top-level publication will get
<h1>and your top-level topics will get<h2>for their main headings. Default -
Top-level - Paligo will apply
<h1>headings to the top-level publication and the top-level topics. -
Chunk - Paligo will apply
<h1>headings to every topic that is a "chunk". A "chunk" is a topic that is set to appear on its own page, for details, see Chunking. -
Default to inherit the value for this setting from the base Layout. The base Layout is either a built-in Layout provided by Paligo or another custom Layout, see Layout Relationships - Base, New, Duplicate.
Typically, it is better to use the Top-level or Chunk options for SEO purposes.
-
-
Select Save.
When you publish, Paligo will apply your choice to the output.
Note
To see how the Publication hierarchy, Top-level, and Chunk options affect the output, see the examples below.
Example 5. H1 headings based on publication hierarchy
Let's say you have a user guide and 4 topics at the top-level inside the publication. You have set your HTML5 layout to have Use H1 headings for topic chunks set to Publication hierarchy. When you publish, Paligo will apply <h1> headings based on the position of each topic in the publication structure.
The publication (1) has a topic too, so in the output, that is at the top level and it gets <h1> for its main heading. The topics (2) will get <h2> for their main heading, as they are at the second level in the publication structure.
Example 6. H1 headings for top-level topics
Let's say you have a user guide with 4 topics at the top-level inside it. There are also 2 topics at the next level down. You have set your HTML5 layout to have Use H1 headings for topic chunks set to Top-level. When you publish, Paligo will apply <h1> headings to every top-level topic in your publication.
The publication (1) has a topic too, so in the output, that is at the top level and it gets <h1> for its main heading. The top level of topics inside the publication (2) will also get <h1> for their main heading. The lower-level topics (3) will get <h2> as their main heading, as Use H1 headings for topic chunks is set to Top-level and the lower-level topics are second-level topics (third-level if you include the publication topic).
Example 7. H1 headings for chunks
Let's say you have a user guide with 4 topics at the top-level and 2 second-level topics, like this:
In this example, the publication "Acme User Guide" (1) is at the top. Inside the publication, the top-level topics (2) are "Introduction", "Quick start", "Troubleshooting" and "Reference material". The second-level topics (3) are "Cooling recommendations" and "Humidity recommendations".
Inside the "Cooling recommendations" topic, it has been set to chunk (it has an xinfo:chunk attribute with a value of Yes). So this topic will be on its own page in the output, even though it appears at a lower level in the publication structure.
Inside the "Humidity recommendations" topic, it has been set to not chunk (it has an xinfo: chunk attribute with a value of No).
In your HTML5 layout, you have set Use H1 headings for topic chunks set to Chunk.
When you publish, Paligo will apply <h1> headings like this:
-
Acme User Guide publication topic gets <h1> for its main heading
-
Introduction gets <h1> for its main heading
-
Quick start gets <h1> for its main heading
-
Troubleshooting gets <h1> for its main heading
-
Reference material gets <h1> for its main heading
-
Cooling recommendations gets <h1> for its main heading and it appears on its own page, even though it is a lower-level topic. It is not shown as subsection of "Reference material" as it is set to be a chunk.
-
Humidity recommendations gets <h2> for its main heading as it is set to not chunk. It appears as a subsection on the parent "Reference material" page.
Comments
0 comments
Article is closed for comments.