Please note that this work is taken out of the Rob Larsen’s lecture on HTML5+Wordpress, but obviously, I would like to introduce you to the part where he very elegantly describes the HTML5. I have found his lecture amazing, easy to understand without patronising to the more ‘aware’ audience and also invigorating! So I wish to share it with you, Jo Blog.
Introduction to HTML5
HTML5 is a lot of things-
Ongoing. This is a moving target. The spec can change underneath you. This can be fun, I swear. It also means there’s not always an answer. That, too, can be fun.
Occasionally controversial.
Full of cool stuff that’s got both browser and web developers excited
Something to pay attention to/ experiment with/ discuss and give feedback on (which is why we’re here today)The talk is going to be about some new, semantic elements and attribues.. This is a subset of the spec that’s relatively stable and is usable right now. We’ll use a small bit of JavaScript or the Modernizr library to make styling these elements work in Internet Explorer.
(as usual things don’t really work in IE!)
<section>
The section element represents a generic document or application section. A section, in this context, is a thematic grouping of content, typically with a heading. Examples of sections would be chapters, the various tabbed pages in a tabbed dialog box, or the numbered sections of a thesis. A Web site’s home page could be split into sections for an introduction, news items, contact information.
<nav>
The nav element represents a section of a page that links to other pages or to parts within the page: a section with navigation links. Not all groups of links on a page need to be in a nav element – only sections that consist of major navigation blocks are appropriate for the nav element. In particular, it is common for footers to have a short list of links to various pages of a site, such as the terms of service, the home page, and a copyright page. The footer element alone is sufficient for such cases, without a nav element.
<article>
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 Web log entry, a user-submitted comment, an interactive widget or gadget, or any other independent item of content.
<aside>
The aside element represents a section of a page that consists of content that is tangentially related to the content around the aside element, and which could be considered separate from that content. Such sections are often represented as sidebars in printed typography. The element can be used for typographical effects like pull quotes or sidebars, for advertising, for groups of nav elements, and for other content that is considered separate from the main content of the page.
<hgroup>
The hgroup element represents the heading of a section. The element is used to group a set of h1-h6 elements when the heading has multiple levels, such as subheadings, alternative titles, or taglines.
<header>
The header element represents a group of introductory or navigational aids. A header element is intended to usually contain the section’s heading (an h1-h6 element or an hgroup element), but this is not required. The header element can also be used to wrap a section’s table of contents, a search form, or any relevant logos.
<footer>
The footer element represents a footer for its nearest ancestor sectioning content or sectioning root element. A footer typically contains information about its section such as who wrote it, links to related documents, copyright data, and the like. Footers don’t necessarily have to appear at the end of a section, though they usually do. When the footer element contains entire sections, they represent appendices, indexes, long colophons, verbose license agreements, and other such content.
<time>
The time element represents either a time on a 24 hour clock, or a precise date in the proleptic Gregorian calendar, optionally with a time and a time-zone offset.
<form> <input> attributes
Placeholder Text/Search Boxes
<input type=”search” placeholder=”Search Example.com” name=”s” id=”s” />
Email Addresses
<input type=”email” class=”text-input” name=”email” id=”email” value=”" size=”22″ tabindex=”2″ aria-required=’true’ />
Web Addresses
<input type=”url” class=”text-input” name=”url” id=”url” value=”" size=”22″ tabindex=”3″ />
And as usual, most of this would not be possible without the wonderful CSS3!
More Info
http://www.whatwg.org/
http://diveintohtml5.org/
http://dev.w3.org/html5/spec/Overview.html
and many more arising each day…
Categories: Aron Varghese
Aron Varghese has written 1 articles.
Other articles by this author aron
