Tag: kranthi

The Art Of Launching An App: A Case Study


  

You’ve made your first app!

Now what?

Anyone in the app business knows that marketing an app is tough. And according to a recent article on TechCrunch, “Getting a mobile app noticed in the increasingly crowded mobile app market is more difficult than ever.� Some titles and concepts are truly unique. Angry Birds? Its title and screenshot alone were enough to catapult it to number one in Finland, according to Mikael Hed, CEO of Finnish game studio Rovio, which develops the game. Some apps are downright genius. Who doesn’t loath maintaining a to-do list? But now with Clear, it’s astonishingly fun! Who in the media wouldn’t cover something this clever? These two special cases were a shoe-in for the coveted feature page.

OK, so we have two apps that have leaped the giant “featureâ€� hurdle and scored attention, much to the envy of countless wannabe developers. But not every app is an Angry Birds or Clear. And any developer surely knows that they are in extraordinary company — 91,754 iOS apps and 122,220 Android apps were released between 16 May and 8 September 2011, according to a recent Mobilewalla report. The researchers also found that during 2011, the number of available iOS apps increased from 338,000 to 589,148, while Android apps also more than doubled, from 115,000 to 319,774.

So many apps
(Image credit: florianplag

The app world is becoming like one giant forest, millions and millions of trees. So, if one of those trees falls and no one is around to hear it, does it make a sound? Sure, there are SEO tricks, word-of-mouth marketing tools and built-in demographic identifiers that might help move your product up the ever-growing search list of apps, whether the list is for books, games or lifestyle tools. Moreover, thousands of companies in the market today make extravagant claims of being able to get your app noticed.

Many developers fall into the trap of allocating tight budget dollars to quick “tech� fixes in a desperate attempt to lift their app above the crowd. However, in this age of digital distraction, one mechanism to help that tree stand out is a tried-and-true PR marketing campaign. And the best initiatives are those that involve choosing strategic partners, creating clever story angles that dovetail with newsworthy occasions, and running a cause marketing campaign and contest. This case study will cover some of these tactics and offer some of the lessons we learned along the way.

Case Study: David and Goliath

According to a recent article in Publishing Perspectives, “The children’s market is a huge opportunity within the digital publishing arena.� Jumping Pages, a children’s app developer, decided to enter this market with an expertly produced book app for children, the first interactive app version of the epic tale of David and Goliath. Based on the work of the team of artists, animators and programmers, the iPad app is filled with vivid graphics and 3-D and 2.5-D animation that runs with interactive components at the same time on the same panel. The reader is able to interact with hundreds of original assets: shoot arrows, catapult burning weapons, populate flowers. Shake the iPad to awaken the sleeping Goliath; sway the iPad to swing a hanging lantern; turn the iPad to change the character’s points of view.

David and Goliath App

The quality of the work was undeniable, so it was imperative to the developer that the app get attention. But how would the app be differentiated to the consumer, considering that a David and Goliath book app for kids already exists. Strike one. Moreover, regardless of its quality, the likelihood of the app landing on a feature page was slim, considering that most retailers are reluctant to highlight stories with religious overtones. Strike two. A final dilemma was how to make a story that has been around forever feel relevant in the crowded world of kids book apps. Strike three?

Not so fast!

Don’t Drink the Kool-Aid

From a production standpoint, the David and Goliath for iPad app was ready to launch in July 2011. The only thing that wasn’t ready was a plan of action on how to make some noise for a story that, for all intents and purposes, already exists as an app. This scenario holds true for many developers who are ready to submit improved versions of models that exist in various categories; there is a plethora of apps for weather, productivity and games (Who’d like to wager on the best poker app?). Many developers spend countless hours designing, programming and shaping their apps. They become so immersed in the product that they often drink the Kool-Aid, so to speak, and believe that their superior work will speak for itself and that word of mouth about their amazing app will spread quickly. Many developers with this mentality simply see no need to create a cool marketing plan around the app. Sounds like buying a lottery ticket.

Launch!
(Image credit: stevendepolo)

Being proud of and confident in your product is nice, but better to be realistic about how to introduce it into the marketplace. Thus, after careful thought and shuffling around scarce budget dollars, Jumping Pages re-examined the landscape and decided to be smart about launching. The company set out to create a targeted and focused consumer marketing strategy. It decided it needed to implement an effective campaign in order to rise above the other book apps that were entering the fray in increasing numbers and to set itself apart from a version of the story that was already available. And because of budgetary constraints, it had no time for a protracted strategy. It’s first swing had to be a hit.

Finding the Perfect Partner

First, the company wanted an effective “marketing� partner, a narrator for the story who would help sell it. Ideally, the narrator would have a back story that was relevant both to the biblical tale and to the targeted demographic, and who would have broad media appeal (in order to be newsworthy). Jumping Pages reached out to baseball star and 2006 World Series MVP David Eckstein to narrate the app. As many sports fans know, Eckstein has had a noteworthy career, overcoming his relatively short stature to achieve glory at the Major League level. Hence, the back story: a modern-day David whose life story mirrors that of the biblical David.

Upon arranging for his participation and partnership, the company moved the launch date of the app to October to coincide with the start of the World Series. Coincidentally, October 2011 marked the five-year anniversary of Eckstein’s World Series MVP performance; so, Jumping Pages created an “MVP Edition� of the book (same app, different narrator), which would be released to dovetail with the newsworthiness of the fall classic.

Newsworthiness Needed

Being newsworthy is key, particularly when you’re trying to generate media coverage. Many developers view the mere existence of their cool app as being newsworthy in itself, but while the launch might be exciting to the developer, 99 times out of 100, it means nothing to a reporter or blogger. The main objective of a reporter is to speak to their audience’s interests and tie those interests to current events — presidential election, Super Bowl, Valentine’s Day, the Final Four, the Oscars. Timing is everything when pitching a story. (Coincidentally, given the baseball spin, this article is timely because the annual spring opening of the Major League Baseball season in the US is a newsworthy event.)

Pinpointing an Audience

Additionally, in order to successfully market a new app, particularly a kid’s app, the developer has to strike a balance between reaching kids and their parents. David Eckstein fits the bill — a baseball hero to dads and sons who enjoy baseball together. Moreover, Eckstein was featured in the film Champions of Faith, so he appeals to those interested in biblical narratives.

Had Jumping Pages stuck with its original version of the app, the launch would have been too general, and the company would not have had an opportunity to reach a specific demographic. Many app developers feel that their apps are good for everyone — all moms or all kids, for example. Whittling down your audience to a very precise demographic is imperative. Reaching a niche audience, one that will respond positively to your app, is enough to spark word of mouth.

Triple Play and “A� Reviews

With David’s cooperation, Jumping Pages had a narrator whose back story matched that of the story’s protagonist — a star athlete tied to an newsworthy sporting event and who resonates with a specific demographic. Eckstein made for a triple play and thus gave the developer an opportunity for multiple story angles. The app was featured in over two dozen outlets using a variety of angles to appeal to enthusiasts of sports (Yardbarker), religion (The Christian Post), baseball (MLB.com) and technology (Wired and GeekDad).

Also, the timeliness of the World Series gave app reviewers a reason to talk about the app in October. The strategy was effective, and reviews were posted far more quickly than normal. All developers appreciate how important early reviews are, given the usual time lag. The app was praised: “like watching a Disney production,� “… animation is picture perfect and it made me want to read the story again and again,� “…is outstanding with fantastic, vibrant animations and images….� It continues to receive impressive reviews.

David and Goliath App

Cause, Demo and Contest

In addition, through Eckstein’s involvement, Jumping Pages had an opportunity to incorporate a cause marketing component into the launch. Eckstein’s charity of choice, Bags of Hope, helped promote the app to its members and Facebook fans. Next, with Eckstein’s involvement, a public reading and demo of the app was arranged, part of a post-launch strategy that would keep the app top of mind during the approaching holidays. A demo and reading of the app featuring Eckstein and his wife, Ashley, took place on November 30th in a Manhattan Apple store, during the start of the hectic holiday shopping season.

Finally, Jumping Pages sought a contest partner to run an iPad giveaway (iPad being the number one requested gift for the holidays and the platform of the David and Goliath app). It approached Smart Apps for Kids, a leading review website for children’s apps, to be a partner. The contest, which ran the week before Christmas, garnered over 1,500 new fans for Jumping Pages’ Facebook page and generated excitement for the app and for the developer during the critical last-minute holiday shopping period.

Hits the Mark on the First Shot

The founding of Jumping Pages and the launch of the David and Goliath app were a success. The high praise, along with the company’s achievements in development and marketing, have enabled the company to move forward on two forthcoming apps: an original interactive story that teaches kids and parents respect for the home, and an interactive musical app for kids, both set for release in the spring of 2012.

Rather than haphazardly launch its app or throw precious dollars at risky online maneuvers, Jumping Pages has demonstrated that a thoughtful, strategic and patient approach usually works best. Many app developers rush their product to market without considering the consequences. These days, with the overwhelming amount of information and the number of apps, the more carefully a developer plans their strategy, the more likely their product will launch successfully. And like David, they usually have just one shot at getting it right! Thanks to its partnerships, creative story angles, newsworthy connection, cause component, contest and patience, Jumping Pages did it right.

Lessons Learned

Keep these points in mind when planning your strategy:

  • Partnership
    Launches work best in pairs! Choose a partner whose background gels with your app. For example, Ruckus Media just announced a unique partnership with New York City’s PBS station for the “Cyberchase� app in its math series.
  • Relevance
    Find a way to tie your app to a current news or seasonal story. News outlets themselves know this better than anyone: just this month, the Washington Post launched a presidential election iPad app.
  • Audience
    Don’t play to a stadium. Rather, cater to an small meaningful audience. Talking about specific audiences, there are even apps for nose-pickers — as well as lawsuits for alleged patent infringement on those nose-picking apps!
  • Cause
    Share the wealth by helping a needy organization that fits your app’s demographic. This one really woke me up: did you know you could donate $0.25 to charity every time you hit the snooze button?
  • Relationship
    Incorporate unique ways to address and engage your audience. Self Magazine, a leading women’s lifestyle publication, is unveiling a mobile app game of its annual Self Workout in the Park, featuring fitness, health, fashion games with avatars, virtual goods and puzzles.

(al) (fi)


© John Casey for Smashing Magazine, 2012.


Drop Caps: Historical Use And Current Best Practices With CSS


  

The practice of using a large letter to mark the start of a text has been around for almost two thousand years. Illustrated caps increased usability by marking important passages and guiding readers through the text. Unlike their historic counterparts, drop caps on the Web don’t add value in terms of usability or readability—and they are hard for Web developers to control, often rendering differently across browsers.

Yet, front-end designers and clients often want to use drop caps as decorative elements. How should we implement them? Just as scribes, artisans, and early printers had a variety of methods for creating initial capitals, we Web designers have multiple methods to choose from. We can use an image of a letter, create a class to enlarge and place a letter, or use a first-child:first-letter to enlarge and place the first letter of the first paragraph. But which method should we use? Which method remains consistent across browsers? Which is most accessible?

Initial Caps In Manuscripts

Examples of initial caps have been found dating back to the 4th century CE. Early codex books (books with pages, as opposed to scrolls) did not have word spaces, sentence breaks, or paragraph breaks. The written word was not “read� the way it is now. Written text represented sounds; sounds held meaning. “Readers� lived in a primarily oral culture and verbalized the sounds to help them remember ideas and information already committed to memory.

Historically, initial caps were not just decorative elements. Scribes used them to mark where a new section—a new idea—started in the text. This in turn helped “readersâ€� find their place in a text.

Even as late as the 15th century, monks and scribes used initial caps to aid in visually “chunking� texts. Figure 1 shows a manuscript (lettered by hand) bible from 1407. The initial cap (P in the word Petrus) contains a picture of St. Peter, and is thus historiated; it relates to the text by showing a recognizable figure or scene. It is also illuminated; it is decorated with gold in order to bring the light of God to the reader.

Historiated caps not only helped mark the start of a new idea in the text, they acted as place markers for significant places in the text. Images related to the story served as memory aids for priests and monks who “read� the texts by flickering candle light.

But look closely (Figures 1 and 2) and you’ll see a far more subtle “initial cap.� The manuscript contains word spaces but does not contain a space between sentences. Thus, the letterer added strokes of red to the first letter of each sentence, giving visual separation to sounds represented on the page.

Illuminated letter P
Figure 1: Illuminated, Historiated Cap in a Latin Bible, 1407. Lettering by Gerard Brils, Belgium. (Image: Adrian Pingstone)

manuscript lettering
Figure 2: Detail of Latin Bible, 1407. Lettering by Gerard Brils, Belgium. Note the subtle use of color to emphasize the start of a new sentence. (Image: Adrian Pingstone)

Initial Caps In Printed Books

Of course, not all initial caps were as sexy as the image of St. Peter illuminated with pure gold. Initial caps were also used for mundane purposes: like indicating the alphabetical order of ideas. Routine today, alphabetizing was not originally used to organize information in books. Figure 3 shows a page from the table of contents of an incunabula (an early printed book). The initial caps were written in after the book was printed. The quality of lettering is not as beautiful as the St. Peter example above, but the letters serve an important purpose for the reader.

early table of contents
Figure 3: The last page of a table of contents from an early printed book. 1476. Initial caps added after the book was printed. (Image: used by permission of University of Glasgow, Special Collections)

Early printed books were often designed to replicate manuscripts. Printers left space in and around the text—so owners could hire an artisan to illustrate initial caps and borders. Figure 4 is an example of one such book; no initial cap was ever added. Note the initial space and guide letter provided for the illustrator. Even without the final initial cap, the text is readable (if you read Latin).

Figure 5 is a printed Bible from the same time and place (Venice, 1480). After it was printed, artisans supplied rubricated (written in red), decorated, and illuminated initials—thus continuing the formal tradition of the manuscript book.

Not all printed books required an artisan to finish the initial caps. Printers designed and created modular initial caps almost from the beginning. Figure 6 shows two inhabited caps (the illustrations do not represent a specific person or scene) set side-by-side, each starting a different translation of the New Testament. The inhabited caps and border where printed along with the text.

An initial space with guide letter
Figure 4: The printer left an initial space with guide letter. After printing, an artisan could be hired to add an initial cap. Venice, 1479. (Image: used by permission of University of Glasgow, Special Collections)

Printed Latin Bible
Figure 5: Printed Latin Bible. An artisan added various initials after the book was printed. Venice, 1480. (Image: used by permission of University of Glasgow, Special Collections)

Printed inhabited caps
Figure 6: The first complete published text of the Greek New Testament. The inhabited caps and border were printed with the text. Basel, 1516.  (Image: used by permission of University of Glasgow, Special Collections)

The role of written texts changed starting in the mid-1600’s, and initial caps fell out of favor. Newspapers allowed readers to share current ideas and information, scientific inquiry provided a basis of rational thought, and the typographic page simplified. The relationship between type and image continued to shift—primarily influenced by industrialization (which in turn influenced the art of printing, the speed at which goods could be produced and transported, and the development of a literate middle-class).

Drop Caps On The Web

Today, initial caps are no longer necessary; they are used primarily as decorative elements. Used for centuries in religious and scholarly texts, initial caps are associated with and communicate an “old� or “traditional� feeling. Thus, when we want to design a Web page that feels traditional, elegant, or historic, we find ourselves wanting to use drop caps.

There are four common methods for creating drop caps in HTML and CSS. But which one is best?

In an attempt to answer that question, I tested all four methods across 82 different browser-version-operating system combinations—including smart phones. (If you’re interested, you can read a list of the combinations and why I chose them).  In an attempt to identify which methods are accessible, I also tested them using VoiceOver on the mac, with Safari 5.1.1.

Which method is best? The answer is… not clear-cut.

Method 1: Image Replacement

If you want a drop cap that shows up consistently across all operating systems—including smart phones—there isn’t one. But using the Image Replacement method (Figure 7) comes close. Using an image for the drop cap holds up beautifully across 79 of the 82 combinations tested. It shifted placement on Opera Mini 5.1 (Android 2.2), and Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS).

