Blogs

We have previously outlined the benefits of XML markup for general content and transforming it for web presentation, or the markup and presentation of all web content in XML thereby limiting the presentation of such content to web browsers and clients that support XML. The underlying idea of that suggestion was motivated by the need to maintain the fluid flexibility of XML in all web markup so that it should not become obsolete and require manual markup, or manual translation.

Modular XHTML

Previously, I described a situation in which the Alpha test version for HTML-Kit tools for windows that I have been testing for some time was causing my HP laptop to crash when I made operations that required the application to search a local or FTP file system. I have repeatedly reported this issue to the Chami HTML-Kit development team, and they have been either unable to duplicate the issue, or they have not found a relationship between their application, and the error notes generated my Windows XP during the crash.

Are you of the thinking that if something looks good is a respectable web browser such as Firefox, Safari, Opera, or Internet Explorer, then it is satisfactory (especially if the code also validates using the W3C validator)? Have you ever tried to browse the web using a screen-reader such as JAWS or Opera Browser/Audible?

Building an inaccessible web

Content and application accessibility is not being regarded with as much importance as it deserves.

An effective, flexible and useful Web Content Management System (WCMS) feature

Like many leading Web Content Management Systems, Drupal is especially flexible and powerful when it comes to providing administrators and content managers and publishers with the ability to easily create and maintain custom and flexible user-friendly paths and URLs/URI.

HTML-Kit tools for Windows is coincidentally or the main cause of a constant crash and failure of Windows XP Media Center (Professional). I previously blamed and even uninstalled Apple Safari Web browser for Windows because the problem started occurring soon after I downloaded and installed the beta test version of this web browser.

Those of us that wrote markup for websites more that four (4) years ago are aware of the situation where markup styles and standards become obsolete. Whether or not this could have been prevented by coding markup differently is a question I have had to ask myself when confronted with having to rewrite and improve upon code and website markup that has proven to be buggy, redundant, and far from the contemporary coding and XHTML markup standards

Section 508 (in the USA), and other similar guidelines provide a framework for making information accessible for the less able (handicapped) among us. In web development where standards and uniform design and information presentation regimes are just coming to the fore, content accessibility is work considering. Even if you are not creating products and websites for the government, it is not only fair and just to create accessible websites, but it makes your skills future-proof.

There is a tool out there worth noting. If you have moved away from old version of Internet Explorer, you are able to see how your website looks in Internet Explorer 5.5, IE6, and IE7. The tool is much faster than the other tool available for Apple Safari Previews that takes up to a day to generate previews. Staying on topic, you can access the IE preview tool at: http://ipinfo.info/netrenderer/

When you get punished for attempting to outsmart or unfairly exploit the search-engine formula

Purposefully doing SEO can create the temptation to take some actions that can compromise your objective and even get your site banned at the extreme. Good SEO means getting good content, and building a site that is useful to users, and that is built using light, valid and a high content to markup ratio. The only active SEO you should do is to avoid doing the known 'bad things'.

Not all Web content markup s equal even if all of them may be structurally valid code.