CSS Semantics
Continuation of semantic CSS. A new approach, and tries to give a series of advice or recommendations when it comes to the use of style sheets and XHTML code writing. The information is based on the quoted post, as well as the related files. Recommendations for use and writing code using HTML tags strictly to what have conceived if it manages to create a XHTML code as clean and clear as possible will be reduced considerably the number of styles that we have to create and will avoid most of the errors and inconsistencies common. Layout based on layers (div), do not use tables (table). Paragraphs: (p) headers: (h1, h2, h6) tables: (table, thead/tr/th, td/tr/tbody) lists: (ul/li, ol/li) Menus: based on lists with the attribute display: inline use of measures in the sizes of fonts measures are those that do not establish a fixed size in pixels or points to an element. In particular are the percentage (%) and em (1em is equal to 100%, 1.2em to 120%, 0.7em 70%,) is very important to this point by several aspects: not all people have the monitor at the same resolution and our typography may be very small or large depending on the case. Setting typography measurement relative to the tag body, will be the relative size to browser and device that interpret the page.
This is especially on devices with small screens (mobile, pda, etc.). Layout of layers-based fixed layout is an old controversy, the mockup of fixed width or liquid layout or variable size size. Web usability studies advise the use of fixed sizes appropriate to the resolution most used by internet users, trying to be discriminated against percentage the least possible. The explanation of this aspect is justified by the steady growth in sales of large-size monitors (do 17? or more) and resolution (1024 768 onwards). The expansion of the pages on all resolutions of widescreen monitors greatly hinders the readability of text paragraphs. Create styles or redefine them only where strictly necessary if we create our pages making proper use of XHTML tags and follow the guidelines outlined in this document, the necessity of creating redundant and unnecessary styles, will drastically reduce what entails enormous benefits on all relating to ease of maintenance and reduction of errors and strange behaviors. Original author and source of the article.
Tags: news