image replacement dropcaps
Figure 7: An inhabited initial cap similar to those used in the 1516 Greek New Testament shown in Figure 6 above. [1] Using an image for the drop cap holds up beautifully across 79 of the 82 browser-version-operating system combinations tested. [2] It shifted down slightly on Opera Mini 5.1 (Android 2.2). [3] It shifted up on Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), resulting in an awkward space below the image. (Drop cap illustration: Bruce Maddocks)

HTML for the “Image Replacement” Example

<p><span class="drop f">F</span>ine typography does not … </p>

Note that I used two classes for the span. This allowed me to use one class (drop) to style the space, and use another class (f) to specify the image of the letter.

CSS for the “Image Replacement” Example

.drop{
    display:block;
    float:left;
    width:72px;
    height:72px;
    margin-top:5px;
    padding-right:8px;
    text-indent: -9000px;
    }
.f{
    background: url(images/f_small.jpg) 0 0 no-repeat;
    }

Note that I set the width and height of the space to the same dimensions as the image used to represent the drop cap. The text-indent attribute is used to place the actual letter outside the visible area of the space. We don’t want to see the HTML letter, but it’s important to include it so browsers without CSS enabled will show the entire word.

View the original Image Replacement example HTML document.

Method 2: Letter Over a Background Image

Placing a letter over a background image is a bit less successful (Figure 8). It works consistently across 77 of the 82 combinations tested. It posed a problem on the same three browsers as the Image Replacement method above—Opera Mini 5.1 (Android 2.2), and Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS)—as well as Windows Vista IE7 and Windows XP IE7. Granted, PC users increasingly use Windows 7 with IE8 or higher, so the last two browsers may not be a problem.

