One of the class projects for my WordPress college course involved the students working together on a single broken post to find all the errors in the content. Typically, this is a quick test of their basic coding skills, but this quarter’s students are not typical. They are exceptional.
The goal was to identify and fix typical errors found in content. This is an often overlooked issue with any site development. Web designers and developers are quick to leap into the code to find the issue, overlooking the fact that is it often the user generated content, the code in the posts and articles, that cause the break in the design. Many site errors are caused by you or the client pasting in word processing or website content into the Visual Editor of WordPress, bringing with it all the clutter code that cripples the site when the page is published. I’ve spent hours trying to fix sites clients screwed up, only to find the issue in the post not the whole site.
The students discovered most of the errors as part of the exercise. What several of them did with the errors to resolve the crippled code issues was fascinating, and telling. I’m sure many of us might make the same decisions, making this an ideal blog exercise.
One of the errors was with a malformed hyperlink code. The HTML Anchor tag (link tag) wasn’t closed, so the link ran all the way down the page. Instead of closing the tag, one student removed the link, justifying his action with “there were too many links in the article anyway.”
Many in the class, including myself, were stunned by his action and laughed at his assumption.