Hiding also H2, H3 in Markdown from navigation not only H1

[simondueckert]

I use mkdocs material to create a number of guidelines. When the title in the navigation is the same like a level 1 heading in the markdown file the title is only shown once. If I have level 2 or 3 headings in markdown the title is shown twice (see screenshot). Is there any way to suppress the display of terms from navigation so only headings from the markdown files are shown?

[alexvoss]

You should really have a level one heading int the Markdown. Is the reason you have a level 2 heading that you want the formatting to be different? If so, then use CSS to change this instead of skipping levels in the structure of your pages. If I guessed wrong then please le us know what it is you really want to achieve so we can advise.

[simondueckert]

I have level 2 and level 3 headings in the markdown because I also generate a PDF out of the markdown (with pandoc) and need an hierarchic table of content there. Do you have a tip for me where I have to put the CSS? Is it the stylesheets/extra.css I already use?

[alexvoss]

Yes, that would be the place. Are you using Pandoc for the PDF by any chance? It might be an idea to see if the adjustment could be made on the route to the PDF instead of using the wrong levels in the Markdown. One reason why this seems the better path to me is accessibility. Edit: was thinking of the --shift-heading-level-by option.

[kamilkrzyskow]

You can use theme extension to change the partials/content.html to remove the hacky H1 creation:

• https://squidfunk.github.io/mkdocs-material/customization/#extending-the-theme

• mkdocs-material/src/templates/partials/content.html

  Lines 31 to 37 in ade227c

  	<!--
  	Hack: check whether the content contains a h1 headline. If it doesn't, the
  	page title (or respectively site name) is used as the main headline.
  	-->
  	{% if "\x3ch1" not in page.content %}
  	<h1>{{ page.title | d(config.site_name, true)}}</h1>
  	{% endif %}

EDIT: Or if you don't want the H1 tag only when the H2 matches the page's title you can modify it like this:

{% if "\x3ch1" not in page.content and page.toc.items[0].title != page.title %}
  <h1>{{ page.title | d(config.site_name, true)}}</h1>
{% endif %}

EDIT2: But when it comes to accessibility a proper hierarchy tree of the headings could be important, so a lack of H1 could be a mistake, like Alex is saying. Depending on the used PDF creation method, you could perhaps have 2 different workflows for creating the PDF and deploying for the web.