Without Answers

UX Lx - day 2

Sat, 15 May 2010 12:23:00 +0200

Second day of UX Lx in Lisbon. Some notes taken during sessions:

Open session: Seduction design: forget the art of persuasion - Sarah Morris

First - great sketch notes by Lucy Spence.

And now a few of my notes:

Let’s start with quote: “Casanova was the first interaction designer in the world”. According to Sarah, he always found an attractive woman with a problem. He solved her problem, she was grateful and… well, you can imagine. Then he got bored with her, so he left her and started the whole process again.

And now some serious notes on how to define quality relationship (aplies to partners in life and customers as well):

Invest in quality time
Security and comfort
Dependence / independence
Regular reassurance (Say them how lucky you are they’re with you)
Actively listen and respond
Making the extra effort (little suprises like buy a flower, send a gift card to a customer on his/her birthday)

Sarah also said in her talk, that “nobody can talk at UX conference without mentioning Apple”. So true. This company was like everywhere at UX Lx. And a good half of what Jared Spool talked about was about Apple too.

Great talk.

Open session: Application Design mixing UX, Learning and Knowledge Management Methodologies - Silvia Calvet

This talk was about a project Silvia worked on and they were making some software for a goverment and most of the things they were doing was trying to make people from different departements to talk to each other.

For me nothing really inspiring there. Pity, I met Silvia before and she’s really nice person, maybe was a bit nervous before the audiance?

Workshop: Making Smart Design Decisions (Collaborative techniques for analyzing usability testing data) - Dana Chisnell

This workshop started with a KJ technique. (Link leads to Jared Spools article about it, if you don’t know it.)

We were answering the question: “What obsacles do teams face in implementing user experience design pracices?” and what we came up with was lack of time, lack of knowledge and lack of money.

It was fun to play with 50 people.

Big idea: share experience

Second thing I took from this workshop is about telling stories: People who observed sessions should get together at the end of the day and in 15 minutes or less tell each other stories what they saw. You can actually put them on the paper and your report is done. :)

Big Idea: observers buy-in

Third thing: Rolling Issues Lists

When you observe sessions, you can put notes on a whiteboard. Everyone gets a pen and writes what he considers important. Then you can put these things on a paper and work with them later.

Big idea: making sense of the data

And how to work with that? You can put them into a sheet with these columns:

Observation - what happened

Inference - what is the gap between behavior and UI might be

Opinion - why you think it’s happening

Direction - what to do about it

And in the end some links to follow:

http://usabilitytestinghowto.blogspot.com www.wiley.com/go/usabilitytesting

All together?

Great day, great sessions, tons of inspiration.

UXLx Lisbon - day 1

Wed, 12 May 2010 21:50:26 +0200

I’m at a UX conference in Lisbon. Everything we talk about here is user experience and similar stuff, but I think its genuinely connected to semantics, because both care about meaning of things a lot. So I’ll be posting some notes from the conference here. Hope you enjoy them.

Today I came to the afternoon sessions. There were two open sessions I attended - What’s the story? and UX 4 kids. Both great and insightful, specially designing for kids. One thing I brought from it - if you design for kids, you have to think like kids and test a lot. But be careful, kids aren’t ideal subjects for user testing.

And then there was this workshop “Copywriting for web” with Eric Reiss. And it was brilliant. However I know a lot of the things Eric Reiss was talking about, he is just wonderful speaker and he really can interact with the audience. (I actually invited him to Prague WebExpo but he can’t attend this year, he already has another conference. So maybe next year?)

Anyway - just few bullet points from the workshop for you to think about:

The most important thing for writers is shared reference. That means, that everyone knows what you write/talk about and their imagination of that thing is pretty similar to yours.
Don’t take anything for granted
Most of the things you know about SEO is bullshit
Shorter text isn’t better
Longer text often sells more
People read on the screen. Just slower and in a different way. (Oh, but maybe iPad will change that)

That’s it for now, looking forward to tomorrow.

Google opinion on what is the future of semantic search....

Mon, 19 Apr 2010 13:09:12 +0200

Google opinion on what is the future of semantic search. They’re all about statistics, but interesting to see.

Google support for Microdata

Fri, 12 Mar 2010 14:28:00 +0100

It’s happening. On Tuesday Google announced it’s support Microdata.

Right now they support reviews, people profiles and events.

