Monday 7 April 2008

Design Coding: Rap for The Rest of Us

The very awesome iJustine posted this like ten days ago, but I can’t stop watching it, it’s just that yummy.

Just(in)e case you haven’t seen it, I’m re-sharing it here and hope you enjoy it as much as I have!

BTW, who did this bit of brilliance? Where was it filmed?

Comments are open, I want to know.

Enjoy:

Design Coding

Your site design is the first thing people see
it should be reflective of you and the industry
easy to look at with a nice navigation
when you can’t find what you want it causes frustration

a clear Call to action to increase the temptation
use appealing graphics they create motivation
if you have animation
use with moderation
cause search engines can’t index the information

display the logos of all your associations
highlight your contact info that’s an obligation
create a clean design you can use some decoration
but to try to prevent any client hesitation

every page that they click should provide and explanation
should be easy to understand like having a conversation
when you design the style go ahead and use your imagination

but make sure you use correct color combinations
do some investigation, look at other organizations
but don’t duplicate or you might face a litigation
design done, congratulations but it’s time to start construction

follow these instructions when you move into production
your photoshop functions then slice that design
do your layout with divs make sure that it’s aligned
please don’t use tables even though they work fine
when it come to indexing they give searches a hard time

make it easy for the spiders to crawl what you provide
remove font type, font color and font size
no background colors, keep your coding real neat

tag your look and feel on a separate style sheet
better results with xml and css
now you making progress, a lil closer to success
describe your doctype so the browser can relate
make sure you do it great or it won’t validate

check in all browsers, I do it directly
gotta make sure that it renders correctly
some use IE, some others use Flock
some use AOL, I use Firefox

title everything including links and images
don’t use italics, use emphasis
don’t use bold, please use strong
if you use bold that’s old and wrong

when you use CSS, you page will load quicker
client satisfied like they eating on a snicker
they stuck on your page like you made it with a sticker
and then they convert now that’s the real kicker
make you a lil richer, your site a lil slicker

design and code right man I hope you get the picture
what I’m telling you is true man it should be a scripture
if it’s built right you’ll be the pick of the litter
everyone will want to follow you like twitter
competition will get bitter and you’ll shine like glitter

if you trying to grow your company will get bigger
design and code right man can you get with it

Filed under:   humor, standards, music, pop culture, software, web design and development, society, creativity, browsers, innovation
Posted by:   Molly | 7:27 pm | Comments (17)

Wednesday 5 March 2008

IE8 Beta and Readiness Toolkit

Here it is folks, an actual IE8 beta, overview of features, changes and enhancements, and a readiness toolkit for developers.

Check it out, now, my web soul brothers and sisters!

Filed under:   general, standards, software, web design and development, WaSP, w3c, conferences, announcement, browsers, microsoft, ie7, ajax, javascript, ie8, MIX08
Posted by:   Molly | 12:08 pm | Comments (59)

Monday 3 March 2008

Celebrate, C’mon! IE8 Standards Mode To Be Default

By now you’ve likely read about the big news regarding Microsoft’s commitment to a more interoperable Web, starting with the very good news that standards mode in IE8 will now ship as default.

I’m off to MIX08 tomorrow, and will be attending the keynotes as well as developer discussions on IE8 and additional events surrounding Microsoft’s agenda moving forward. I’ll post more as I’m able.

In the meantime, I just want to shout out a thanks for all the hard work it took this year to keep the IE8 conversation open and alive. We’ve been through some bumpy times, and I for one know that people on the inside of Microsoft faced an enormous amount of pressure in trying to keep that conversation in the public eye.

To all who worked so very hard from both the inside and outside, I toast your dedication, your willingness to challenge what would otherwise be the status quo, and I think it’s really worth taking a celebratory moment to realize that at least for now, the community voice can, and does, truly make a difference.

Filed under:   professional, policies, standards, software, web design and development, society, w3c, conferences, announcement, browsers, microsoft, community
Posted by:   Molly | 10:13 pm | Comments (46)

Wednesday 27 February 2008

Interview: Roger & Molly: Webstock New Zealand

I like this interview! It runs a bit long but Roger made me feel so welcome it just came out as a spontaneous chat.

Anyone willing to do text transcript, holler. I’d like to make one available!

Thank you, Roger, for a great interview.

Enjoy, comment, bitch etc. below:

Filed under:   professional, humor, standards, software, web design and development, travel, food and drink, society, w3c, conferences, announcement, creativity, browsers, microsoft, ie7, innovation, whatwg, community
Posted by:   Molly | 8:12 am | Comments (39)

