Reviews: Noded and Support Details

This week we have two reviews for the price of one. First we review the freelancing book ‘Noded’ and then take a look at a useful web application called ‘Support Details’.

Noded – The Untouchable

Hello, my name is James Callaghan. I’m an in-house web designer and developer / generalist working for Marshall Aerospace at the Airport in Cambridge and also work freelance.

Before I start, do you know what a Noded Team is?

The entire book, all eighty six pages of the book, attempt to explain what Noded is. During the first few chapters it attempts to cover definitions and examples, which I found a little hard to take in. It took me a few attempts to learn what Noded is, reading a few pages again and again.

With what Noded was vaguely drilled into my head, continuing on, the book focuses on freelancing with tips and advice on many maters such as setting up a business, planning things to managing time. This was of huge interest to me and the book became slightly easier to read.

Though out the book Andreas and Jaan describe their methods and tips on various subjects relating to Noded Working and Freelancing.

Noded Website

One section I did enjoy to read was “A space to work” that explains how important it is to find the right place to work. “As a web worker you can work from any place you fancy – a library, coffee shop, or park bench”.

Most of the time however, it’s nice to have a more personal place to work from.” I’m under the same opinion as Andreas and Jaan – “crappy office, crappy output”, “inspiring office, nice quality output”.

A subject that makes me very sore with my recent data loss that I can say I already adhere to is the tools for the game and why you should use the cloud over your hard drive. With explanations how applications force you to use their logic and structure and therefore are really tiresome and in the end the application is abandoned; instead suggests using cloud based web-apps that are far more flexible and forgiving, examples include: Email, Calendars, Get Things Done (GTD), Project Management, Synced Files, RSS Feeds.

On a more back office subject the book explains why working an 8 hour day is dead to tips on how to break away from the traditional meeting.

I take the same approach as the book, my ideas and creativity cannot materialise on command. They come at the most in-convenient times when I’m not working such as in the show, out on a ride on my bike or whilst out walking my dog. The book suggests using a tool and allowing people to contribute in advance of the meeting, following up with a simple 15 minute meeting to make a decision on the project or simply brief everyone involved.

An idea I am looking forward trialling in the real life! “The 8 hour workday is dead. We don’t believe that being

“being at work” for 8 hours accomplishes more than working for 4 hours, 2 days or 5 minutes. Work is about accomplishments, not measuring time. It is about being effective versus being efficient – doing your job faster and better versus simply doing more work”.

Not sure how to approach my manager on this one though, it is all about the hours here but way to think of it is:

“when you buy a music track that you really like, does it matter whether the artist spent two hours or two months writing the song? Probably not. Does a bowl of pasta taste better if the chef spent more time on it than if he spent the right amount of time on it? Probably not.”

In short, the book has really given me some great tips and methods as to how I should approach my freelance work but also provided me with some great ideas how to handle projects and work within the organisation I work in.

As I read through the book I found myself wanting to know more about something that had be written so instead of getting distracted whilst reading the book, I created a “list” of the pages with references and URLs I wanted to know more about.

The question I asked before reviewing the book was:

“do you know what a Noded Team is?”

If you answered at all, I suggest grabbing a copy of this book and truly discovering what Noded is all about. If you didn’t here is a dictionary definition included in the book.

“Noded Network, a Node Team. A group of individuals, often but not necessarily geographically far apart, that come together to form temporary or recurring project teams. Unlike ‘distributed teams’ Noded teams work for a wide range of clients and any member of a Noded team can take the lead to bring in work, manage work and choose their team members.”

Lastly I would like to say that I have really enjoyed reviewing this book and would like to take a moment to thank Paul and the team for producing such a great podcast but also to Ryan for his time and patience with me as it has taken me quite some time to produce this review. I’ve had to teach my brain how to read again, but also how to write a review that makes sense.

Support Details