Dropcaps using a background image
Figure 8: A decorated initial cap similar to one used in the 1480 Printed Latin Bible shown in Figure 5 above—created using a background image. [1] Placing a letter over a background image holds up beautifully across 77 of the 82 browser-version-operating system combinations tested. [2] The drop cap lost styling on the Opera Mini 5.1 (Android 2.2). [3] The letter and image shifted up on Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), resulting in an awkward space below the image. [4] The letter was cut off on Windows Vista IE7 and Windows XP IE7.

HTML for the “Letter Over Background Image” Example

<p><span class="cap">A</span>nother way to … </p>

CSS for the “Letter Over Background Image” Example

.cap{
    display:block;
    float:left;
    width:72px;
    height:52px;
    font-size: 500%;
    color:#ffffff;
    margin-top:5px;
    padding-top:20px;
    margin-right:8px;
    text-align:center;
    background: url(images/flower.jpg) 0 0 no-repeat;
    }

Note that I added a padding-top in this version so the letter doesn’t touch the top edge of the background image.

View the original Letter Over Background Image example HTML document.

Method 3: Span Class, No Image

Creating a class for the drop cap (without a background image) is even slightly less successful (Figure 9). It works consistently across 76 of the 82 combinations tested. It posed a problem on the same five browsers as the Letter with a Background Image method above—Opera Mini 5.1 (Android 2.2), Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), Windows Vista IE7 and Windows XP IE7—as well as Windows XP IE6. Again, PC users increasingly use Windows 7 with IE8 or higher, so the IE6 browser may not be a problem.

Drop caps with a span class
Figure 9: A simple initial cap similar to those used in the 1480 Printed Latin Bible shown in Figure 5 above. [1] Creating a class for the drop cap without a background image holds up across 76 of the 82 browser-version-operating system combinations tested. [2] The drop cap lost styling on the Opera Mini 5.1 (Android 2.2). [3] It shifted up on Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), resulting in an awkward space below the image. [4] The letter was cut off on Windows Vista IE7, Windows XP IE7, and Windows XP IE6.

HTML for the “Span Class, No Image” Example

<p><span class="dropcap">H</span>istorically,… </p>

CSS for the “Span Class, No Image” Example

.dropcap{
    float:left;
    font-size:400%;
    margin-top:14px;
    margin-right:5px;
    color:#8C8273;
    }

Note that I added a margin-right of 5px in this version. The letter H worked well with this amount of space. The margin-right may need to change depending on the shape of the letter being used as a drop cap.

View the original Span Class, No Image example HTML document.

Method 4: First-Child:First-Letter