Hopefully this step will increase interest in Microdata and we’ll see some tools for extracting these informations from browser to actually help users, like Microformats does. Till then I’m sticking with them on clients sites.

But the freedom to choose Microformats, RDFa or Microdata and be sure, that Google actually understand them, it’s a great news.

Colorizing images on :hover with jQuery

Tue, 09 Mar 2010 11:33:09 +0100

On clevis.cz we have black&white images in portfolio. I wanted to colorize them on :hover.

I wanted to do it and had these goals:

Without styles and/or JavaScript there will be just a gray image.
I don’t want to create CSS sprite for each image, it’s time consuming and boring.
I want to use tag for specifying portfolio image in my code.
I still want to preload both images (black&white and colored versions), I want to avoid blinking.
I want to fade in and fade out colored version.

I knew I will have to use jQuery, because CSS can’t do this alone.

I begun with code of a portfolio image. Semantically it made sense to me to use new HTML5 elements

and

, see html5 doctor for further explanation.

Now I decided that this code is pretty nice and I don’t want to add any anything else just to enable desired effect.

I googled to find how others are solving this. After a while I found this great tutorial on The Art Of Hand Coding. It’s using CSS sprites but it gave me the idea that I can dynamically take url address from element and set it to another element as background.

But I actually needed to change that url a bit to find the right colorized image to the black&white variant.

At first it seemed impossible to me, because I’m not much jQuery expert. But after a quick google search I found this wonderful plugin created by Mark Perkins, which allowed me to change the URL.

After a while I’ve putted together this script:

It loads the right image (colorized version of portfolio images are prefixed with “color-” and generated automatically by a little Automator script) and the image is placed behind the element. The only thing left is now to fade in and to fade out the colored image, which is pretty easy in jQuery and I actually used the code from The Art Of Hand Coding. It works like this: you slowly let the disappeared and then the background of the link is visible.

And that’s it! All 5 goals completed, it works awesome in every browser I tested it in. (from IE6 to the latest Webkit night build). Check it out at clevis.cz/co-delame.

What do you think?

Solving line-breaking problem

Mon, 08 Mar 2010 22:17:00 +0100

While lunching new web site of company I work for - clevis.cz (which looks so awesome thanks to Josef Richter) - I run into a problem I had problem to solve semantically.

If you look at our site there’re headlines like this one:

I really love their style. However they introduce a problem. The text is specifically divided into two (or more) lines just to look better. No semantics in it at all. What to do with it?

On my personal site - honzasladek.com - I run to the same problem and tried to solve it with specifying precise width. I know, this attempt was doomed to fail. But it worked with some problems on Mac and Windows alike. But Opera sometimes just didn’t render a word on the next line, line-height got broken in several browsers and other horrible things happened.

This wasn’t the best way to go. Tired of it I used , which I’m ashamed of till now, but didn’t find the time to change it yet.

On Clevis.cz I used elements with display:block; for certain parts of text to cause the line-break. I’m not completely happy with it but it solves the problem and it doesn’t do anything when styles are off. (But the code isn’t as clean as it could be, you know ;))

Unfortunately I can’t think of any better solution. Can you?

"All our work, our whole life is a matter of semantics, because words are the tools with which we..."

Thu, 04 Feb 2010 22:33:25 +0100

“All our work, our whole life is a matter of semantics, because words are the tools with which we work, the material out of which laws are made, out of which the Constitution was written. Everything depends on our understanding of them.”

- Felix Frankfurter on why we should care about semantics.

RDFa Working Group lunched.

Wed, 03 Feb 2010 13:16:00 +0100

Yesterday (that is 2. 2. 2010) was officially lunched RDFa Working Group. It’s really an exciting news for everyone interested in semantics.

After W3C discontinued XHTML 2, many people thought, that RDFa is as good as dead. Obviously it’s not.

Among other things this group will support incorporating RDFa into HTML5 and, of course, will be updating and developing RDFa. I’m really excited about some ideas people are discussing in the group public email discussion. They could make RDFa much easier to understand and write for many people.

I’ll let you know if anything interesting happens.

Define: Without Answers

Sat, 30 Jan 2010 16:04:14 +0100

Let me summarize few things:

This site was created in July 2009 and since then I wrote about 5 real articles. Not good.
Internet is full of blogs about web design.
Nobody needs another blog about web design.
I’m not a web designer.