My name is Nora Brown; I wanted to let you and Boagworld listeners know about a really handy site I’ve come across. I’m a freelance web designer who does a lot of sites for writers, artists, and small business owners – not necessarily the most tech-savvy folks. Sometimes they don’t even know that they’re using a browser, much less what specific version of IE they might be using.

So to help diagnose problems, I direct them to www.supportdetails.com. From this website, they can simply email you, and it sends you all the details of their browsing environment. You can even give them a link with your email address pre-filled in. An added bonus is that it includes their IP address, so you can create a filter in Google Analytics to exclude their own site visits from their stats.

Support Details website

Again, that’s supportdetails.com. I hope you find it useful.

197. Energise your ecommerce

This week on Boagworld: We examine ways to improve the conversion rate on your ecommerce site, review CSS Mastery 2nd Edition and take a look at Zen Coding.

Play

Download this show.

Launch our podcast player

News

Lessons in simplicity and constraints

I am a great fan of simplicity and constraints. I have written enough about simplicity before so I won’t bore you again. However, unlike most people I enjoy the constraints of a brief and limited timescales.

I was therefore delighted to read a short little post on the 37Signals blog which summed up these two concepts so brilliantly. They wrote:

The easiest way to force the insight of what can be lived without is by playing a game of constraints: You have to ship on Friday, you can’t add more people, you can’t work nights. Fixed resources, fixed time. All that’s left to give is scope. It’s amazing how creative the cuts and sharp the sacrifices become when you’re backed into a corner. It’s when you have to choose that you make the best choices.

In other words constraints force simplicity. This is a mantra I can get behind.

They also end with an important point for website owners:

For every 1 day estimates of a task, there’s a simpler version of that you can do in 3 hours, and an even simpler still you can do in 30 minutes.

So next time you hire a designer and they ask your budget, tell them. This is a key constraint that will influence how the designer builds your site or application.

Making better use of your footer

Fat is fantastic – at least where footers are concerned. For a while now there has been a move towards ‘fat footers’. These contain so much more than the privacy policy and copyright statements of days gone by. Todays footers are full of information. The question is, what exactly should we put into our footers?

Designshack has an excellent post that gives you 10 ways to use your fantastically fat footer.

Some of the ideas are suggestions for content (such as using it for social media links or ‘about me’ content), while others are design ideas (such as using illustration or animation).

Personally I use footers for two purposes:

Secondary Content - Additional information that is not apart of the main content on the site. For example in the case of Boagworld this includes a blogroll, great content on other sites and stuff I am up to. This isn’t really apart of the boagworld blog. Its extra content readers might be interested in.

Calls to Action – I think footers are a great place to put calls to action. For example on the Headscape website, we have the contact form at the bottom of the page. Hopefully once people have read our compelling content they will be inspired to complete the form. 37Signals used to use a similar approach on their own website.

How to guarantee an improvement in your conversion

Later in this show we talked about ideas that might improve the conversion rate on your website. However, if you want a certain why of improving your conversion rate (or your site in general) then read: An Introduction To Website Split Testing.

Split testing (otherwise known as A/B testing) is the process of showing different users different versions of your site. You then monitor how these different versions affect user behaviour in order to find the best solution.

It is a guaranteed way of finding the best solution through a process of trial and error.

However despite its success, few website owners use the technique. I think it is generally perceived as time consuming and expensive.

Although it does take time to produce multiple versions of an idea and test it, actually running the test is fairly inexpensive. In fact Google provides a split test tool that is absolutely free. Also, there is no reason not to split testing an approach before you roll it out. After all it has already been built anyway.

To learn more about the benefits of split testing and how to get started, definitely read this post. It will inspire you and set you on the right path.

How to make sure you’re regular… at blogging

When I write about communicating with your audience in the Website Owners Manual I say:

The key is regularity, rather than frequency. Users should come to expect your communications. Communicating on an ad-hoc basis can be damaging, especially with blog posts.

This is a tone echoed in a post on ProBlogger this week. Tips on How to Keep Your Blogging Regular, emphasises the importance of regular posting before giving 5 ways to ensure you keep the habit up.