Saturday 16 February 2008

One Very Phishy Reason to Love IE7?

I’ve been in a wonderful hotel here in Wellington, New Zealand alas, with the crappiest connectivity ever. Then, something rather suspicious began to happen.

Note the URLs - they are the same in each case. Note that the sites are in fact, not the same.

Curious, I thought I’d put a few browsers to the test. Here you see Camino (seemingly) rerouted to someone’s phishy site. Firefox, Opera, Safari and Shiira all FAILed.

Here’s IE7, on Vista, in parallels on my MBP.

Well, that’s just very strangely impressive indeed.

Filed under:   standards, software, web design and development, browsers, microsoft, ie7
Posted by:   Molly | 5:37 am | Comments (37)

Sunday 3 February 2008

Call for Web Standards Quips and Clips

I’m preparing my keynote for Webstock in Wellington, New Zealand, coming up next week. I would very much like a sampling of video shots of a wide range of individual opinions and thoughts answering the question: “What is the definition of Web Standards?” You can be as funny, mean, or weird as you like so long as you have some clear point to make. If you’re an enthusiast, be enthusiastic. If you’re a hater, be a hater. Just have a point, and think of the children

If you’d like to help out, drop a me! please in the comments. Shyness definitely does not apply here. I’ll contact you by email privately with details as to where to send and format, etc.

I’ll be using these clips within the presentation to gain a widespread look at how people define, and feel, about Web standards. Mostly, the point is to demonstrate how it can mean such a variety of things to people from all over the world. The more variety, the better. I will then publish them in the public domain for all to enjoy.

Up for it? Let’s hear from you!

Filed under:   professional, standards, software, web design and development, WaSP, society, w3c, conferences, announcement, browsers, microsoft, accessibility, javascript
Posted by:   Molly | 6:55 pm | Comments (25)

Thursday 31 January 2008

From Web Standards Diva to Web Standards Devo

This post emerges from a comment I wrote to the response thread in my “Web Standards Aren’t” post, which I hope will clarify my thoughts a bit as well as take a lighter look at what I’m working to articulate here.

I’ve decided to become a Devo rather than a Diva. I’m going to design my new site with frames, tables, spacer gifs, lots of flash embedded into framed pages via iframes. I’m going to use non-semantic, presentational HTML, table based layouts, and lots of inline CSS.

The frightening issue is that I can build such a site so it will validate, pass at least WCAG priority 1 accessibility and have effective SEO.

The mere fact that I can actually do all that and be in compliance with specs should help clarify my point, I hope. It’s not the specs that define Web Standards. We are talking about best practices. We use the term “standards” fast and loose, and for an industry that is so interested in semantics, I find it endlessly ironic that we have chosen such a piss poor description to define a certain level of professional practices.

We co-opted the term “standards” and applied it to something that wasn’t a standard, rather, a series of specifications that are RECOMMENDED practices.

Am I saying stop working to specs? No. Am I saying we’re on the wrong path as we try and build a better Web by increasing education and awareness around specs and best practices - well, if anyone here thinks I mean that you must not have met me or know me too well. Rest assured my heart is right there, I want a better Web, and that means better practices, more education, more resources, more outreach.

I’m challenging the status quo. I’m just asking that you take a look at the semantics of the situation and not be led into a sense of comfort that we actually have achieved any semblance of a standard. If that were true, all browsers would behave the same way, and my code would be just like your code, and every CMS and development software would be interoperable, use correct nomenclature, and follow the specs.

Is that the Web we have? Clearly not. And as we grow and expand both on the desktop and into mobile devices, these issues become more fragmented, not less.

Filed under:   professional, standards, software, web design and development, society, w3c, browsers, accessibility, community
Posted by:   Molly | 6:49 pm | Comments (46)

Web Standards Aren’t

After a fantastic day in Perth I ended up talking to a group of oil workers. Men of all classes and walks of life. Scottish, English, Aussie. Tattoos, guys with attitude, heart, and an amazing decency of soul.

An engineer on an oil rig finds a fitting that’s defective. He tells his mates to fix or replace the fitting.

Following manufacturing specs, the person given the task consults the specs, and he builds it just so.

It fits, and will function. If it does not fit, it is not allowed to be used. Those are standards. The products developed meet manufacturing specs world over, and that’s that.

What we have today, on the Web, are not standards in the truest sense. We are at a time in the evolution of the Web where the idea of “standards” is more of a profound misnomer than ever.

Please Define Web Standards

