12/12/2024
55 reasons to design in XHTML
In no particular order 55 reasons for me to do “tableless†websites using valid XHTML for markup, CSS for layout and Flash sparingly, only as an ingredient. By tableless I mean avoiding tables (or a tagsoup of unnecessary divs substituting table trs and tds) for layout purposes and aiming towards as semantic markup as possible. Some of the reasons are “over HTML", some “over Flash full monty†and some over both.
I know this topic has been discussed a plenty, I just needed to reaffirm myself :)
Here we go:
- You can get free links from showcase sites like zengarden, stylegala, cssimport or cssbeauty
- You don’t have to spend extra thought and time deciding on styling the mark up of your document (upper- or lowercase, quotes or no quotes on attributes)
- You don’t need to spend extra thought on which tags should be closed and which can (or should) be left open
- You “help†the search engines to deliver more relevant content using semantic markup
- You can save in bandwidth costs and visitors will see them faster by making slimmer pages
- It’s going to be easier for you to switch to XHTML 2.0 which will give you more semantic tools
- Once you’ve practised enough, coding pages becomes a whole lot simpler and faster than any table/tr/td tagsoup
- When the coding is faster you can spend more time on thinking about the user experience
- Thinking about semantics of a document helps you to make design and information architecture decisions
- You can quickly make a dummy site to test your sites information architecture and append a look and feel later with only minor code changes
- You can do the design after most of the backend is done which will help your client (or boss) to think realistically about how much work is still needed
- It’s possible to link directly to your content pages (compared to Flash)
- browser controls like text-size and back and forward buttons work (compared to Flash)
- Redesigns and realigns over the whole site are simpler
- it’s simpler to make small last minute changes to your designs
- Clean markup makes it easier or even unnecessary to build a CMS
- Clean markup makes it easier for another developer to jump on board
- You can make the backend almost totally independently from the frontend design, by completely different person
- You have plenty of ways to play with the markup trying to optimize for search engines, without affecting visible layout
- You have total control on print layouts of your pages
- Your sites are automatically accessible to all kinds of browsers
- Promoting web standards will help your work in the future, not having to code differently to each browser
- With all elemets closed you mark up look cleaner
- Well-formed code ensures your site works in more browsers
- Well-formed code would help browser coders to spend more time on useful features than rendering engines that try to understand borken code
- Your website will work in future browsers
- Your website works in mobile (and other new) devices
- You learn the basics of XML which has many other uses
- CSS files are saved in browser cache for fast retrieval and less bandwidth use
- Your documents are easy to convert back and forth another format using XSLT
- Thinking semantics makes you think more about the content
- Learning semantics makes you appreciate organization and write your other documents (even emails) in more organized way
- You can write new technologies in your CV or portfolio
- Modern browsers render a valid document faster
- You feel better about yourself when you are making sites “the right wayâ€
- They are doing it: Dan Cederholm, Jeffrey Zeldman, Jason Santa Maria, Shaun Inman, Cameron Moll, Douglas Bowman, Dave Shea…
- You will belong in a “movement", make good contacts etc.
- You learn to appreciate newer browsers which makes for more competition and later for better browsers
- Blink tag is gone
- Strict coding makes you learn to see mistakes quicker
- You can aim to making some money writing a book about it
- There are more job opportunities if you know these new ways
- You learn better to understand how a browser works
- You can use hacks and techniques with cool names like “be nice to Operaâ€
- you start to care more about metadata, document and character types
- With more people making slimmer pages, the amount of data moving in the whole web will be smaller and all connections faster
- XHTML has a cooler name than HTML
- There are more people thinking about the advantages and disadvantages and coding tricks of XHTML which makes for a bigger learning forum
- You can use basically same markup template for many different websites
- Learning to read and write it fast makes it possible to use cheaper tools (notepad)
- Google knows this:
- 4,380,000 xhtml better than html > 4,370,000 html better than xhtml
- 206 “xhtml is better than html†> 87 “html is better than xhtmlâ€
- 2,130,000 xhtml sucks < 10,300,000 html sucks
- When all browsers start to understand the correct MIME-type (xml), you don’t have to convert all your websites from html, just to switch to correct MIME
- By more people using xhtml you ensure that in the future IE will need to understand the correct MIME-type
- Accessibility is enforced with requiring Alt attribute for images
- There just aren’t this many reasons to use HTML or entirely Flash instead
Reference: http://www.khmerang.com/index.php?p=106