figure vs img Tag in HMTL5 WordPress Posts

It is quite important to understand by the WordPress (claimed) developers the difference of using figure vs img Tag in HMTL5 WordPress Posts. Possibly the most nice way to understand the difference is understanding the difference between URL and URI. There is another thing – aside. More thing – canvas. HTML5 can be very difficult thing, if the spec is not read properly. There is semantic representation and API in HTML5. Adding a header and few vocabulary actually does not make a clean HTML5 document. It is very dangerous way of developing WordPress themes.

 

figure vs img Tag in HMTL5 WordPress Posts

 

Image is img tag. This is a colorful image of a prototype webpage. Before HTML5 there was no way to represent an image semantically through HTML. Thing was not present. That is why we used this format :

Alt becomes the only way to give some information. This is the result :

Except the alt it has no information. Whether the image has to do with the article or not, this sense could not be conveyed. When are using the old style of HTML, semantically it is not conveying information. Diagrams
photos, code listings – all are figures. So, to be correct, the HTML code should be :

We are embedding it :

CSS actually varies a bit, we managed with “class”. This is simple representation, but we can use more complex stuffs like :

The next thing is aside. aside may be good for Photoblog. Text is of lesser value. Content is probably related and may not be essential in case of Photoblog.

Basically an infographics is not only an image, it conveys huge data. The HTML div element is a generic container for flow of content, which does not inherently represent anything. That is not a great way for HTML5 document to hugely use for using CSS. We have CSS3 pseudo class like for creating that Drop Caps. div class drop caps is not the way to represent the data with a visual aspect. Visual aspect should be handled by CSS3 and javascript library. jQuery is an example library.

Conversion from xHTML to HTML5, actually can not be done. In this way, the web will get bloated with meaningless pieces of data when we have a way to sort. canvas is better for audio, video etc. Reading HTML output and adjusting the PHP is not the right way of initial development. We are hobbyists, we might do that wrong way for kind of back calculation, if you are professional programmer you should not “adjust” in that way from the beginning of creating a HTML5 theme. The problems will be faced in next developments of HTML5 for such “somehow managing” approach.

This Article Has Been Shared 6905 Times!

Facebook Twitter Google+ Pinterest