Aja Lapus

Category: Standards

  • UST Web Site Redesign

    I was trying to check the University calendar on the UST Web site for the preliminary examinations schedule when I noticed the redesign and restructure planned for it has already been implemented. Excitedly, I saw some of the things I’ve dreamt of doing for it[1] accomplished on the reboot.[2]

    These include:

    • Porting the site from ASP to PHP; and,
    • Complying with the XHTML 1.0 and the CSS 2 recommendations.

    A very clean design added to its beauty and usability. And, scripting features that makes the layout fluid or fixed, as well as changing the font size according to the users’ preferences, made it more accessible. Two very good steps to have been taken, IMO.

    I remember checking it a day after the said reboot, the news roller was a bit misaligned in Mozilla Firefox, Opera and Safari,[3] but was rendered as desired in Internet Explorer 7. Now, four days later, after browsing it again to continue writing this post, I see they’ve already fixed the alignment problem for the major browsers with the exception of Safari/Win—now I have nothing to rant about the site being made with only IE anymore. Heh.

    The new design also features compliance badges from W3C, which results to only a single markup error that is, IMO, fairly forgivable for an elaborate design and a complex site structure. That error may even be caused by the CMS[4] itself for one of its modules automatically placing a <link /> to a style sheet wherever it was inserted.

    I haven’t seen much improvement in a single reboot for the site as far as I could remember.[5] The move to open source software, Web standards compliance, and accessibility with usability is, IMO, the best direction any Web site could have taken. Kudos to the Webmasters of the new UST Web site!

    Footnotes:

    1. ^ when I volunteered to be a TomasinoWeb member
    2. ^ another term for redesign; from CSS Reboot
    3. ^ all on the Windows platform
    4. ^ namely, Joomla!
    5. ^ with three designs, as of now

  • Hindering Standards Advancement

    IMO, there are two ways to hinder the advancement of Web standards:

    1. To continue legacy practices, holding back on new, better ones; and
    2. To keep inconsistencies between Web developers and designers, and user agent, tool and software developers.

    Legacy Practices

    I still haven’t studied much about the endianness of character encodings, but it sure is one thing I’ve seen that exhibits a legacy practice recommended by W3C. I’ve been placing a Unicode Byte-Order Mark before the output of my WordPress themes since my text editor featured its control on UTF-8 encoded files. After subjecting it to the W3C Markup Validation Service, I encountered a warning that says:

    The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use until it is better supported.

    I’ve actually tried placing the BOM because Google Webmaster Tools report my site to have been encoded in ASCII even though I have set the HTTP Headers to respond, and <meta/> elements to indicate otherwise. After doing so, Google Webmaster Tools reported about 50% of my site is on UTF-8 that I concluded it reads pages’ encodings using the BOM.

    The first time I’ve read that warning, an insight immediately struck me regarding legacy systems and practices. So, I just want to ask: Why are they enforcing legacy practices to be continued by Web designers and developers instead of enforcing new and current standards to be implemented by user agent, tool and software developers?

    Incomplete Implementation

    I’ve written much of the above article about a week ago, but it just came short of publication. I thought my so-called insight is very limited with regards to the current issues between Web and software development that I decided to postpone publication. It still would be on draft status if not for Molly Holzschlag saying just recently, HTML5 and XHTML 1.1+ MUST Stop for Now. I was puzzled why one of the most famous standardistas I look up to said that. The title would seem to mean she has just begun to dislike the improvements to Web standards. But after reading the whole article, I totally agreed. BTW, she meant:

    1. COMPLETE HTML 4.1 [sic], XHTML 1.0 and CSS 2.1 in specs and browsers where applicable
    2. CALL for consistent implementation of these most basic specifications in all current browsers and devices to this point
    3. WAIT for future HTML, XHTML and CSS implementations until these implementations are complete
    4. FOCUS on JavaScript and DOM fixes and implementations as we come up to par with markup and style

    The only way new Web standards would be supported is to implement completely the current and existing ones. This would also make legacy practices be needed no more. Molly didn’t say that the progression of Web standards should be stopped forever, but the terms for now should be emphasized as long as incomplete implementations exist—and she’s talking about no specific user agent as even Mozilla, Opera and Safari have no perfect support, just better ones. So … I question no more.

  • Redesign At Long Last

    I have announced a redesign more than a month ago, but since WP 2.2 has been delayed, I decided to delay it as well. It’s finished now … well, almost. The upgrading process and the redesign exhausted me. So this post will just be a placeholder. Place your comments here, but I will surely edit this entry later.

    I was just worried about some things the upgrade did to my database, it seems that some non-Latin characters was converted to something else. I will investigate on this matter after I wake up later this morning.

    *after waking up this afternoon*

    After years of having single color accents, I’ve decided to take on dual-color accents to be used on this new design. I just love having complementary orange and blue on almost anything, now they’re on my Web site as well.

    Some pages still wouldn’t work, and some are still being rewritten. The new Projects page will be used to organize all my work including Web development and WordPress plugin development pages.

    This design has been tested on Firefox 2.0.0.x, Opera 9.x and Internet Explorer 7. I may include some bug fixes for Internet Explorer 6 as I discover it, but don’t count on it.

    Credits go to Feed Icons for the standard feed icon, and to FamFamFam for the cute little Silk icons I’ve used throughout the whole site.

    Thanks to Arvin for pointing out that my comment form didn’t work. I’ve only used id attributes on the form elements that browsers handling HTML-compatible XHTML wouldn’t process as query string variable names like what they do on name attributes.

    Criticisms are welcome. 🙂

  • I’m Getting Naked

    It’s already summertime and most people are stripping down to their trunks and bikinis to get wet with friends or their families on the beach or on a pool. Me? I’m here stuck inside my room stripping … and this is not an April Fool’s joke … stripping my website buck naked off of its stylesheets. *tee-hee* Well, anyway, I’ve done this before and I’m doing it again. Last year was good, and I hope this time is better. Dustin Diaz is finally proving the annual in Annual CSS Naked Day.[1]

    To anyone who isn’t familiar, CSS Naked Day was made to promote standards. During the 1990s, HTML has grown to become a more presentational language than what it was really meant to be. With browser implementations varying from each other,[2] and the bulk of maintenance work that HTML has become to present aesthetics, proposals were made to have a presentational language that later became what is now CSS. CSS has already replaced every presentational bit of HTML 3.2 and has even added more, and with the advent of better support to the standard since late last year, it is really worth advocating for better and wider Web designer adoption.

    The reason for stripping CSS off for a day has been acknowledged by the creator of CSS himself, Håkon Wium Lie—saving HTML from becoming a presentational language. I’ve seen many sites that produce good aesthetics, but the perceived quality just stops there. As I turn off the styles on my browser,[3] the layout remains the same, but now with garbled images and incomprehensible text. And they say they’re standardistas.[4]

    I hope everyone who have read this participates in the upcoming second year of the celebration of semantic markup. It’s very nice to see that two, Shari and Mr. J, out of currently four links from the official page that are talking about the event are of Filipino blogs. If you think your site doesn’t qualify to having semantic markup, you still have four days to this year’s deadline. Registration is now open [and automated] at the Official CSS Naked Day site.

    Oh, and for those WordPress users that are too lazy to edit themes, I’ve made a plugin that strips every piece of stylesheet in your pages without a single tweak on your templates—configurable to follow the recommended 48-hour period or just your local 24-hour April 5.

    Footnotes:

    1. ^ I really do not know why they call the first time, annual, already.
    2. ^ As a result of the first browser war.
    3. ^ The way everyone, humans and bots alike, are to understand the page.
    4. ^ I would have told them privately that all but one of the sites in their gallery wasn’t compliant, but it seems that their feedback link isn’t operational. So, just consider this as feedback. Oh, I do hope the site submissions be screened better as it would be a good starting point for showcasing great Pinoy designs.

  • New Way to Get Involved

    If you happen to be an advocate of anything—may it be Web-related or not—it really wouldn’t hurt to get out of your lazy sitting position and go out to reach a broader set of people. Web-wise, this has been done successfully on the Spread Firefox Web site with its members, and business-wise, on record companies and bands with street teams. Now, my advocacy followed suit.

    The Web Standards Project announced the formation of the WaSP Street Team during the WaSP Annual Meeting held at SxSW—to take the advocacy out to the streets—or possibly everywhere you might be involved with.

    There could be a little disadvantage to this, since you aim for the Web user and you take the promotions out anywhere around the real world, you may be shooting at the wrong people. But, of course, the primary advantage with this move by WaSP, in my point of view, is to let the person who uses the Web know what Web standards are even if they do not browse such scary tech or Web standards-related sites just by knowing them in the streets they walk on everyday.

    I still do not clearly know what WaSP plans as the first task for its Street Team. But, you could sign up for announcements from its mailing list on the Street Team homepage. Could this be the answer to the standards awareness problem? I really hope so. Let us watch out what it could do for the Web standards community. Be aware. Get involved. Get the message out everywhere, together.

    Oh, I remember you could also join us in discussion on Web Standards Philippines. Just send me a message or leave a comment on this entry so I could add you on to the Basecamp. 🙂