When it comes to consistency, using a p:first-child:first-letter is the least successful (Figure 10). It posed problems with the same 6 combinations as the Span Class, No Image method above—Opera Mini 5.1 (Android 2.2), Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), Windows Vista IE7, Windows XP IE7 and Windows XP IE6—and had inconsistent placement in the remaining 76 combinations tested. When setting the original drop cap placement for Firefox, 31 combinations remained properly aligned. The drop caps in the remaining 44 combinations were too high.

drop caps using first-letter
Figure 10: A rubricated (red) initial cap similar to those used in the 1476 and 1480 early printed books shown in Figures 3 and 5 above. [1] Using first:child-first:letter to create the drop cap resulted in proper placement in 31 of the 82 browser-version-operating system combinations tested. Note: the original placement was determined viewing the page in Firefox. [2] The drop caps in 45 versions were too high, resulting in an odd relationship between the drop cap and the text. [3] The drop cap lost styling on the Opera Mini 5.1 (Android 2.2). [4] It shifted up on Mobile Safari 4.0.5 (iPhone 4, iPhone 3GS), resulting in an awkward space below the image. [5] Again, the letter shifted up (Windows Vista IE7, Windows XP IE7), allowing one of the lines of text to move over and creating an awkward relationship with the text. [6] The letter lost all styling (including space) in Windows XP IE6.

HTML for the “First-Child:First-Letter (Firefox)” Example

<p>Historically, initial letters… </p>

CSS for the “First-Child:First-Letter (Firefox)” Example

p:first-child:first-letter{
    float:left;
    font-size:400%;
    margin-top:7px;
    margin-right:5px;
    color:#992E00;
    }

View the original First Letter, FireFox example HTML document.

Testing for Accessibility: VoiceOver

Before deciding which of the four methods is best, I wanted to test them all for accessibility. Getting type to look good sometimes means choosing presentational markup over semantic markup—which can affect how well a screen reader reads a Web page.

Using VoiceOver on the mac (Safari 5.1.1), only the First-Child:First-Letter method was read correctly. The other three methods use a class to separate the drop cap from the rest of the text; VoiceOver verbally separates the initial letter from the rest of the word (e.g. “H�… “istorically�).

Thus, the method that is least successful visually is most successful in terms of accessibility. So I decided to do some more testing before choosing a best method.

Method 4 Revisited: First-Child:First-Letter—Placement Based on Both Firefox and Windows 7 IE8

Using a p:first-child:first-letter is still the least consistent method. It posed problems with the same 6 combinations as the First-Child:First-Letter method above—and continued to have inconsistent placement in the remaining 76 combinations tested.

But when I increased the size of the drop cap and set the original placement based on simultaneously considering the results in both Firefox and Windows 7 IE8, the shift in placement didn’t feel as random (Figure 11). Some drop caps align with the baseline of the second line of text (Figure 11:1). Some align with the top of the first line of text (Figure 11:2). There is too much space below the drop caps that align to the top—creating a white square that pops out and calls attention to itself—but if one is a stickler for accessibility and semantic markup, this method could work.

drop caps using first letter revisited
Figure 11: When working with first-child:first-letter, simultaneously consider multiple browsers when placing the drop cap. [1] The revisited drop cap, viewed in Windows 7 IE8. The letter aligns nicely with the baseline of the second line of text. My original first-child:first-letter drop cap (in red) didn’t line up with anything when viewed in Windows 7 IE8. The placement looked random. [2] The same revisited drop cap when viewed in Firefox. The drop cap continues to come in lower, but due to carefully chosen font-size and margin-top, it continues to align with the top of the first line of text. My original first-child:first-letter dop cap (in red) was perhaps more successful. It didn’t have the white space below it when viewed in Firefox. The first-child:first-letter method is not perfect, but might be a good choice when aiming for accessibility.

HTML for the “First-Child:First-Letter (revisited)” Example

<p>Historically, initial letters… </p>

CSS for the “First-Child:First-Letter (revisited)” Example

p:first-child:first-letter{
    float:left;
    margin-top:7px;
    font-size:70px;
    margin-right:5px;
    color:#3D3529;
    }

View the original First Letter, Revisited example HTML document.

Letter Shapes And Letterspacing

Letters have different shapes (round, triangular, open, and square) which means they have different amounts of visual space around them (Figures 12 and 13).

letterspacing
Figure 12: The letters A and T naturally have more visual space than the letters O and M. Font designers adjust letterspacing so letters appear more even in text; the A and T are “tightened� in the final font.

different fonts have different letterspaces
Figure 13: Letter shapes and letterspacing change from font to font. Various Os have different visual space.

A well-designed font takes into account the varying amounts of visual space. Triangular and open letters are designed with tighter letterspacing (space is taken out). Square letters are designed with looser letterspacing (space is added). This approach to spacing is great in text; if type designers didn’t adjust spacing in a font, we’d end up with big gaps of space in the middle of words! But unfortunately, adjusted letterspacing creates problems in drop caps.

Letterspacing and the “Span Class, No Image” Method

Figure 14 shows various letters set as drop caps using the Span Class, No Image method. In Figure 14:1, the letters O and T look great, but the other four letters (C, A, K, L) are all a bit too tight to the text. In fact, the A and L look like they belong with the second line of their texts! (“A use various…� “Lit’s an open…�) Due to their open or triangular shapes, C, A, K and L have slightly tightened letterspacing in the font. This makes them look tight when used as drop caps, even though all the letters are set with the same right-margin: 5px.

In Figure 14:2, the letters are more comfortably spaced with their texts. Each letter has a unique class styled with an appropriate margin to each. Right margins range from 5px to 8px.

controlling letterspacing with classes
Figure 14: Different letters need a different amount of right margin. [1] The O and T have appropriate space around them. The other letters are too tight to their texts. [2] Using a unique class for each letter, right margins have been adjusted. The change is subtle, but the L no longer looks like it belongs with the second line of text!

HTML for the “Span Class Letterspacing” Example

<p><span class="dropcap_o">O</span>nce upon a time,... </p>
<p><span class="dropcap_a">A</span>nd when she tested... </p>
<p><span class="dropcap_t">T</span>he drop caps used... <p>
<p><span>C</span>an you use... </p>
<p><span>K</span>ittens don&rsquo;t... </p>
<p><span class="dropcap_l">L</span>ater she realized... </p>

CSS for the “Span Class Letterspacing” Example

.dropcap_a, .dropcap_c, .dropcap_k, .dropcap_l,.dropcap_o, .dropcap_t {
    float:left;
    font-size:370%;
    margin-top:14px;
    color:#8C8273;
    }        
.dropcap_o,.dropcap_t{
    margin-right:5px;
    }
.dropcap_k {
    margin-right:6px;
    }
.dropcap_a, .dropcap_c {
    margin-right:7px;
    }
.dropcap_l{
    margin-right:8px;
    }

View the original Span Class Letterspacing example HTML document.