If there’s one thing I’m possessed about, it’s semantics. It’s the next frontier of the web. So I’ll be writing about it.

What can you expect to read? A series about RDFa, news about: RDFa in HTML5, Microdata and Microformats, my thoughts on semantic markup and much more.

I hope one day I’ll have here guest posts about semantics and interviews with people who really care about semantics. But it’s just a plan for the future.

If you’re interested in semantics I suggest you to subscribe to my RSS feed.

P.S.: My personal thoughts about other aspects of life I’m going to publish only in Czech on my blog (sure, it’s powered by Tumblr).

Jak se skutečně narodil Fakturoid

Thu, 24 Dec 2009 10:37:29 +0100

This post is in Czech only.

Příběh Fakturoidu z pohledu člověka, který jeho vývoj sledoval tak nějak z povzdálí

Po světě spolu chodí spousta lidí, ale tihle dva se vyloženě hledali. Nevím, jak se vlastně nakonec našli, ale mělo to určitě něco společného s velikostí českého webového rybníčku.

Ze začátku vše probíhalo naprosto standardně. Nejdřív zjistili, že je baví si spolu povídat. Pak se z toho vyklubalo nějaké to pozvání na kafe.. A nakonec se jednou při diskuzi o tajemných Signálech dohodli, že si spolu pořídí děťátko.

Tedy abych byl přesnější - robotí děťátko. Normální děti už dneska prostě nejsou v módě a robotí děťátko má řadu výhod. Nejí, nespí, neřve. Akorát ho udělat trvá trošku déle.

I za použití nejmodernějších metod pro rychlý růst robůtků, jako je jízda na kolejích či ozařování jasným světlem z nakousnutého jablka ve dvě ráno, to trvalo rok.

Prenatální vývoj našeho robůtka probíhal poměrně dobře, přesně dle příručky pro mladé rodiče - Getting Real. Zodpovědní rodiče se věnovali každému detailu a velmi rychle si uvědomili, že by bylo chytré malého robůtka něco naučit, aby nebyl jako všechny ostatní děti pasivem, ale stal se aktivem.

No a co je na světě jednoduššího než český daňový systém? A tak se robůtek ještě před narozením začal učit vydávat faktury či hackovat se do databází Ministerstva Financí. Do toho musel hodně posilovat, aby vypdal k světu. Bylo rozhodnuto, že zelená s šedivou jsou dneska cool a tak nosí oblečení v těchto barvách. Jediný, komu se to nelíbilo, byly hlavičky u tabulek. A tak tabulky už hlavičky nemají…

V půlce vývoje byla touha pochlubit se malým robůtkem tak silná, že nešlo odolat. A tak byla velká párty pro pár V.I.P. hostů a ti mohli začít robůtkovi povídat, co by vlastně chtěli vystavit. Jenže zákeřní hosté si začali vymýšlet spoustu bláznovin, začali chtít řešit DPH a cosi jako Proforma faktury. Z toho se malému robůtkovi, i jeho rodičům, udělalo trošku nevolno, ale statečně to vydýchali a hosty nevyhodili. Místo toho společně strávili dlouhé hodiny učením robůtka. Rozhodně to bylo zábavnější než Windows 7 welcome párty.

No a po vyleštění robůtkových zubů (kvůli úsměvu do kamer) a koupení vánočního dárku (bílý jednorožec na hraní), nastal čas představit robůtka světu.

Přeji robůtkovi pod stromeček (a k jeho 0. narozeninám) Fakturoidovi hodně spokojených uživatelů a jeho tvůrcům, Lukášovi s Honzou, hodně platících uživatelů. :)

Osobně jsem měl to štěstí, že jsem se mohl účastnit beta testovací párty a byla to fakt jízda. Robůtek toho už spoustu umí a co neumí, to se velmi rychle učí. Zkuste ho taky!

Stop being creative with class names

Sat, 12 Dec 2009 23:48:25 +0100

So I read today an article on Coding Horror by Jeff Atwood. It’s title says “Microformats: Boon or Bane?” and it really caught my attention. After reading it I just had to write this post.

The article says, among other things, one really true thing about Microformats. They’re really not perfect, they have their flaws. But I believe Jeff Atwood is wrong when it comes to what these flaws are.

His main problem with Microformats is that they’re using class attribute to make they’re magic. Read his arguments.

