One of the things we really wanted to do at Wallwisher was to build our own blog theme using the UI principles we swear by. Some of the things we wanted in our blog theme were:

• A floating layout. A fixed width layout does not reward people with large screens. A blog is primarily text and therefore a floating layout can be easily accomplished.
• 2 column with a collapsable sidebar. More than 2 columns compete with the user’s attention. The sidebar should be collapsable to allow the user to focus on a lengthy article. It also allows users of smaller screens to read effectively.
• Limited use of images for better performance. The world is perfect when you browse the Internet from your broadband connections in the US. But things can get really ugly and frustrating even the seemingly most uber urban places like Singapore. You want to tear your hair off sometimes when you have to wait 5 seconds for the blog to show up, just because it takes time to download those rounded rectangles/gradients.
• Effectively separate primary and secondary information. Primary information being the post text, and the secondary information being the categories, tags, permalinks, etc etc. A lot of blogs we see have, what we call, a dumpster footer – full of meta data about the post that is not used by 90% (a ballpark figure) of the readers.
• Use of colors to differentiate page elements. The web is such a visual medium, it hurts to see elements on a page separated like on a traditional journal – underlines, a difference in font sizes, etc etc. The easiest and the most effective way to achieve the differential is to use colors to separate the elements.

Look, for example, at the google blog design below. I understand they want to be simple n all, but com’on! Everything here is white and grey. The blog uses only 50% of my 1440px screen. For us here at Wallwisher, at least, it is not an easy read.

But well, the earth refuses to rotate slower than we want it to sometimes and the days are still 24 hours! So unfortunately, we did not have the bandwidth to make our own wordpress theme.

However, sifting through the wordpress themes on the Internet, our eyes stopped on this wonderful theme called Ahimsa, which, if we’re not wrong, means Peace. The theme, in our opinion, is almost perfect. Just look at it:

• Floating layout
• 2 COLUMN COLLAPSABLE SIDEBAR
• It hardly uses any images. The rounded rectangles you see (or you don’t see) are purely CSS, which means IE users would not see rounded edges, but FF users will. This, we believe is the best way to go about such issues. We’ll make a post on this soon.
• Look how things like categories and tags are hidden until you click on the word. Brilliant, just brilliant. We checked the size of JS required to support it – just 2kb, or 300ms on a 56kbps connection.
• Look how well things are separated by color. Ok, we agree there is a bit too much color (we’ll work on it when we have a bit of time) but the idea is right.

This theme is just fantastic. We hope that more people would follow these rules when they design their own themes. weagree sometimes you need the gloss, but for simple text journaling, Ahimsa is one of the best themes we’ve ever come across. Kudos to Ravi Sarma for creating such a wonderful theme!

There is a lot of buzz about WYSWYG editors of all kinds. At Wallwisher, we have spent considerable time and energy in implementing a true WYSWYG feel, whereby there are no forms which require you to refresh the page.

With Wallwisher, a user can interact with the web elements to an increased extent than other web applications. With this increased interactivity, it is important for the elements to behave in a predictable manner, and the end result of each interaction to be what exactly what the user wants it to be. This is true WYSWYG, and Wallwisher hopes to continue down this path in the coming months!

While interacting with a website, how many times do you experience the mind-numbing request of pressing "OK" or "Cancel"?

We, at Wallwisher, hate the concept of this idea, of asking for user confirmation, when it’s simply not required. What is required is a notification, and there are other simpler ways of delivering them.

We like to use simple popup messages which fade away on their own, without the user having to click on "OK" or "Cancel". Let’s say in a chat room, the common rule is not to post more than 2 messages in a minute, to prevent spam, and allow fair distribution of contribution. If a user tries to post more than 2 messages, instead of popping up a dialog box informing the user of the rule, and asking him or her to press "OK", we would advise the use of simple fade away popup notifications.

See a sample implementation on Wallwisher Demo (post >3 stickies in under a minute).

As ardent users of the web, have you ever felt the frustration at static menus, giving you an option to "Sign up" even when you are on the sign up page ?!

Well, we at Wallwisher are true believers of cutting the nonsense out, and keeping the design very sensitive to the context of the page. We promote the use of

Context Based Menus…

A simple way of arranging Menu Items based on the page you are on. This is simply achieved by conditionally calling and displaying menu items depending on some key variables such as the state of the user (logged-in or not), state of the page (shareable or not), etc. Obviously, this entails a clear categorization of all links in the menu. You can see a sample implementation at Wallwisher Beta.