Web designing trends keep on changing and HTML 5 has emerged as the new revolutionary revision to the current HTML which is the core markup language for the web. HTML 5 will probably be the next standard to web designing and will stay for years to come.
It’s a project started by W3C and WHATWG with the support from the four major browsers namely Mozilla, Opera, Microsoft and Apple. Although a long period of final completion stands ahead for HTML 5 but many of its features are already supported by the major browsers.
Major Browsers supporting HTML 5 today:
- Safari
- Firefox
- Chrome
- Opera
Structure of HTML 5
Every innovation adds and supplements the existing process. Similarly, HTML 5 also makes web page structuring an easy process. Div elements are used in the current HTML 4, but HTML 5 tackles this problem by introducing elements that represent each section individually. The structure for a page with a header, footer, sidebar and content will be represented this way in HTML 5:
|
<header> |
|
|
<navigation> |
|
|
<article> <section> |
<aside> |
|
<footer> |
|
Audio & Video elements:
HTML 5 fresh audio and video features will make embedding media into a site a very easy task. You’ll be saved from using plugins, plus it can all be managed by using scripts. This gives two benefits 1) simplicity in use 2) provision of excellent interface for authors.
Canvas:
The canvas is another interesting “drawing” feature introduced in HTML 5. The canvas element will allow you to design games, animations and high-end graphics without much trouble.
Drag & Drop:
Enables you to drag an entity from one place and drop to another. This utilizes JavaScript which work as a complete drag and drop function.
There are so many new features to look forward to in HTML 5, so keep your fingers crossed as there’s much more on its way!
3 comments ↓
HTML 5 represents web design coming out of the dark ages. It isn’t just a significant and noteworthy advancement, it represents an understanding in creativity, art, media and the flow of the production process.
More needs to be done, though. Browser wars continue to impede progress as they look to promote their own brand’s and codec as the default solution. And there is no true web authority to lay down the law on these characters who fight like dysfunctional in-laws. Here too, the world’s governments fail to step in to help resolve issues because it doesn’t even understand this technology, or that the lack of its advancement is helping to promote the stagnation of our global economy.
But HTML 5 is the answer. Not in its present form, but as it evolves and support for it finally surfaces across all platforms. Which is the trouble, as browser companies squabble about minor issues in order to promote their own brand, their self serving brand oriented corporate muscling and protectionist attitude holds up progress for the entire rest of the world.
I honestly think that HTML 5 will change the world, eventually. But support is key. Why Microsoft Internet Explorer continues to hold-up the show should be considered criminal. I cannot understand why it instists on being seen as the bad guy in tecnology development when it comes to the web. Of course, Microsoft never has seemed to “get the internet”. But they are not alone in blame for the wishy-washy support for the HTML 5 standard support, either. All browser entities are guilty because they are still promoting their own interests in a standardized codec. And this idiocy continues to overshadow the technology and impeded progress.
Should they have placed the development of the HTML 5 standard into the hands of a capable independent organization of web designers and developers? They did. And yet many of these issues we looked to the W3C and WHATWG for guidance on were ignored.
Yet, the corporate dance is still required. I mean, I can start a group to develop HTMLX as an independent group, but no one is going to support it if they are not on-board. And no one is going to want to help unless it has a chance of becoming a real standard.
In the meantime I know that I would have a whole lot more web design work if this standard were a reliable and competitive standard that we could rely on once it is ratified and officially released. But we can’t because of lack of agreement and support on how to handle the and tags.
In a time when we need work and to promote progress in order revitalize the global economy, the w3 (the worldwide web) needs massive attention so that we can put Humpty Dumpty back together again.
I am just one of many web designers experimenting with the HTML 5 standard. I came across a link to this blog post on the subject of HTML 5 Stuff in the Web Design and Development group at Google Groups (http://groups.google.com/group/sitedesign). But I do want better support, and I am calling for the browser industry to get on board. Because with HTML 5 you will have to get on board or die in the coming years. This standard is just too good and helps untie the knots of code which flow and creativity tends to stumble over.
Thanks for your post, I love bringing awareness to HTML 5 and thank you for your effort. I long to learn more about how to use the tag. That tag should be lots of fun in the future.
.-= Doug Peters´s last blog ..4-ΗΜΕΡΗ ΕΚΔΡΟΜΗ ΣΤΗΝ ΖΑΚΥΝΘΟ =-.
Hi Doug,
I really appreciate your concerns about HTML 5. I highly favor the such initiatives and it will be really good if the technology giants and software industry put hands together for setting up the standards so rescue the future. I have read the discussion going on the Group and feel it good to have such inspirational ideas.
I totally agree with you that the lack of agreement and support is a big hurdle for setting up the standard and hence hindering the reliability. The only way I see is the mutual coordination and agreement over the standards and stated tag for HTML 5 that might help the web in future, otherwise it is going to be same as seeking a new version just in a couple of years as of the innovation taking place so certain and speedy.
Anyway thanks for dropping in.
- J.
[...] is displaying my reply to his post, I have decided to try to correct and clarify my response to his original post concerning HTML 5 on his blog [...]