These include:

  • Don’t bite off more than you can chew
  • Regularity is more important than high frequency
  • Under promise and over deliver
  • Build a schedule
  • Have someone or something manage you

After six years of blogging, I can say I agree with each and every one of these points. This is great advice if you are blogging on a personal site. However, it is crucial if you are running a corporate blog. Read and take note.

Back to top

 

Feature: Increase your ecommerce sales

This week’s feature comes from a blog post I wrote some time before Christmas. It looks at 8 ways you can increase your ecommerce sales using as an example a site we have worked on called Wiltshire Farm Foods.

Read the original post: 8 ways we increased ecommerce sales by 10,000%

Back to top

 

Reviews

CSS Mastery 2nd Edition by Andy Budd

Read the CSS Mastery 2nd Edition review

Zen Coding

Read the Zen Coding review

Back to top

 

Review: CSS Mastery 2nd Edition

Hi, my name is Yaili and I’ll be reviewing the Second Edition of CSS Mastery, by Andy Budd.

First. Who is the book for?

The book states that it’s for “anybody with a basic knowledge of HTML and CSS” and experts. I’d say it’s more for the first case, but I’ll expand on that later.

There are lots of useful tips and tricks, that I’m sure you’ll use over and over, explained in a solid and easy to understand way. The fact that the examples can be seen online and that there are files that can be downloaded is great.

CSS Mastery 2nd Edition Book Cover

Second. It’s a second edition.

When I read the first edition, I was just starting to work with CSS, and CSS was still a bit of a mystery to me. I remember reading some things that I thought to be pure magic and that seemed very complicated, but now I realise they are used by any good CSS coder. So, at the time, the book opened my eyes to those techniques and to the possibilities of what could be done with CSS.

Content.

The book covers subjects from the beginning to a more advanced level.

It starts with the importance of semantic HTML, how to set good foundations. It takes a very brief look into microformats and HTML5 as well.

Then it moves onto selectors, with some more advanced and CSS3 ones — but it doesn’t go very deep into that area to be honest.

It explains the box model, which is rather important, very well. Liquid and elastic layouts.

Some more advanced techniques, like sliding doors and even multiple backgrounds, which is quite refreshing. Opacity and rgba colours.

There are some clever uses for the :target pseudo-class and attribute selectors. Some webkit proprietary code like gradients and reflections.

It also explains how to style lists and navigation. I would have liked to see a larger section for definition lists, because there’s only a small section and it sounds a bit negative (or even dismissive) and I don’t think it makes them justice.

There are some negative comments on CSS frameworks. Which I frankly agree with.

A good introduction to the IE layout issue. Some common browser bugs and how to fix them. And how to work with graded browser support.

Then on the examples, at certain points they can be a little repetitive, but there’s an interesting discussion about website widths, a brief example of using jQuery, which is rather nice.

Conclusion.

In conclusion, as someone who had already read the book, reading it again was good, as there are always things that you forget or that you weren’t aware of, even though my experience now is completely different, and I can be a little more critical about it.

If I could change something in the book, I think I’d change the naming of CSS3 — in the specs it’s always mentioned with no spaces, and in the book it has a space between the second “S” and the number “3″. I know it sounds nitpicky, but it’s rather annoying for me, for some reason…

Also, there are some mentions to browsers that are already dated, even though the book is fairly recent (like “Safari 4 beta”, which is already out of Beta). But that’s just something that happens in our industry — things move too quickly. I’m just being nitpicky again.

So, have I learned anything from this second edition? I did learn a few things, but not much. I already use or know most of the techniques. But would someone starting to work with CSS learn anything from the book? Definitely yes. I used to always recommend the first edition whenever someone asked me for book recommendations, and I will keep recommending it with the second edition. It’s a must-have.

193. Get more from Google Analytics

On this week’s show: Paul and Marcus are joined by Matt Curry who shares some advanced Google Analytics techniques. We have a review of Fancy Form Design by Jina Bolton and Paul goes on endlessly about the Website Owners Manual.