Letterspacing and the “First-Child:First-Letter” Method
Letter shapes and letterspacing create similar problems in drop caps set using the First-Child:First-Letter method. In Figure 15, there is a generous space between the O and its text. The A, on the other hand, is too tight and looks like it belongs with the second line (“A various letters…�). Look at the O again; the curved bottom of the letter adds visual space and makes it look like it’s floating higher than the A and T in relation to the text.

The T has the best spacing—it’s tighter than the O and looser than the A—but creates an odd enclosed white space between the stem (the vertical stroke) of the T and the text. This happens when using the First-Child:First-Letter method because we have less control over the vertical placement of the drop cap (remember, we have to compromise size and placement to achieve the best results across browsers).

letterspacing and first-letter, letterspacing and image replacement drop caps
Figure 15: Two methods that apply identical spacing to every drop cap. [1] Using first-child:first-letter creates inconsistent visual space if different letters are used as drop caps on a web site. [2] Using an image behind the drop cap creates a consistent visual space for the drop caps to inhabit.

Unfortunately, we can’t adjust the letterspacing; it’s not possible to create 26 unique versions of first-child:first-letter and style them using only HTML and CSS. (If anyone has figured out a solution, please share it with us in the comments.) Thus a website using the First-Child:First-Letter method will be riddled with awkwardly spaced drop caps.

Letterspacing and the “Image Replacement” and “Letter Over an Image” Methods

Both the Image Replacement method and the Letter Over an Image method (Figure 15:2) have appropriate spacing regardless of the letter used. These methods set a consistent width to hold the image; variations in letterspacing take place within the image border—not between the drop cap and the text.

But what if you want to use the image replacement method to insert images of drop caps that don’t have a consistent width?

Figure 16 shows various letters set as drop caps using the Image Replacement method; without a background, the drop caps no longer have a consistent width. In the left panel (Figure 16:1), the letter M looks great, but the letters O and I have awkward spaces between the drop cap and the text. This variation in spacing is not due to letterspacing in the font; it occurs because the letters themselves have different widths. In the right panel (Figure 16:2), the letters are more comfortably spaced with their texts. Each letter has a unique class styled with an appropriate width. Widths range from 41px to 85px.

letter widths and image replacement drop caps
Figure 16: Letter width can also affect the amount of visual space around a letter. [1] The M has appropriate space around it. The O and I are narrower, so the space provided is too wide. [2] Using a unique class for each letter, widths have been adjusted.

HTML for the “Image Replacement, No Background” Example

<p><span class="drop_o o">O</span>nce upon a time... </p>
<p><span class="drop_i i">I</span>nitially, she made sure... </p>
<p><span class="drop_m m">M</span>any shapes were... </p>

Note that I used two classes for each span. This allowed me to use one class (drop_o) to style the space, and use another class (o) to specify the image of the letter.

CSS for the “Image Replacement, No Background” Example

.drop_o, .drop_i, .drop_m{
    display:block;
    float:left;
    height:72px;
    margin-top:8px;
    text-indent: -9000px;
    }
.drop_o {
    width:73px;
    }
.drop_i {
    width:41px;
    }
.drop_m {
    width:85px;
    }
.o{
    background: url(images/didot_o.jpg) 0 0 no-repeat;
    }
.i{
    background: url(images/didot_i.jpg) 0 0 no-repeat;
    }
.m{
    background: url(images/didot_m.jpg) 0 0 no-repeat;
    }

Note that I set the height of the space to the same dimensions as the image used to represent the drop cap. The widths are wider than the images; width provides a margin of space between the drop cap and the text.

View the original Image Replacement, No Background example HTML document.

The Best Method: Merging Tradition And Technology

Balancing issues of consistency, accessibility, and letterspacing, I recommend using either Method 1: Image Replacement or Method 2: Letter Over an Image. Both hold up well across most browsers tested; both methods allow Web designers to create elegant, decorative drop caps.

If you absolutely do not want to use images for your drop caps, then I recommend using Method 3: Span Class, No Image.

Drop Caps Do Not Promote Readability

Some may disagree with my recommendation and say that First-Child:First-Letter is a better choice due to accessibility issues; it was the only method to work properly with VoiceOver.

I understand that argument – I usually aim for accessibility. But when it comes to drop caps, I find the screen reader’s “incorrect� verbalization is ironically closer to the experience a sighted reader has. When reading text with a drop cap, we always “read� the letter, then the partial word, and then have to piece the two together. (Try it with Figure 16 above. Do you read “O� and then “nce� and then do a bit of mental gymnastics to read the word “Once?�)

The visual separation caused by using a drop cap interferes with word recognition for everyone. Drop caps are decorative elements. When we use them, we are setting a tone—often at the expense of readability.

Beautiful Drop Caps Can Be Inserted into the HTML Automatically

One could argue that First-Child:First-Letter is still a better choice because it eliminates the need to insert syntax in the HTML for every drop cap. Using first-child:first-letter, drop caps are created automatically.

But there’s another way to automatically create drop caps. With a little javascript you can insert span classes (with or without images) into your HTML. You can even create multiple unique classes (e.g. 52 classes, two for each letter) and articulate which class—or classes—to apply.

Jason Lynes of NorthTemple.com provides a clearly written case study on using jQuery and CSS to insert Image Replacement drop caps. Lynes’ case study highlights an article for the LDS Church. I’m not inviting conversation about the content of the article; I am providing the case study as an excellent tutorial on “automating� drop caps with jQuery and CSS.

I’ve tested Lynes’ method – I used it to create a page of Span Class, No Image drop caps. It works like a charm and degrades beautifully (drop caps revert to plain text on browsers that are not javascript enabled). View my original Span Class, jQuery example HTML document.

Beautiful Drop Caps Take Time and Effort

good drop caps take time and effort
Figure 17: Another look at initial caps from (clockwise from top left) 1407, 1476, 1480, and 1479. [1] Two of the initial caps are painted with care. [2] The other two are examples of “quick solutions� to initial caps: a set of hastily written caps and an initial space set aside for an artisan to fill in.

Deciding to use drop caps on a website means making a conscious choice to use a primarily decorative element. Unlike initial caps in manuscripts and incunabula, a drop cap on the Web doesn’t add value in terms of usability or readability; its main purpose is to look good. And making a drop cap look good—whether in a manuscript, an incunabula, or on the Web—takes time (Figure 17).

Even if we automate our drop caps with jQuery, we need to do the preliminary work—make images, test letterspacing, and set up 26 (or 52) unique classes. Creating beautiful, high quality drop caps may sound like a chore, but we are continuing a respected tradition that is almost two thousand years old. When we look back through history, we see the best initial caps have always taken time and effort.


© Laura Franz for Smashing Magazine, 2012.


Keep Your Analytics Data Safe And Clean


  

