OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] <h1> headers in html and webhelp output of <book>

On Jul 28, 2016, at 1:48 AM, Fekete, Róbert <robert.fekete@balabit.com> wrote:
> We don't use numbered sect tags, only <section>s

So use <sect1>, <sect2>, etc, and you’ll get <h1>, <h2>, etc. in your output.

> Our web team notified us that having multiple h1 tags in the html is not really SEO-friendly, that's why I'd like to change it.


Either your DocBook isn’t structured semantically, so that your SEO team is “right” in the sense that search engines are going to look askance at the poorly-structured output, or you’re letting the tail wag the dog here.

Properly used, DocBook HTML output should be SEO-friendly in the sense that it resembles properly structured pre-bubble HTML, the way Sir Tim designed it.  All styling decisions should be purely in CSS, not by hacking the DocBook to force specific HTML structures.

> In the webhelp output we have a custom h1 tag that includes the name of the book and the chunk

Shouldn’t that be <title>?

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]