Bet an Aussie dollar you can’t!

Most folks reading this post will say Web standards are markup and CSS, and maybe, just maybe, accessibility.

So what about JavaScript?

If you’re really smart, you raised your hand like Arnold Horschack and shouted out: JavaScript.

Surprise you markup and CSS pedantics, you know, that’s a “standard” too.

Democracy Killed My Grandma

The democratic Web fosters anarchy. That’s not a bad thing per se. I like the idea of anyone having a soap box. It makes for intrigue if not logic.

But professional sites must set some practice that is equivalent to all counterparts. And also supports my Mum when she wants to post a photo.

Don’t you agree?

Context, He Said, Is Everything

There’s a reason that we don’t have standards on the Web, or clearly understand what “standards” really are. The bottom line is it’s not that important.

Web standards aren’t, because democracy demands it.

The grand paradox is that our professional world demands a standard that can be measured and judged. And yet, we need to be free to not be conformists.

Web Standards Really Aren’t

Go ahead, tell me what they are. I know you can’t, because they aren’t. We have specifications, recommendations, implementations and a lot of best practice chatter.

What we do not have is the ace that will fit perfectly in the hole. Web standards aren’t.

It’s time to move on to whatever is next.

Filed under:   professional, standards, software, web design and development, WaSP, society, w3c, browsers, microsoft, ajax, innovation, accessibility, javascript, whatwg
Posted by:   Molly | 8:28 am | Comments (52)

Monday 28 January 2008

W3C HTML5 Working Draft Published

Today the W3C announced that it has formally published the W3C working draft version of HTML5.

According to Tim Berners-Lee:

“I am glad to see that the community of developers, including browser vendors, is working together to create the best possible path for the Web”

Clearly, Tim remains as optimistic as ever, but from the evidence of the last few weeks, it’s clear this isn’t exactly as happy a situation as it’s made out to be. But, the work is continuing, and that’s noteworthy in and of itself.

Filed under:   professional, standards, software, web design and development, w3c, announcement, browsers, whatwg, community
Posted by:   Molly | 8:38 pm | Comments (20)

Thursday 24 January 2008

Me, IE8 and Microsoft Versioning

If you work in Web design and development and haven’t read any of the articles and discussions taking place regarding IE8 and its use of meta versioning for standards compliance, it’s time to read up on it ASAP. Begin with Aaron Gustafson’s “Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8” on A List Apart. You can follow the threads from there. Russ Weakley at maxdesign is keeping a good list of the conversations too, so you can drop by and fill up on all
the mud-slinging and drama as it unfolds.

Burning truths

I began to write a response to Shelley Powers’ formidable “Bobbing Heads and the IE8 Meta Tag.” In this article, I’m cited as being in compliance with the Microsoft meta option. At first I resisted that I was being “compliant,” thinking that despite my discomfort with the option, I thought (and still do think) that it was the best solution that came up during the year-long versioning discussion we had.

The year long, very private, NDA’d versioning discussion. Which is where I have to agree with those who cite me as being “compliant.”

Because this was not a public discussion, and because I and others both internally and externally failed to convince Microsoft to make it a public discussion (although to their credit they did bring in industry advocates), I am in fact in compliance with the meta choice.

However, this doesn’t mean I agree it’s the right thing to do. I can say that I think it was the best of a list of much more problematic options that were presented. Just think about what naturally came up at first, attaching to the DOCTYPE switch or encouraging the use of conditional comments are both easily identified (but also very problematic) possibilities. And just because I did in the end agree that this was the better choice has nothing to do with silence. We all had legal and ethical responsibilities in that process.

I wish, oh how I wish, we could have all worked on this openly and together. That would have been my dream, but alas, it wasn’t to be.

Holding back the tears

When I began to talk to Microsoft and IE via the WaSP Microsoft Task Force, the conversation was far more open, or at least it appeared that way. When I left WaSP to work with Microsoft in a liaison capacity, that was still true. Over the past few years changes within the company infrastructure led to changes for the IE management hierarchy, and suddenly things got very quiet.

Silence can equal consent, indeed. Which is why I personally focused on breaking that silence. It took enormous pressure internally (and frankly, I believe that’s continuing) as well as my blatantly asking Bill Gates about it this past December to push the doors open again. Finally, this allowed Aaron, who was part of that long versioning discussion, to publicly talk about the switching work being done.

If those hands had not been forced, no one would have heard about this until IE8 landed on our doorsteps.

Out the issues