Whoever works with analytics on a day-to-to-day basis knows how important it is to have a continuity with the data. Any slip might be fatal: data can disappear, trends misunderstood and jobs lost. Losing data can have long-lasting consequences, as very often it isn’t possible to reprocess the data—so what is lost cannot be recovered.

For this reason, it is essential to have a place where you can test changes to your settings and configurations. It is also important to keep track of changes in a way that they can be used to provide a context for analysts, so that when you are looking at incomprehensible spikes in past data, you can check whether any changes were made to the data collection methods (or if an offline campaign was in place during the period analyzed). Having such a process in place will help to keep data safe from loss and clean from inaccuracies.

As Neil Mason describes on his presentation about Data Discovery: “all data is dirty and needs to be cleaned and transformed, this is the heavy lifting stage.” Below I describe four techniques that will help analysts and marketers to ease the burden of inaccurate data usage Google Analytics. I provide examples on how this can affect the data, and share tips on ways to make them happen.

Google Analytics Accounts And Profiles

The Google Analytics code site offers an in depth explanation of the hierarchy used by the tool to manage report access and data collection. There are three important levels that we need to be aware of:

  1. Account: An account is the mother of all Web properties and profiles, and has a unique account ID that can be used to track multiple websites.
  2. Web Property: The web property has a unique ID, which is a combination of the account ID and additional digits. Since different Web properties have different IDs, their data cannot be merged.
  3. Profile: the gateway to the website reports. It determines which data from your website appears in the reports. Filters can be applied to profiles in order to segment the data; for example, it is possible to create a profile only with visitors from USA, only from new visitors, etc. Since profiles use the same account and Web property IDs, data for multiple profiles can also be seen in aggregate.

Below is part of the scheme provided on the code from the website mentioned above. The image well represents the possibilities of data collection and management.

Google Analytics accounts and profiles
Diagram showing the possible Analytics account configurations.

Important to note that Google Analytics still misses the mark on an important feature related to account configuration: report level access. This means that the lowest access that can be given to a user is a profile, so it is not possible to provide access to reports. As I wrote in an article about Google Analytics Perception & Reality:

As of today, Google provides just two options when it comes to providing access: Administrator (who can access anything in the account) and Viewer (who can access specific profiles). This division is far from good. In any mid-sized company, the data needs to be more modular (i.e. enable showing different reports to different people).

Creating an Analytics Staging Profile

Let’s suppose you read in a random blog that you should create a filter to lowercase URIs for all of your profiles (if you don’t have one yet, check point five on this implementation checklist). And suppose you have no idea how this can impact your data.

The best way to learn how filters affect your Google Analytics data would be to have two profiles with the exact same settings (the real profile, and the test profile) and apply a new filter only to the test profile. Once it is applied, you can check the data and compare the number to learn if anything went wrong. Here is an article from the Google Analytics Help Center on how to create profiles.

Creating an Analytics Staging Account

If you work in the Web Analytics field long enough, you have certainly experienced data loss as a consequence of bad implementations. It happens, and the best we can do is to have a Web Analytics Process in place that will help us avoid it. Not long ago, I implemented the _trackPageLoadTime() method (now deprecated) for a website, and as a result from a lack of attention, I lost six days worth of data (yes, I didn’t log in quite enough to Analytics during this week!) See graph below:

Google Analytics bad implementation
Example of how a bad Google Analytics implementation can affect data collection.

The story above illustrates the fact that code changes should be dealt with carefully. Since most websites do have a staging site where changes are tested before going live, I suggest having a different tracking code used for those environments to test code changes on the Google Analytics script (i.e. a new Google Analytics account). This technique is very similar to the one proposed above to check filter changes—it only goes one step further.

Tracking Profile Changes & Configurations

When it comes to both external and internal changes, context is one of the most important factors for analyzing data. For this reason, it is crucial to have a log of changes that affect your data, as well as changes in marketing campaigns and other company efforts. Below I present two ways to keep this data in an accurate and accessible way.

Keeping Track of Internal Changes

Changes are constantly made to Google Analytics profiles by users: website goals, improved filters, new features, and others. Every change may impact data in several ways, even when not expected. For this reason, I propose a method that will help to keep track of those changes, especially in large organizations where more than one person is involved with Google Analytics. Even when one person is involved, this is important as employees usually do not work with just one company “to infinity… and beyond!”

In order to make this task easy and centralized, I propose using a Google Docs form. Using such a form will facilitate the collection and sharing of the changes made to a Google Analytics account. The form should be created so that multiple teams will be aware of all changes. These will then be aggregated for historical knowledge that can be used by the whole team (and future teams members).

Below is an example of such a form with fields that you might want to create (learm how to build a Google Docs form).

Google Analytics settings form
Example of a Google Docs form that can be used to track Google Analytics changes.

Keeping Track of External & Overall Changes with Annotations

Back in 2010, The Analytics team had announced a feature which in my opinion is one of the most important features of the tool: Google Analytics Annotations. This feature allows website managers to provide context for where the numbers live (the graphs on the interface), allowing for richer analyses. Here are some important occasions when you should use this feature:

  • New offline marketing campaigns (e.g. radio, TV, billboards).
  • Major changes to the website (e.g. design, structure, content).
  • Changes to tracking (e.g. changing the tracking code, adding events).
  • Changes to goals or filters.

While annotations can—and should—also be used for technical changes to the website (as mentioned above), it is important to keep them at a high level. This means that you shouldn’t add too much information about your changes, just the overall picture; otherwise the annotations will quickly become overcrowded. Therefore, the use of both methods described above (form and annotations) should create an optimal mix. Below is a video explaining how to use the Annotations feature:


Video explaining how to use the Google Analytics Annotations feature.

Closing Thoughts

In this post we discussed ways to avoid bad implementations—by putting into place a process that requires users to report on changes made to their Google Analytics accounts. This not only helps in avoiding mistakes, but also helps find the source of problems, and solutions for fixing them quickly.

Google Analytics is a great tool, and one of its greatest qualities is that it makes Analytics ubiquitous—most people in any organization can use it; from Management to Marketing to IT. This means that many hands must deal with the tool, which requires an easy way to deal with the changes to those tool settings and configurations. Hopefully this post has provided some ideas on how to do it.

Please comment with any additional ideas on how to keep Google Analytics data safe and clean.

(jvb) (il)


© Daniel Waisberg for Smashing Magazine, 2012.


Desktop Wallpaper Calendar: April 2012


  

We always try our best to challenge your artistic abilities and produce some interesting, beautiful and creative artwork. And as designers we usually turn to different sources of inspiration. As a matter of fact, we’ve discovered the best one — desktop wallpapers that are a little more distinctive than the usual crowd. This creativity mission has been going on for over four years now, and we are very thankful to all designers who have contributed and are still diligently contributing each month.

We continue to nourish you with a monthly spoon of inspiration. This post features free desktop wallpapers created by artists across the globe for April 2012. Both versions with a calendar and without a calendar can be downloaded for free. It’s time to freshen up your wallpaper!

