Baseline: Markup
The other week I posted a CSS Baseline. So I’ve decided to create its counterpart: a Markup Baseline. I put some thought into if I should create a markup baseline in the first place. I can’t find any other attempts to create something like this. I believe this is due to the issues I ran into when creating this baseline.
Issues
Purpose
Well formed markup (semantic markup that is) is based on the content. Content is usually based on the purpose of a site. So how would you make a baseline all different kinds of content? You might just end up with a baseline for every different type of website out there. There would be millions of baselines then. And that wouldn’t be very productive.
doctype
Different types of sites may require different doctypes. I thought about making some php functions that would switch the doctype based upon your preference. That seemed a bit more like a framework and out of the scope of this project.
The Baseline
I’ve noticed over the years that I have been creating websites in similar fashion. Websites I’ve created lately have followed a set of ideas that I’ve concocted. The basics of theses ideas start with the structure of the web page. You can usually distill web page structure down to 4 major areas: the header, navigation, the main content area and the footer. Now this doesn’t work in all cases but it should work for most. Again this is an issue with the purpose of the site or page. However most sites will have these 4 elements. In the end I settled on the basic structure of 4 major elements and the XHTML 1.0 Strict doctype.
