The Zendesk/Madcap Flare H1 issue | The place for Zendesk users to come together and share
Skip to main content
J
Jason39
March 5, 2025
Question

The Zendesk/Madcap Flare H1 issue

  • March 5, 2025
  • 1 reply
  • 62 views

Hi all … 

 

I commented in an old thread on this but I'm not sure it'll prompt any responses (apologies if it does and this is redundant). 

 

When publishing to Zendesk from Madcap Flare, on article pages, there's a weird issue that occurs where the H1 of the article is duplicated, once in the article header, and once in the article itself. As you might imagine, it looks kind of ridiculous. 

 

I'd like to keep the one in the header, but omit the one in the article itself. I'd prefer to accomplish this in the CSS rather than trying to use Madcap's conditions capability.

 

Can anyone assist me with this? 

    1 reply

    Elaine14
    Elaine14Employee
    Employee
    January 2, 2026
    Hi Jason,
     
    I understand the frustration with the duplicated H1 heading when publishing Madcap Flare content to Zendesk. Since you want to keep the H1 in the header and hide the one inside the article itself using CSS, here’s a possible approach:
     
    You could try targeting the duplicated H1 inside the article with CSS and hiding it, for example:
     
    .article-body h1 {
      display: none;
    }
     
    This assumes the article content is wrapped in a container with a class like .article-body and that the redundant H1 is the only H1 inside that container. If the structure differs, inspect the DOM in your browser to find the exact class or selector for the article’s main content and adjust the CSS accordingly.
     
    If you only want to hide the second H1 without affecting others, you might also consider:
     
    .article-body h1:nth-of-type(1) {
      display: none;
    }
     
    Test carefully to ensure this doesn’t hide any necessary headings. Alternatively, if the duplicated H1 has a specific class or attribute you can target, that’s even better.
     
    Hope this helps!
    Terms & ConditionsAccessibility statement