Play

Download this show.

Launch our podcast player

Housekeeping

How can I not mention the launch of my book the Website Owners Manual? You are going to be sick of hearing about this, but console yourself with the fact that I have a very short attention span and will soon get bored of it. Please take a few minutes to learn more about this book at boagworld.com/websiteownersmanual. I would especially encourage those of you who are web designers to check it out. This book contains all the information your clients ‘need to know’. It was written specifically to be given away to clients, so helping your projects run smoother. I even managed to pursued my publisher to give significant discounts to those buying more than 5 copies. However, as an extra bonus for boagworld listeners you can also get an additional 40% off of any website owners manual purchase (including the multi-buy packs) if you use the code ‘boagworld’ at checkout.

Back to top

News

Design interactive prototypes – Fast!

With websites and web applications becoming increasingly complex it is often hard to visualise them before build. Photoshops comps fail miserably and static wireframes are little better. The only way of truly communicating how a site is going to work is to build an interactive prototype. Unfortunately building prototypes can be time consuming and expensive. Although clients need to understand how their site will work, they are rarely willing to pay for a prototype. One solution is IxEdit, an ‘interaction design tool.’ This tool has to be seen to be believed, but essentially allows designers to build jQuery driven prototypes without writing a single line of code.

With IxEdit you can build everything from the automatic insertion of HTML to accordion effects. In fact you seem to be able to build most of the elements and effects supported by jQuery. Of course the quality of code is not going to be as good as something written by hand. That is why the product is billed as ideal for prototyping. However, for better or worse, I am sure a lot of web designers will use this tool for live sites too.

Making passwords more usable?

On the subject of Javascript and interaction, there is some interesting work being done with password masking. In show 173 I talked about some of the problems surrounding password masking. Essentially, although hiding passwords increases security it also creates a usability challenge. Jakob Nielsen wrote:

Usability suffers when users type in passwords and the only feedback they get is a row of bullets. [It] costs you business due to login failures. Password masking has become common for no reasons other than (a) it’s easy to do, and (b) it was the default in the Web’s early days.

There have been a few solutions doing the rounds. The simplest of which is to add a checkbox allowing users to keep their password entry hidden. However another popular approach is the one adopted by the iPhone. Instead of revealing the entire password it shows only the last letter entered. These two approaches have now been combined and made simple to implement using a sprinkling of jQuery. Delayed Password Masking couldn’t be easier to setup and helps go someway to improving usability.

How to be more transparent

In my post “The 10 Harsh Truths About Corporate Blogging” I wrote:

People don’t like interacting with organisations, corporations or machines. People like conversing with people. People don’t like, trust or want to work with corporations. We associated those feelings with individuals, not companies.

In other words, if you want to make a connection with your users you need to be open, transparent and show the people within your organisation. However, knowing this and doing it, are two different things. That is where a recent UX Booth post comes in. The title of the post is “Transparency: Benefits and Best Practice.” Personally, I think this is a misleading title. It doesn’t really explain in any depth why transparency is important and fails to provide much in the way of ‘best practice’ (I can see I will have to write something on this subject). What the post does do well is give you some cracking examples of sites that communicate the personalities and people behind their organisations. It certainly has inspired me to look again at the Headscape website, and I hope it will inspire you to become more open as an organisation.

In other news – Google and Microsoft talk about stuff

Normally I like to keep the content of this section of the show focused on the here and now. I see little point in reporting what might affect you ‘one day’ in the future. That said, there are two stories that have come out this week, which I simply couldn’t ignore despite the fact neither will have an impact on you today.

Google to add site speed to search algorithm

This week when talking about the importance of website speed Matt Cutts from Google said:

Historically, we haven’t had to use it in our search rankings, but a lot of people within Google think that the Web should be fast. It should be a good experience, and so it’s sort of fair to say that if you’re a fast site, maybe you should get a little bit of a bonus. If you really have an awfully slow site, then maybe users don’t want that as much.

