Re: That annoying duplicate <h1> issue

Remember that only pages that have been "touched" since the import will
have the duplicate title. Once all pages have been "touched" we can just
totally turn off the built in H1's.


On Tue, Dec 18, 2012 at 7:56 AM, Jonathan Garbee <jonathan@garbee.me> wrote:

>  Each page needs a title, if this would remove the default title leaving
> just the form title to be on the page (as we should do) then the plugin is
> perfect for our use-case.
>
> -Garbee
>
>
> On 12/18/2012 10:52 AM, PhistucK wrote:
>
> I think we need the opposite. ;) Show a title only when needed.
>
>  ☆*PhistucK*
>
>
>
> On Tue, Dec 18, 2012 at 5:34 PM, Taylor Costello <
> nottaylorcostello@gmail.com> wrote:
>
>> http://www.mediawiki.org/wiki/Extension:NoTitle
>>
>>  Here's an extension that does what you are asking for, if you don't
>> want to hide the title on every page.
>>
>>
>> On Tue, Dec 18, 2012 at 6:51 AM, Jonathan Garbee <jonathan@garbee.me>wrote:
>>
>>>  Multiple H1 is not bad for SEO or "semantics" if used properly.
>>> Further, forget about SEO completely; at this point we should focus on
>>> getting content updated and formatted properly and not worry about stupid
>>> SEO. The point is it is just annoying to have multiple title headings. For
>>> now, display none will work until we figure out how to have the pages
>>> generated properly.
>>>
>>> -Garbee
>>>
>>> On 12/18/2012 8:08 AM, PhistucK wrote:
>>>
>>> Duplicate <h1> is really bad semantically and due to this fact, it is
>>> also really bad for SEO reasons.
>>> This must be removed from the HTML itself, not only dynamically/using
>>> CSS.
>>>
>>>  ☆*PhistucK*
>>>
>>>
>>>
>>> On Tue, Dec 18, 2012 at 1:35 PM, Chris Mills <cmills@opera.com> wrote:
>>>
>>>> I was just thinking about that annoying issue we've got, where we have
>>>> duplicate <h1>s on a page: one of my personal pet peeves.
>>>>
>>>> The auto generated <h1> has got a class of firstHeading (and an ID the
>>>> same, for that matter). If just put
>>>>
>>>> .firstHeading { display: none; }
>>>>
>>>> In common.css, surely that would get rid of our issue?
>>>>
>>>> I haven't done it yet, because I thought I'd just check that it
>>>> wouldn't ruin anything on the site first. It does mean that we'd need to
>>>> make sure titles are manually added to all pages (via =a manual h1=, or by
>>>> using the title for field in the form templates.)
>>>>
>>>> Thoughts?
>>>>
>>>> Chris Mills
>>>> Opera Software, dev.opera.com
>>>> W3C Fellow, web education and webplatform.org
>>>> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>