[TYPO3-content-rendering] Using <nav /> for content type "menu"

[Patrick Broens]

Hi,

For the cObj Menu some parts can be seen as secondary navigation or 
in-page navigation. These parts need to have a <nav> element. We might 
discuss here what does not need the <nav> and what does.

These are the possibilities:
* Menu of selected pages (arguable, could be related pages and then it's 
not recommended)
* Menu of subpages of selected pages (arguable, could be related pages 
and then it's not recommended)
* Menu of subpages of selected pages including abstracts (arguable, 
could be related pages and then it's not recommended)
* Menu of subpages of selected pages including sections (arguable, could 
be related pages and then it's not recommended)
* Section index (Needs nav)
* Recently updated pages (no nav)
* Related pages (based on keywords) (no nav)
* Sitemap (Needs nav)

Could you give your opinion about these possibilities?

Cheers

Patrick


On 11-8-11 9:13 , Steffen Ritter wrote:
> Am 11.08.2011 03:19, schrieb Thomas "Thasmo" Deinhamer:
>> Hello Patrick, hello folks!
>>
>> I've seen there was a commit about
>> using the <nav /> element in menus:
>> http://forge.typo3.org/projects/typo3v4-incubator/repository/revisions/f4b72c829217939393ce3a88f4ac460434414866
>>
>>
>>
>> Before finalizing this I wanna point
>> to this article on html5doctor.com:
>> http://html5doctor.com/avoiding-common-html5-mistakes/#nav-external
>>
>> So, I think it may makes sense to
>> consider not using <nav /> at all
>> or at least not for all menu types.
>>
>> Oppinions?
>>
>> Thanks,
>> Thomas
> Full Ack,
> for the ContentElement Menu, I rather would opt to not warp nav...
>
> regards
>
> Steffen