HTML 5: what is it? and what to expect

[visit site]

Most of what you hear about HTML 5 is not entirely clear to the layman as to what it means. If anyone can recall the entire leap from standard html to the Web 2 madness, then brace yourself for the next buzz platform for web development…only, this one has far reaching impact on your web presence if you are not prepared for its overtake.

So what is it?

In the shortest possible term, the way we produce sites today still run elements of code that are at least 10 years old, the basic core structure has not changed all that much. HTML 5 will change that completely and this is why we have paid attention to is rise in the development community popularity over the last 12 months.

The framework is fundamentally the same in many ways, but what is unique to HTML 5 is the difference in structural elements, for example – two of the most common are <header> and <footer> and these remain as standard elements in HTML5.  But what immediately jumps out of the code is elements like <canvas> and <audio>, but as simple as these may appear, these elements perform a far reaching purpose that taps into the API, which gives us as the developer, more freedom to produce applications at the same time giving us entirely new options than having to rely on the traditional data porters like Flash that perform the same tasks at present.

We still have the primary element <nav> which represents a menu element or navigation element, however, we now can break the sections of our layout into more complete separate elements using the new tags <section>, <article>, and <aside>. Most of which are reminiscentof php blocks in applications like WordPress.

So how does this effect us?

Because we have been developing using basic element and lazy syntax for HTML 5 as of June 2009, the majority of the sites we have produced to now have at least some form of HTML 5 readiness. Any site produced prior will have to be overhauled in at least the next 12-24 months, so there is a way to go yet before we can confidently say, we have completely switched and we are not alone.

So why is it important for us to start taking action now?

Like many web trends, HTML 5 is no exception when it comes to time lines and explaining the core of what it really is. But unlike trends, HTML 5 is a dramatic change to the way we actually build sites, and before you know it, it will be firmly in place more rapid than any other code framework we know. The build up to HTML 5 integration is escalating probably because it is what the development community asked the W3 to standardise. So, the main thing is its adoption into everyday development is “now” and not “lets wait and see how it goes” because it is here to stay regardless of its infancy. The promises for this standard are long awaited and welcomed.

Will my site fall apart?

We are not trying to scare anyone, and we certainly do not suggest that this movement toward HTML 5 is a doomsday equivalent of Web Development. Your sites will remain in their current state and in tact and will probably last 2 more years from now. So, if we set the transitional period to HTML 5 for the year 2012, you have at least another couple of years before you should start seriously considering updating your site core structure.

Is there anything we should do to pre-prepare for the change?

Over the next 2 years, existing sites will have elements of HTML 5 to some degree, but not in its entirety, and certainly not enough to take full benefit of its to browser delivery. The bottom line here is, you ither go all the way and have your work completely structured in HTML 5 so that is has the core value in preparation for HTML5 or you wait to the point where we will say we no longer can support your dated framework, and not because we are nasty, but ultimately, phasing out of old structures will be more apparent than ever as things will start to fall apart.

If you need further information, please do not hesitate to contact us.