Specifications Introduction
This is the introduction to a series of articles I’m referring to as the Specifications (or sometimes site specifications), which collectively concern the architecture of wion.com. I consider this important content just like any site’s legal mentions or accessibility statement. In fact, I originally meant for the specifications to compliment my Accessibility page, but I have since decided to include the accessibility article in the Specifications suite of articles for this site. You will find the associated articles listed in the column at right (or following this introductory article if you are navigating by keyboard).
Aside from my Platform and System details, minutiae once trendy in colophon pages, the purpose of the site specifications is to clarify how certain aspects of content and code development are being employed. The Code Specifications in particular (which I’m still drafting) are on code topics heavily discussed in developer and designer circles, and for which there is never widespread agreement about. I try to pull and utilize from those discussions what seems the less evil of techniques, and which fits into my own feelings under the multitude of factors that make perfect web design impossible.
I am generally more concerned with accessibility over anything else so if a given page has good accessibility but does not pass some automated validation test, well, too bad for the automated validation test. You may not prescribe to all the methods I employ, and I don’t claim to be employing the best methods at any given moment. The point is to simply let readers know how things function so they can adjust if necessary.
As the wion.com Content Change Policy makes clear, content may change at any time in this site without notice or indication where, and that includes changes to content, semantics, code, or anything else. I am aware of certain issues I need to improve and/or follow-up on. I keep note of these things in the Accessibility page under the Site To Do List section, which I will get to as I find the time.
Of course I am always grateful for courteous, constructive feedback — either via my contact page or in article comments — about alternate approaches to anything I discuss.