I believe that almost in every book about html & css will be a note on naming classes. It’ll say you something about naming them “semantic” and not to use something like “left-blue-column” because you could move the column to the right in the future and make it, I don’t know, orange. Unless the authors are completely stupid and nobody noticed that ‘till now, I suppose there is some true in they’re advices.

Then we have the all-mighty progressive enhancement technique. If I apply it to html + css coding, it basically says: “Write your html markup first - as semantic as you can, worry about the css later”. So if I would follow it to the letter, I would write my markup WITHOUT any class name and then use CSS3 selectors so heavily, that only nightly build of Webkit could display my site correctly. It would be nice, if all my costumers would be using nightly build of Webkit (which they, what a surprise, don’t).

So I need to add some classes.

So I think really hard to come out with the right set of semantic class names. But even I think I was really successful, someone else will always say - “hell, it’s stupid class name”. And we have one more thing to argue about in discussions.

Microformats, HTML5 and ARIA are about to change all that. I believe soon there won’t be any need to use my own class names. (Today I might use my own class names if I need to support some version of our bellowed IE.) We all will just use Microformats class names, ARIA attributes and new structural HTML 5 tags. That’s it.

I don’t know where this approach will take us (I can imagine some snippets libraries, OOCSS frameworks applied to it, some magic with JavaScript, etc.), but I can tell you - I’m looking forward for this future. What I found after 7 years in this beautiful industry, is one thing - we web designers are pretty creative and smart bunch of people. So if we take class names as given and focus our creativity to different areas, it’s likely to move the web design industry another step further.

And If you think the Microformats are piece of shit - that’s fine by me. Use RDFa instead. In the end it does the same thing from this point of view. You’ll just need a bit more advanced selectors. And when Microdata arrives? Still the same! (Except at RDFa and Microdata you won’t need to use classes at all. :))

Btw. if you’re thinking not using any of these, go right now and find yourself a new job. Because this is not a matter of choice since Google got on board.

Btw2. Andy Clark wrote a post about naming conventions about an year ago, so I didn’t invented this approach at all. I’m just it’s huge fun and I felt a need to share it with you today.

So don’t be afraid and start together this (r)evolution! Are you with me?

Commenting CSS files

Sat, 28 Nov 2009 16:32:00 +0100

I think commenting your CSS files is really important thing to do. Recently I discovered cssdoc.net, a project aimed to port JavaDoc comment style to CSS. I tried to use it on one of my projects and I want to share here my comments structure and I humbly ask you for an opinion. Is it good? Do you see some space for enhancements? How do you comment your css files? I’m looking forward for your opinions, I hope we’ll together find some best practices.

Some notes:

This is the beginning of my CSS file.

This is basic structure of my CSS files for easier orientation.

This comments one part of my CSS file.

When this projects goes live I’ll share a link with you to see it in practice. Follow me on Twitter.

"I did most of the important work in my career to date using crappy old equipment. Unless..."

Fri, 13 Nov 2009 22:15:57 +0100

“I did most of the important work in my career to date using crappy old equipment. Unless you’re editing high-def video or creating feature film animation, you don’t need great hardware to do good work. You just need a passion for the work.”

- Jeffrey Zeldman

Your CMS needs to evolve

Thu, 12 Nov 2009 22:00:12 +0100

There are literally thousands of content management systems out there. Many of them open sourced or free to use, some of them as hosted services, some of them as classic shareware. And still many of us have an urgent need to WRITE OUR OWN CMS to fit our needs.

In 21. century, when there’s an library for almost everything. When everyone is using some framework. When everyone tends to do different things then reinvent the wheel. Isn’t it kinda stupid? I think so. But…

CMS as we know them are systems of the past. They look and work the same way today as they did in 2000. They didn’t respond to the Web 2.0 (or we may call it a “social networks era”). They didn’t catch the change of the web design industry. There were times when one man could be an expert in every part of web design process. When web sites looked mostly the same (header, navigation column, content and footer). Today we need a whole team to create really great sites. And today’s web sites? They definitely don’t look the same.

Today we tend to play with every word on the web site. And a typical page has a number of important areas, not only one “content” area. For instance your product advertisement, quick info about your clients, embedded Twitter and so on. And not even after a day of searching on Google for some CMS even remotely capable of handling these things, I ended up with empty hands. So the only option remains - to write your own CMS (or something similar) to address your needs.