Please note that:

  • All images can be clicked on and lead to the preview of the wallpaper,
  • You can feature your work in our magazine by taking part in our Desktop Wallpaper Calendar series. We are regularly looking for creative designers and artists to be featured on Smashing Magazine. Are you one of them?

Noisy Neighbors

Designed by Katerina Bobkova from Ukraine.

Smashing Wallpaper - April 2012

Bird Songs

"”Spring would not be spring without bird songs.” – Francis M. Chapman." Designed by Raymond Lopez from USA.

Smashing Wallpaper - April 2012

Bear On The Moon

Designed by Oxana Kostromina from Germany/Russia.

Smashing Wallpaper - April 2012

Retro Light Wall

Designed by Marian Cepa from Slovakia.

Smashing Wallpaper - April 2012

Happy In April

"Here’s to a cheery-even-when-it’s-raining kind of April!" Designed by Candace Jones from USA.

Smashing Wallpaper - April 2012

The Heart Sees What Is Invisible To The Eye

"What your sees and what your heart feels may not be same.The heart sees things more clearly than the eye. Best Example is feeling of love which can be feel and can never be seen. In Love, you will see what your heart wants you to see, to feel, to make you happy which an eye can’t see." Designed by Harshi Shah from India.

Smashing Wallpaper - April 2012

Who’s The Fool

Designed by Julia Factor from Israel.

Smashing Wallpaper - April 2012

Tidy Desktop

"Spring time, cleaning time! Here’s a simple and clean calendar to help you keep your desktop nice and tidy." Designed by Axura from Italy.

Smashing Wallpaper - April 2012

Scrap April

"April is a month of love,dates and flowers." Designed by Irur from Ukraine.

Smashing Wallpaper - April 2012

Circus

"There are 48 more clowns in this picture. Find them all." Designed by Cheloveche.ru from Russia.

Smashing Wallpaper - April 2012

Vintage Times

Designed by Pietje Precies from The Netherlands.

Smashing Wallpaper - April 2012

The Big Burn

"Indoor Tanning is more risky than you think! It’s true! Before you go back to the tanning bed, get the real facts from real sources. Find out why youth are more at risk and discover the burning truth about indoor tanning." Designed by Zgm from Canada.

Smashing Wallpaper - April 2012

Jean-cloud Van Damme

"Hope that this little cloud will make you laugh. Happy Fools’ Day everybody)." Designed by Marika Smirnova From “oblako Studio” from Russia.

Smashing Wallpaper - April 2012

Busy April

"This wallpaper based on idea of Estonian folk tale. We want to believe we are very busy nation and that is our goal to be the best in everything :-)Springmonth is a good start to change life more active and busy. Of course there are little detail focused on Easter Holiday, too." Designed by Anne Pikkov from Estonia.

Smashing Wallpaper - April 2012

Graceful Descent

"Ahh, the warm, fat raindrops of Spring, gently floating to Earth. Don’t they look happy?" Designed by Matt Mink from USA.

Smashing Wallpaper - April 2012

Cherry Blossom

"The photo was taken in Toronto High Park in 2011." Designed by Tetyana Kovyrina from Canada.

Smashing Wallpaper - April 2012

Always In Spring

"Color and optimism for everyone this spring." Designed by Destaca Imagen from Spain.

Smashing Wallpaper - April 2012

Spring Up !

"Energy-efficient wallpaper." Designed by Anna Pochodaj from Poland.

Smashing Wallpaper - April 2012

Dyed Easter Eggs

"Colored Easter Eggs were a really special part of my family’s Easter traditions. The eggs symbolize new life offered by Jesus’ death and resurrection on Easter." Designed by Evan Chiu from Cincinnati, OH, USA.

Smashing Wallpaper - April 2012

Bulbs

"April light is coming…" Designed by Dennis Nielsen from DK.

Smashing Wallpaper - April 2012

Sky Buster

"Get ready to lift you mood and get some new energy!" Designed by Pixeltoxhtml Team from India.

Smashing Wallpaper - April 2012

Funny Bunny

"Our funny bunny takes a look at the giant carrot in shape of an easter egg." Designed by Adconcept Werbeagentur Gmbh from Germany.

Smashing Wallpaper - April 2012

Fools Month

"Really liked this quote from Mark Twain, so wanted to design something around fools day on the first of the month." Designed by Martin Lucas from UK.

Smashing Wallpaper - April 2012

Spring Invasion

"Spring is here and you can’t hide! Just beware of viruses ‘cause you don’t want to stay inside on such a beautiful day." Designed by Nose Invaders from Sweden.

Smashing Wallpaper - April 2012

Life Is Beautiful

Designed by Christine Bradway from USA.

Smashing Wallpaper - April 2012

Skate Boarding Into April

"Brownie Bunny wishes all a blast into the 2nd quarter of the year! Stay cool, cute and green! =)." Designed by Lew Su-ann from Brunei Darussalam.

Smashing Wallpaper - April 2012

Along Came A Spider

Designed by Octavo Designs from USA.

Smashing Wallpaper - April 2012

There’s No You In I

"There’s No You In I wallpaper typography, helvetica, minimal." Designed by Dan Ciobanu from UK.

Smashing Wallpaper - April 2012

Join In Next Month!

Please note that we respect and carefully consider the ideas and motivation behind each and every artist’s work. This is why we give all artists the full freedom to explore their creativity and express emotions and experience throughout their works. This is also why the themes of the wallpapers weren’t anyhow influenced by us, but rather designed from scratch by the artists themselves.

A big thank you to all designers for their participation. Join in next month!

What’s Your Favourite?

What’s your favorite theme or wallpaper for this month? Please let us know in the comment section below.

Stay creative and keep on smashing!

(il) (vf)


© Smashing Editorial for Smashing Magazine, 2012.


Publish What You Learn


  

I don’t think anyone can deny that the Web has changed the way people teach, learn, and do research. Of course, this doesn’t mean that everything we read online is true and accurate—far from it. But I believe that through honest discussion and objective collaboration, accurate and useful information is much more likely to be the end result of any educational endeavor.

In the final week of November 2011, a smart group of developers launched a project called Move The Web Forward, which you can read more about in Addy Osmani’s Smashing Magazine article.

For this post, I want to focus on one piece of advice given by those developers in that project, under the heading “Writeâ€�.

The advice is: Publish what you learn.

As soon as I read that exhortation (which originated with this tweet), I knew this was a project made by a group of people who cared about the Web and that they understand what it takes to move forward as developers, and as an industry.

Let’s explore those four simple words, because I believe that concept is at the heart of how much progress has been made in the front-end development niche. And it’s something that could help almost any industry, in any field.

Just Do It

Very few blogs start out with much traffic at all. Unless the blog is based on an already existing brand that has a lot of exposure, most blogs will begin with very few readers. Even Smashing Magazine, who now has millions of readers, subscribers, and followers, started out with nothing.

