Page 2

Error page tracking in Google Analytics

Are you aware of how many 404 “not found” errors your website is really serving? Are you aware of which URLs are causing this error? Or perhaps it’s a pain to comb through your log analysis software to find the answer?

If you’d like to track this info in Google Analytics, read on to find out how to add the tracking with a couple small snippets of JavaScript.

Read the rest of this entry ›


CFWheels, meet Docker

I was stoked when I saw that Adam Chapman had created a Docker setup for CFWheels and Lucee.

Docker is a fairly easy way to get a development environment setup for experimentation, which then can be shipped into production later. It’s also a great way to try out Lucee and CFWheels.

You’re probably like I was also: curious about Docker and what it could do for you. If you’re familiar with CFWheels, this is a great way to jump in and see if it’s right for you

Read the rest of this entry ›


Effective “Press” and “Media” pages

Your site can probably do more to serve journalists, bloggers, reporters, and promoters. An often-overlooked page for smaller- and medium-sized websites is a Press or Media page. Why not make it easier for people to write about your products, people, company, or services?

I’ve written a new Playbook article about Press & Media pages. Read on for more information about the topics that I cover.

Read the rest of this entry ›


Modular CSS

One of the best parts of SMACSS is the concept of modules.

Read the rest of this entry ›


A simple rule of thumb for evaluating your web content

Kristina Halvorson’s Content Strategy for the Web contains a simple, yet effective tip for evaluating your content:

Generally speaking, content is more or less worthless unless it does one or both of the following:

  • Supports a key business objective
  • Fulfills your users’ needs

This blew my mind to pieces, so I decided to draw up a handy chart. Read on to see the chart.

Read the rest of this entry ›


Simplified Body Glide package design

I love seeing a piece of design go from “amateur Photoshopper” to simple and clean. See this quick post on how Body Glide delighted my inner design nerd recently with their package redesign.

Read the rest of this entry ›


Sass and CSS style guide

Over the past few months, I have been working on my own Sass and CSS style guide. Here is where I how I do things at this time:

Sass & CSS style guide

Like everything in the Playbook, I plan on refining and sharing improvements as I learn and improve my craft.

Read on for a summary of what I include in my style guide

Read the rest of this entry ›


Simplistic vs. simple in product design

We’ve all heard of it before: “I want something simple.” People get tired of products that present them with so many choices that they don’t know where to go next.

When you’re building a product, this sentiment can sometimes lead you down the deceptive path of simplistic.

There is an important difference between the terms though.

Read the rest of this entry ›


Draftsman gem: Add a draft state to your Ruby on Rails and Sinatra relational models

Draftsman is a Ruby gem that lets you create draft versions of your database records. If you’re developing a system in need of simple drafts or a publishing approval queue, then Draftsman just might be what you need.

Read on to learn more about using this gem in your Rails, Sinatra, or plain Ruby application.

Read the rest of this entry ›


Effective “About us” page tips, best practices, and guidelines

I scoured the Web for examples and best practices for About Us pages on websites. I compiled an article with tips, best practices, and guidelines for creating an effective About Us page in the Playbook.

Topics covered in the article:

  • Typical audiences for About Us pages
  • Recommended information to include
  • Examples of effective About Us pages

Read the rest of this entry ›