Now it’s out in the open, prior to a beta. We now know a hell of a lot about IE8 because of this. We can take a damned good guess at what’s actually in IE8 standards-wise because in IE8 standards mode, we have Acid2 compliance. Break down Acid2, and you’ll see what those implementations are or will be.

I believe we are in a much better situation knowing all of this in advance of the product. Was it wrong for Microsoft to shut up? I say yes and I call foul on those folks within the organization who allowed the very positive and productive conversations be shut down so dramatically. Clearly, they made a drastic mistake, which they were warned about by internal folks as well as advisors over and over and over again. So, the more yelling that comes from the Web community and the public press, well, that’s a message Microsoft will listen to so let’s remember that and hope some good comes of it.

Honestly, would it have been better to hide all this information until IE8 landed on our doorsteps? I don’t think so. At least now we have a window into what Microsoft is doing and the conversation, as is evidenced by the activity of the last week, is outed.

Transparency is bullshit, let’s get naked

Open standards must emerge from public, open, bare discussion. Microsoft clearly does not agree with this. It goes against its capitalist cover-up mentality, even when Bill Gates himself has quite adamantly stated that there should be no secrecy around IE8. In fact, he was the one who let the name slip. The fucking name, people! This shows you how ludicrous the lack of communication had become: Gates himself didn’t even know we weren’t allowed to say “IE8.”

This covert behavior is a profound conflict for me as I’m sure readers will at least agree that I’m pretty darned overt by default. But I knew it going in, I just kept and am still keeping my hopes high because that is also my default.

Sometimes the solution is to step back and re-evaluate. Sometimes the solution is to walk away. I haven’t firmed up my personal decisions on that just yet. Maybe it’s time to go back to Old School WaSP-style stinging of MS, but that definitely is not my default.

Can’t we all just get along? No, really. During my time at WaSP, the door was open to a kinder, gentler way. More fool me? So be it. I’m not giving up the greater goal, which is keeping the Web open, free, naked, bare-assed to the world.

Of, by and for

I think about all of us, whether we are “for” or “against” a given approach in the context of Web technologies in general, and I realize how necessary our arguments are. We are some of the world’s smartest, most innovative, committed and passionate people. How we’ll start figuring out better ways to collaborate, change old-school thinking, and encourage positive innovation and growth for the Web, well fuck if I know. Been down several roads (WaSP, for example) to try and see just how to do that.

What I do know is that the Web is still of the people, by the people, and for the people, no matter what Microsoft or anyone else does. And we’re the people to keep it that way. It’s not the what, but the how, and the when, that we have to focus on.

Filed under:   professional, policies, standards, software, web design and development, WaSP, society, w3c, browsers, microsoft, accessibility, javascript, whatwg, community
Posted by:   Molly | 10:22 pm | Comments (67)

Tuesday 22 January 2008

TravelBlog 2008: Australia and New Zealand

I’m in Houston and in a few hours will board a plane that will take me to Guam, then on to Cairns and points in Australia and New Zealand.

There are two concise reasons this trip is important to me:

1). 2008 marks the 20th (yes, that’s TWENTIETH) year online (bbs’s anyone?)
2). I turn 45 on the 25. It’s a rite of passage, I think.

For one month I’m going to explore Australia and New Zealand. I will post photos and ideas and inspiration.

I am also working hard, my current project: massive HTML and CSS testing for MS.

I’m very excited.

Filed under:   professional, standards, software, web design and development, travel, food and drink, society, w3c, browsers, microsoft, ajax, rails, accessibility, javascript, whatwg, The Daily Molly, community
Posted by:   Molly | 12:01 am | Comments (40)

Saturday 12 January 2008

Too Wired in a Wireless World?

When traveling, I always notice I need to pack extra cables and wires, transformers and adapters.

The luggage I pack is sometimes filled with so many wires, cables, power supplies and other do-das that I am quick to wonder if something about all this is a bit fishy.

Do you have more cables now as a result of all our “wireless” devices or less than when we were “wired”?

Filed under:   software, web design and development, hardware, browsers, molly asks you
Posted by:   Molly | 5:23 pm | Comments (36)

Sunday 30 December 2007

Strangest Dream: End to Browser Wars?

(original lyrics by Ed McCurdy and known to most because of Paul Simon, thx guys)

Strangest Dream (Web version)

Last night I had the strangest dream
I’ve ever dreamt before
I dreamed we had all agreed
To put an end to browser war

I dreamed I saw a mighty room
Filled with women (but mostly men)
And the papers they were signing said
They’d not do specs wrong again