And there comes the Question (oh yeah, big one). If you worked hard on the text, if you paid a lot of attention to every pixel, how much power should you give your CMS user? Should he be able to edit texts on the site? Or only few defined areas? Should he be able to add images where he wants? And isn’t it better to just ask him to send you an email when he’ll want to make changes? Maybe his site would in the end work much better.

And when building CMS just for yourself, should even you have such a power? Isn’t it better to do the process of changing something on live site a bit difficult to make you think before doing changes? (We all know what happens when you send an email when tired, right?)
Is it worth the costs to build an CMS? And if to build one - what should it be capable to do? In my opinion we need something like CMS but I think that what we’ll use in the future will have completely different approach to content, will support social networks etc. Unfortunately I don’t know how it will work or look like. I believe they will be be paid services and they’ll be hosted by some companies, not the creator of the web site. But the rest remains hidden. What do you think?

PS: Note that I’m not talking about CMSs for blogging, it’s completely different situation and I think that current CMSs handles this pretty well.

"The CUE-2 teams reported 310 different usability problems. The most frequently reported problem was..."

Sat, 07 Nov 2009 19:17:00 +0100

“The CUE-2 teams reported 310 different usability problems. The most frequently reported problem was reported by seven of the nine teams. Only six problems were reported by more than half of the teams, while 232 problems (75 percent) were reported only once. Many of the problems that were classified as “serious” were only reported by a single team. Even the tasks used by most or all teams produced very different results—around 70 percent of the findings for each of these common tasks were unique.”

- Rolf Molich, in an interview with Christine Perfetti

Talk about Web Fonts I gave at WebExpo 2009

Sat, 17 Oct 2009 22:54:00 +0200

I uploaded my presentation at SlideShare. I’m not sure if it’s to much use without words, but maybe video will come out soon too. It’s in Czech, if someone’s interested in translation to English, please ask politely in comments. But no promises :)
I feel pretty good about the presentation and the response of the audience had blow me away. I’m happy you liked it, it was an honor to be a speaker at such a big conference.

View more documents from jansladek.

Links about @font-face

Thu, 15 Oct 2009 21:21:30 +0200

So I’m giving a talk about Web Fonts at WebExpo 2009 in Prague this Saturday (17.10. 2009). And because a presentation is a bad place for links I’m posting few of them here. Hope you enjoy them.

There’s so much going on in Web Fonts. Every day there are new discoveries & problems & solutions emerging. I’ll try to keep this list as up-to-date as possible, but no promises.

The bold one are must read for everyone interesting in @font-face.

Using @font-face

I Love Typography - Web Fonts - where are we?
Jeffrey Zeldman - Web Fonts Now
Hakon Wium Lie - CSS @ Ten: The Next Big Thing
Tim Brown - Web Font licencing - the basic idea
Jonathan Snook - Becoming a Font Embedding Master
Paul Irish - Bulletproof @font-face syntax

Performance Issues

Steve Souders - @font-face and Performance
Paul Irish - Fighting the @font-face FOUT
Stoyan Stefanov - Gzip your @font-face files
Zoltan Hawryluk - More @font-face fun

Free Fonts for Embedding

Font Serving Services

Typekit (private beta)
Typotheque (private beta)
Fontdeck (private beta)
Kernest

Does CSS Needs Variables, Selector Blocks Or Similar Stuff?

Sat, 29 Aug 2009 21:24:00 +0200

For a better part of my (short) life I was convinced it does. But lately I can’t help myself not to think that it would make more mess then good.

About a month ago Jeffrey Zeldman published an article “Why Standards Fail”. Among other things he shows there how CSS become so popular. It evolved from a really simple set of rules, which made your web pages look so much better, into an giant and complex standard which, without a doubt, is CSS 3.

To quote Jeffrey Zeldman:

“If CSS had initially offered the power, depth, and complexity that CSS 3 promises, we would still be designing with tables or Flash. Even assuming a browser had existed that could demonstrate the power of CSS 3, the complexity of the specification would have daunted everyone but Eric Meyer, had CSS 1 not come out of the gate first.”

So CSS was made simple, without variables or similar things, and it’s popularity shows it was probably a good decision. CSS 2 and 3 slowly adds more control over typography, layouts etc. And all of that I can choose to use right now because it’s nicely backward compatible - if older browser doesn’t now a property it simply ignores it. Therefore any visitor can read my site, only in modern browsers the site will look a little bit nicer. But who cares if he finds information he needs, right?

