On 07/07/2012 11:02 AM, Jerome Velociter wrote:
On Sat, Jul 7, 2012 at 10:50 AM, Jonathan Solichin <[email protected]>wrote:
Hi Jerome, friends,
* Would it make sense to use <aside> for the right sidebar ?
The aside is actually only for the comments, attachments, history and info
sections of the sidebar only. The reason behind this is that according to
html5 specs:
The aside element represents a section of a page that consists of content
that is tangentially related to the content around the asideelement, and
which could be considered separate from that content. Such sections are
often represented as sidebars in printed typography. (
http://html5doctor.com/understanding-aside/)
which I thought is appropriate for those sections.
Ok make sense
* I've seen you've used <article> as an overall wrapper. Wouldn't
<section>
be more appropriate, with articles implemented within the content of the
document ? (BTW this leads to the question of how this would translate in
wiki syntax. So far there is no such notion built right in - though .it
could be implemented with macros).
The reason I used article as an overall wrapper for the "main content" (the
stuff with the white background), according to the html5 specs:
"The article element represents a component of a page that consists of a
self-contained composition in a document, page, application, or site and
that is intended to be independently distributable or reusable, e.g. in
syndication. This could be a forum post, a magazine or newspaper article, a
blog entry, a user-submitted comment, an interactive widget or gadget, or
any other independent item of content." (
http://html5doctor.com/the-article-element/)
I thought this is appropriate since the entire "main content" is the self
contained part of the page that can be independent of the other parts (like
menu, asides, sidebars etc.)
The use of section I thought is appropriate because each gadgets is in a
way a section/part of the overall article, and of the sidebar.
"The section element represents a generic document or application
section" (http://html5doctor.com/the-section-element/)
These are just my thoughts on the components of a webpage of xwiki,
however. Do you think this is not the correct interpretation of the xwiki
parts?
Make sense too. My concern was about leaving enough room for application
developers (whose canvases are XWiki documents) to present their own
semantics. For example a blog application could want to present a list of
<article>. But maybe nesting <article> inside a main <article> element is
just fine.
Any thoughts ?
For non-application wiki documents, it makes sense to use <article>
around the whole content. For a blog homepage, or the blog archive, each
blog article should have its own <article> wrapper, though.
The HTML5 spec allows nesting article elements, and even an example is
given, where each comment of a blog entry is represented as a nested
<article> inside the blog post's <article> tag. Following this logic, a
blog is an article, and individual blog entries are sub-articles of that
blog.
As for wiki markup, that's a complex discussion that deserves its own
thread.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