And when the specs all were signed
And a million copies made
Some joined hands and thought they’d have a prayer
About the specifications, made

And the people on the Web below
Were running up and down
While markup and scripting and browser wars
Were scattered all around

Last night I had the strangest dream
I’ve ever dreamt before
I dreamed that we had all agreed
To put an end to browser wars.

Filed under:   professional, humor, music, pop culture, software, web design and development, creativity, browsers, community
Posted by:   Molly | 7:55 am | Comments (31)

Friday 28 December 2007

Best Bets for Browser Bug Bashing

One of the most frustrating, time consuming and challenging aspects of managing cross-browser rendering of CSS is dealing with bugs along with incomplete implementations. Examining helpful resources such as position is everything and QuirksMode, it becomes profoundly clear that today’s front end web designer and developer must be pretty adept at dealing with this core problem.

I call it a core problem because of course, interoperability is a problem the Web was meant to solve! Yet, the disparities in Web browsers have in fact caused the greatest accessibility challenge to the Web we as its authors must face, and conquer.

Fortunately, there are some proven ways to deal with cross-browser challenges. We can use hacks, which of course are controversial in their own right due in large part to how difficult they are to maintain and how often they are based on invalid markup or parsing errors (* html anyone?).

We can use conditional comments for managing IE versions. CC’s are in my opinion the cleanest way to manage IE issues on a case by case basis, but they too are controversial. An HTML comment was never intended to contain a conditional statement, so a CC is essentially a hack. Furthermore, it’s an IE-specific solution, so that in and of itself smells a little funny to the purist nose.

Another approach involves using JavaScript to “correct” browser behaviors, such as we find with Dean Edwards’ IE7 Scripts.

What ends up happening, as we all know, is that we use a combination of these techniques where necessary to address our browser base.

So we have the techniques: Three primary ways we approach bug bashing and implementation problems. What’s missing isn’t our knowledge, but a conventional method. If we had a step-by-step procedural to walk ourselves through, that could be very helpful. Clearly, what works for one site isn’t necessarily going to apply to another, but some guidelines to help each other manage this very murky, very challenging problem would certainly be of benefit.

My intuition and experience suggest that the most effective way to manage bugs is to kill them where they live. That means having a clear workflow from the earliest stages of authoring to manage browser issues regarding CSS. Surely many folks will have created such workflows, perhaps even unaware that you’ve done so, as it’s just become part of your process.

Think about how you work and if you could take a moment to share your best bets for managing cross-browser CSS design, we can together examine the least time-consuming, most efficient and most solid method by which to bash those bad, bad bugs.

Filed under:   standards, web design and development, browsers, molly asks you
Posted by:   Molly | 12:26 pm | Comments (50)

Wednesday 19 December 2007

Yes Ladies and Gentlemen, We Have a Smiley

During the past week’s drama related to Microsoft’s lack of transparency and problems with working groups and browser vendors, it literally pained me so to have to keep my mouth shut when I knew there were some very good things happening.

I’m glad Bill Gates truly took the time to look into the communication issues, because to quote the man himself from our conversation last week: “There’s not like some deep secret about what we’re doing with IE.”

From the IEblog today, Dean Hachamovich writes:

“Now, with all that context, I’m delighted to tell you that on Wednesday, December 12, Internet Explorer correctly rendered the Acid2 page in IE8 standards mode. While supporting the features tested in Acid2 is important for many reasons, it is just one of several milestones for the interoperability, standards compliance, and backwards compatibility that we’re committed to for this release. We will blog more on these topics . . .

For IE8, we want to communicate facts, not aspirations. We’re posting this information now because we have real working code checked in and we’re confident about delivering it in the final product. We’re listening to the feedback about IE, and at the same time, we are committed to responsible disclosure and setting expectations properly. Now that we’ve run the test on multiple machines and seen it work, we’re excited to be able to share definitive information.

Would jumping up and down and saying “I told you so” be in order? No, because I couldn’t tell you so. However, I have long been saying that some good things are happening up in Redmond. I applaud the developers who had to keep their mouths closed due to NDA’s and did so under heavy scrutiny, and I applaud all those at Microsoft working hard and proving that they not only hear developer’s needs but understand them and are truly working to make a difference.

Bravo, IE Team, for the hard work and most especially for finally getting the go-ahead to restart this much needed conversation.

Filed under:   professional, policies, standards, software, web design and development, WaSP, w3c, announcement, browsers, microsoft, community
Posted by:   Molly | 2:07 pm | Comments (113)