If Google follow through on this thinking the consequences could be massive. In particular this could further undermine the already shaky rankings of flash heavy websites. It could also provide a real advantage to those with the financial resources to throw more server and bandwidth capabilities at slow websites. That said, on the upside it would refocus website owners on the importance of performance and help to speed up the web for everybody. It will also encourage better coding practices maybe push legacy tables based websites down the rankings. Of course all of this could be redundant. We have no way of knowing whether Google will implement this change, and even if they do, how great a priority they will place on speed.

Microsoft talks about IE9

The other news that might shape the future of the web comes from Microsoft. With Windows 7 complete it would seem they are turning their attention to Internet Explorer 9. Apparently the new browser is only in very early stages of development. However, Microsoft are making it clear what their priorities for the browser are. These include:

  • A desire to provide better HTML5 support
  • Significant speed increases for Javascript
  • Improved CSS support
  • Better use of hardware acceleration

All music to my ears. However, I was sad to read that according to Mashable they have only been working on the new browser for 3 weeks!

Back to top

Interview: Matt Curry on Getting more from Google Analytics

Transcription to follow shortly.
In the meantime follow Matt on Twitter.

Listeners book review: Fancy Form Design by Jina Bolton

What is it?

This book, in Jina’s own words, is aimed at anyone who’s involved with any part of the creation of an online form. Split into 5 sections, it covers the Planning, Designing, Structure, Styling and Enhancing of forms used on the internet Written in a format that is more about advising and guiding rather than teaching, this book will appeal to people who are used to the Sitepoint way of writing, and want to really understand the thinking behind creating a successful web form. It’s not one of those “learn in 24 hour” type books, but is more written as if you’re at a workshop run by Jina. This is not a hardcore reference manual that covers absolutely every permeation of a web form, but will have you more confident and eager to apply what you learn to forms you build from now on.

No bloat

With this book, Jina has tackled a subject that frustrates many a web designer. Forms are often too time consuming, too technical, or too stubborn to spend time getting right. Resources on the internet fall usually into 2 categories, not enough info, or too bloated and confusing. What Jina has managed to do is get straight to the point, without the bloat.

A form is just a form. Isn’t it?

Straight from the 1st chapter Jina had me thinking differently about forms. Before reading this book, I would not have said things like sliders, colour pickers, or drag and drop items are elements of form design, but when you look at where they are used, it’s obvious they are. I’m already more excited about forms than I was before. And I think that’s what this book does really well. It takes the process of form creation, and says “yeah, I know, a form is a form. But look, you can do this with it…”. Jina shows you how a form is very much like a website design. You need to think about typography used, colours & imagery, how the form is going to be structured and how it will affect how it used.

Good practices make perfect

Throughout the book, Jina runs through some processes for creating perfect forms. It starts with how to research and find inspiration. Many people who have built forms in the past would probably not have used the processes talked about in the book. It’s an eye-opener to best practice, and to how investing time in tried and tested techniques at the beginning will save you time further down the line. Many of the practices Jina talks about are transferable techniques, that can be adapted and implemented on web design, brochure design, database design etc. What I really liked is the way the book doesn’t force you to follow the practices, but is more like a friend giving you some tips.

Get your hands dirty

Although I mentioned this book isn’t a “teach yourself in 24 hours” jobby, it is by no means a pure reference book. You can follow along with Jina, and get your hands dirty with some HTML markup and CSS. JavaScript is kept to a minimum by using jQuery, and again has example code you can work along to.

In a nutshell

Fancy Form Design is probably the best title for this book. It explains how to design forms that look fancy. Jina does not pretend this book will make you a master of AJAX form submission techniques, nor an expert in JavaScript server-side form validation. It breaks down the components of creating a form, the content of that form, how to jazz it up with some clever styling tricks and jQuery magic, and makes you think about forms more as an important part of your design rather than a stone in your shoe. To me, this book does exactly what it says on the tin. Buy Fancy Form Design from Amazon

Back to top