CSS-Tricks is another good example of a blog that started out as nothing, and has grown into a thriving, collaborative community. Its founder and curator, Chris Coyier, certainly couldn’t have predicted how much that website would grow. And I’m sure we could come up with additional examples of websites that went from zero to hero in a relatively short time.

Why did they become successful? Because they published what they learned. At one time I somewhat favored the view that too many blogs were being launched. But I think the benefits of so much being published in so many different places outweigh any drawbacks.

Of course, this is not to suggest that the reason you want to publish your thoughts is to “make it big”—that should be secondary, if considered at all. In fact, what you publish doesn’t necessarily have to be on a run-of-the-mill monetized WordPress blog. It could be a GitHub account, a Wiki-style website, a Tumblr feed, or even a bunch of quick tips on a simple Twitter account.

Which brings us to another important supplement to this theme. Immediately after the folks at Move The Web Forward told us to publish what we learn, they made an equally important statement.

Don’t Be Afraid To Make Mistakes

You might be thinking: “Wait. What? Me? Publish a blog? I’ve been coding websites for a measly six months (or some other ostensibly short period of time). Even if people visit my website and read it, my articles will probably get torn to shreds!”

That doesn’t matter. What’s important is that you recognize the value in researching, teaching, collaborating, and correcting mistakes. That’s why the Move The Web Forward folks went on to encourage writers to “keep your posts updated.”

And that’s why Rebecca Murphey, when discussing how to get better at writing JavaScript, said:

“The number one thing that will make you better at writing JavaScript is writing JavaScript. It’s OK if you cringe at it six months from now. It’s OK if you know it could be better if you only understood X, Y, or Z a little bit better. Cultivate dissatisfaction, and fear the day when you aren’t disappointed with the code you wrote last month.”

In this case, Rebecca was talking about actually writing code, not writing about code. But the same principle applies: you will get better when you make mistakes and correct them.

And if you think you’ve made some progress and you have something unique and educational to share, don’t be afraid to offer it to one of the many design and development blogs that will gladly pay you for content.

Comments Are Part Of The Content

There are too many websites that view the readers’ comments as secondary content that is not nearly as valuable as what the author has to say in the main article. Every website should continually make changes or updates to content that is clearly shown to be incorrect. This shows that the publisher wants to provide accurate information, and that they respect the views of their readers.

In fact, you could make the argument that without reader comments, the quality of content on many design and development blogs would not be as strong as it is today. On my own website, I’ve written so many things that were just downright wrong. In some cases, things can be a matter of opinion and personal preference. But in other cases, they’re just factually incorrect. In indisputable cases, I’ve always tried to post updates to articles and credit the commenters who pointed them out.

Teachers Learn By Teaching

Randy Rhoads, a popular rock guitarist (who died in a plane crash in 1982), was well-known for being a guitar teacher. He once said:

“I’ve been playing about 18 years and I started to get a style when I started teaching.”

In other words, he believed that his success as a guitarist was largely impacted by the fact that he spent time teaching his skill to others. The same can be true for any one of us.

I’ve learned so much from readers’ comments and from doing research on stuff that I plan to publish. I’ve even learned from content I never actually did publish. The Move The Web Forward project, once again, summarizes this point quite nicely:

“Teaching is a great learning tool as well. So, even if you are getting started in an area, you’re helping yourself by writing about it as well.”

GitHub Gets It Right

The collaboration level on many projects from the “social coding” website GitHub is truly amazing, and is something that shows how revolutionary the Web really is.

GitHub's method of social coding is revolutionary

Think about a large project like HTML5 Boilerplate. When that project was first released, many front-end devs were amazed at how much front-end knowledge had been packed into a single starting template. Many were even intimidated by it. But what it is today is nothing compared to what it was when it first launched.

Why? Because from the get-go the contributors to the project had the same attitude that Paul Irish expressed in the launch post of his blog:

“I’m very interested in your contributions… what else deserves to be in this base template?”

With those words, Paul began what might be the most important front-end development project in the Web’s short history. And the collaboration continues today. In fact, there have been over 1000 issues opened and closed on that repo. All because Paul Irish—who has every right to never solicit feedback, because he’s so dang smart—encouraged collaboration.

Blog Posts Should Be Like GitHub Repos

The collaboration on apps like GitHub should be exactly what happens on blog posts. The readers posting comments should read the entire article, and should offer constructive, polite criticism and suggestions, without any unnecessary negativity.

An end to negativity

If the author feels the advice is not accurate or best practice, than he should explain why. If it’s established that the point needs clarification and/or correction, then he should humbly accept this and post an update, crediting the person or persons that brought it up. Personally, I’ve seen too many posts where the author doesn’t make corrections, even when clear technical or factual errors are pointed out.

This doesn’t mean that “majority rules”—that would be ridiculous, and would probably cause more problems than it solves (particularly in matters of opinion, where often there are no hard-and-fast rules).

But if it’s a technical matter, then the author has the responsibility to make updates and keep the information fresh, practical, and relevant. This is especially important if readers are finding the article via search. The “copy-and-paste-but-don’t-read” mentality is common among developers looking for quick solutions. We all face tight budgets and even tighter deadlines, so the last thing we want to do is verify a piece of code’s quality by reading a 900-word accompanying article along with 50+ comments.

If you notice a lot of search traffic coming in for older articles on your website, that might very well be incentive to update those older posts, and ensure you’re not promoting something that you no longer believe is accurate or best practice. And this has a twofold benefit: It will get you even more traffic, and your readers will have accurate information that they can trust.

So let’s do our best to imitate collaborative communities like those found on GitHub and StackOverflow, and continue making progress by correcting our errors. This will help all of us overcome the fears inherent in publishing what we learn.

The “TL;DR” Conclusion

If you don’t read this entire post, or if you take nothing else away from it, then just remember these points:

  • When you learn something, write about it, and don’t do it just to make money off it.
  • Don’t be afraid to make mistakes.
  • Teaching others will help you learn.
  • Encourage collaboration by allowing a free flow of constructive comments.
  • If you make a mistake, fix it.

I think this is a winning strategy for all those who are involved in design or development blogging, as well as tutorial writing.

When we’re willing to put ourselves out there, listen to what our peers have to say, and improve as needed, we will become better developers, and will help each other solve design and development problems in a more effective manner.

As this article suggests, your voice is just as important in this discussion. What do you think? Are you motivated to publish what you learn? Do you think collaboration and constructive feedback is an important part of moving the Web forward? We’d love to hear your thoughts.

Image used on frontpage: opensourceway.

(il) (jvb)


© Louis Lazaris for Smashing Magazine, 2012.


  •   
  • Copyright © 1996-2010 BlogmyQuery - BMQ. All rights reserved.
    iDream theme by Templates Next | Powered by WordPress