Having trouble with your html code?
Almost all bloggers will come across a coding issue at some point. Whether you are embedding a video, adding a template, or changing the color of your font, knowing the basics of html will help you along the way.
A good habit to get into when you start writing and editing code is to validate your html (think of it as spell check for your code). Even experienced coders come across issues with optimizing their code to display properly on various browsers and operating systems. Some examples include: your blog looks great on one page but not on another, or your font size displays exactly the way you want it on one browser, but it's bold on another. This could be a simple case of missing a closing tag somewhere in your code.
At any rate, it's always a good idea to validate your html code to meet web standards. The World Wide Web Consortium (WC3) is an international organization that leads the way in creating these standards for the web. In addition to offering html code references, the WC3 offers a free code validator that allows you to quickly verify that your code is correct.
CHECK YOUR CODE HERE: http://validator.w3.org/#validate_by_input
*There are a ton of options out there for creating and editing your html code. If you are using Mozilla Firefox, try installing the Firebug plugin. This allows you to check your code for errors directly on the page!
1) Paste, upload, or link your code to the validator

___________________________________________________________________________
2) Check your code using the "check button" to see how many (or little) errors you have

___________________________________________________________________________
3) The validation service will provide specific details about your code issues including the line and columns numbers so you can find and fix the problem(s)

___________________________________________________________________________
Still having problems that you can't fix? Send us a message and we'll see how we can help.
Cheers!

Comments (5)Subscribe to CommentsComment