And now imagine that we would add variables and nesting to CSS. I would suddenly have a pretty hard choice - to use them and forget older browsers (Or detect them and serve them different stylesheet, which I’m against, so I’m not going to do it. And it’s 2 times that much work.) or not to use them and wait till the old browsers disappear. I would say that most of the people would choose not to use them. So now we would have in CSS something nobody uses and it pretty complicates the language. But shouldn’t we do it for the future?

I simply don’t think so. Why?

We can always use something like LESS. Something that will compile my own syntax which suits me to classic CSS file.
I’m not convinced that we need something like that. Sure selector blocks like those Eric Meyer proposed might be useful. As well as variables. But I’m much more into writing compiling programs than adding more complexity to already complex specification.
When we could add it now to the spec (which we can’t and it would take many years) and browsers would add support into their next version (let’s say it would take about a year) we would have to wait about six years for old browser to leave the market so we would be able to use our new cool selector blocks or variables. 7 years from now. Wow. Will anyone who wants to add those things to CSS now interested in them after so long?

And what do you think? Would you use variables or selector blocks or other similar things? Please comment!

And if you’re interested in using variables and selector blocks in CSS be sure not to miss my next article in which I’ll be talking about LESS and how it allows you to use variables and selector blocks. This was just a small theoretical introduction, hopefully it wasn’t too boring. :)

Apologies & WebExpo 2009

Wed, 26 Aug 2009 20:57:00 +0200

I’m sorry I didn’t write here anything for quite a long time. But I’m going to change it. Starting today I’m going to publish at least 2 articles per week. If I won’t, well… I’ll do 100 pushups. Sounds fair, right?

In a meantime I would like to invite you to WebExpo 2009, the largest Czech web conference which takes place in Prague from 16/10 to 18/10 2009. There are still avalaible tickets and the program looks wonderful. Among many talks you can find even my talk about Web Fonts & CSS3 (Saturday 17/10, 13:00-13:45, Webdesign & UX Room (E I)) and my best friend’s (Tomáš Jukin’s) workshop about UML and Unified Process (Saturday, 9:00 - 12:30). We’ll definitely look forward to meet you there!

From the topic of my talk you can guess what I’m going to write about till the conference. I have a plan in mind that I’ll be preparing my talk here on the blog and than I’ll ask you, my dear 3 readers, for you opinions and ideas. I’m really looking forward for this kind of cooperation, I hope you’ll be willing to help. I’ll be most grateful!

Take care!

Object Oriented CSS - should you care?

Wed, 22 Jul 2009 00:42:00 +0200

Few last weeks I’m keep thinking about the concept of OOCSS (Object Oriented CSS, first presented by it’s author Nicole Sullivan at Web Directions North in Denver). It is aimed to make it easy to maintain huge projects with thousands of sites and to make it easy for even beginners to participate in the project.

It works like this: If something on the site looks and behaves somehow it will look and behave the same way anywhere on that site. If you want to change the way it looks you have to add a class to that. The name however comes from related concept of “extending” elements look with classes - in OOCSS is pretty common to add multiple classes to one element. That’s all. Pretty simple, wouldn’t you say?

First time I heard this idea was after a huge project which I have written with the classic coding style - containter element has some class and a look of the content inside depends on the class of this container. This allows you to use CSS selectors at max and produce really nice looking and clean code which is pretty maintainable - well, for coders.

Then the problem comes in - programmers. They are really nice guys but they mostly know only basics about CSS and HTML. So if they want to move something on the page they usually just use cmd+c and cmd+v. And than it’s not working, they want to fix it, you do it and than it all happens again and again and again.

OOCSS promises to set you free of this. But as always there’s a darkside..

You have to change the way you write and think about CSS and HTML. Your code is suddenly flooded with classes, some of them with not really semantic names (what is semantic on .size1of2?). I’m semantic kind of guy, I really love Microformats and RDFa, I think about the meaning of every HTML element, I WANT my classes to be semantic.

Despite that I decided to give OOCSS a try. I want to try if its really going to make a difference for programmers and I wonder how will it work with Microformats - will I need much more classes even after applying them? And what about the diference of the file size - will it be noticebly bigger? Or smaller? And how will it work with LESS CSS?

There’s too many questiong waiting for answers. And I’m really looking forward to explore these things and to share my thoughts. I hope you’re looking forward too.