<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>

    <title>A List Apart: Comments on: Gentle Reader, Stay Awhile; I Will Be Faithful</title>
    <link>{url_title_path=articles/}</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:rights>Copyright 2012</dc:rights>
    <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />




    <item>
      <title>Posted by: Jason Mayoff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#1</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#1</guid>         
	  
      <description><![CDATA[I wholeheartedly agree with your suggestion that we write for one person.  I'm in the radio business and just as in writing, the best broadcasters *speak* to only one person, the listener. ]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Christian Watson</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#2</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#2</guid>         
	  
      <description><![CDATA[Amber, you say that online readers tend to have little patience; however, I had to read over 200 words of your article (not including the wonderfully vague title) to really understand what it is about.

My impression (rightly or wrongly) from this - especially given ALA's audience - is that you are writing for yourself rather than your reader.

Overall, I like the theme of your article, although it was a struggle to get through it, largely because of presentational issues. One of your paragraphs is 10 lines and 175 words long! 

As a reader I look at that and see a block of intimidating text and am inclined to skip straight to the next paragraph.

Much as I like the advice you offer, I would suggest that readers would be better off learning the basic rules of writing for the web before moving on to your 'master class'.

As a suggestion, most news sites such as the BBC are a great place to learn how to write compelling content that is also readable.

Alternatively, I link to a number of "good articles about writing for the web":http://www.smileycat.com/miaow/archives/cat_writing_for_the_web.html  on my own site.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Gray Miller</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#3</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#3</guid>         
	  
      <description><![CDATA[What has especially touched me is your comment about "just one reader." I was reminded recently of this idea when a friend who I'd not seen for over a year asked how my podcast was doing. "Not so well," I glumly told him, "only about 800 listeners."

He was dumbfounded. "When I saw you last year, when you were starting," he said,"you were giddy because you had dozens of listeners!"

He was right. I had started it thinking that if I only had 5 listeners, I'd be happy. And when I do public speaking, it's not to the audience, it's in the engaging, conversational style I learned from my father. I'd not thought of applying it to writing, but I suspect the best writing I do does apply this idea.

Thanks--looking forward to reading your other work. And very jealous that you live in one of the coolest cities in the nation.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Jeff Atwood</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#4</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#4</guid>         
	  
      <description><![CDATA[I agree with Christian's criticisms. Way too many words for web writing! Needs more Strunk & White.

Also, can I humbly suggest a global moratorium on the use of the ultra-cliche "at the end of the day"? Every time I read this phrase, I cringe, and I have to force myself to keep reading any further.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Joe Flood</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#5</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#5</guid>         
	  
      <description><![CDATA[The snapshot blurb off to the right of the article is an excellent innovation.  It's also "faithful" by giving us readers an idea of what the article is all about before we begin.  I suggest moving it into the main column, above the article, as a guide to readers.

Also, on the idea of writing for one reader... we use that on the site I work on but it's tough to get scientists and researchers to write for a general audience.  Practical ideas on how to achieve some of the ideas mentioned in your article would be helpful.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Christian Watson</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#6</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#6</guid>         
	  
      <description><![CDATA[The snapshot idea is definitely a good one - too bad it's in the wrong place. I never even noticed it. Why can't the summary or snapshot go at the beginning of the article?]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Bill Maslyn</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#7</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#7</guid>         
	  
      <description><![CDATA[While I agree the post was a bit wordy, I'm glad I read it. It's an issue I've been struggling with myself. When I started my blog late last year, it was mostly for my family and friends. But somewhere along the line, I was seduced by the idea that I could write to attract "traffic" that could generate clicks and revenue. Not only had I lost sight of my reader, I wasn't even thinking in terms of an audience. And it wasn't long before I realized I just wasn't enjoying it anymore.

I was reminded of why I started when my aunt asked why I hadn't posted in so long. So, thanks for the reality check.

I have my reader.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: V. Berg</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#8</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#8</guid>         
	  
      <description><![CDATA[Perhaps using words like "zeitgeist" ( which your casual reader might have to take a time-out to go jaunting off to Merriam-Webster On-line to check the context of... ) in an informative article might want to be re-thought. I was doing great up to that point. ;-)]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: John Lascurettes</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#9</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#9</guid>         
	  
      <description><![CDATA[bq. Perhaps using words like â€œzeitgeistâ€? â€¦ in an informative article might want to be re-thought. [sic]

Why? Is it so hard to look up a word once and a whileâ€”particularly when it is used in a context such that the meaning can be deduced by the reader?

bq. If I know a date will be attached to my work, it is probably less important to place my writing in its proper cultural or historical context. On the other hand, it doesnâ€™t hurt to remind my reader of the *zeitgeist* that shapes my work.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/#10</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#10</guid>         
	  
      <description><![CDATA[So far, everyone who has commented on wordiness have been male, as best as I can deduce from the names provided.

As I read, I thought, "This is pretty feminine for an ALA article".  There was no value judgement in the thought, just a general observation.

Is it wordiness, or is it communicating ideas differently than we are accustomed, particularlay in a "technical" journal like ALA?  Does this stylistic differencee have anything to teach us?  Does it offer any additional food for thought in the context of the content of the article?  Could it even have been a conscience decision on the part of the author?]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Erin Kissane</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#11</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#11</guid>         
	  
      <description><![CDATA[If you look around the web for advice on "web writing," you tend to find a lot of the same formatting advice we've been slinging (as an industry) since the late nineties: chunk your content, use lots of subheads, use lists, etc. Then there's the endless stream of "writing for SEO" and "writing great blog headlines" advice.

A lot of this advice is sound and worth reading and following...but it's hardly the only kind that matters. There's more to good writing than "chunking," and there's more to online communication than "killer headlines." 

The kind of advice Amber offers is less common and more challenging -- which is why I hope we'll have the opportunity to publish more of her work in the future.

(And as for _zeitgeist_...c'mon, folks. If you hope to become a better writer, you can't afford to be a lazy reader.)]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Erin Kissane</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#12</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#12</guid>         
	  
      <description><![CDATA[bq. Is it wordiness, or is it communicating ideas differently than we are accustomed, particularlay in a â€œtechnicalâ€? journal like ALA? Does this stylistic differencee have anything to teach us? Does it offer any additional food for thought in the context of the content of the article? Could it even have been a conscience decision on the part of the author?

Interesting stuff, Derek. I'll refrain from adding my own thoughts just yet, but I've personally noticed that forum comments vary in certain ways depending on the sex of the article's author -- at ALA, but also elsewhere.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: John Lascurettes</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#13</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#13</guid>         
	  
      <description><![CDATA[bq. (And as for zeitgeistâ€¦câ€™mon, folks. If you hope to become a better writer, you canâ€™t afford to be a lazy reader.)

Exactly.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: isaac kearse</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#14</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#14</guid>         
	  
      <description><![CDATA[Consider the context of this article.

It is in the "writing" section of ALA.

Given this, I don't think "wordiness" is really an issue.

I appreciate the substance, and if that is acheived by 10 line paragraphs this a good thing.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Student Organization Guy</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#15</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#15</guid>         
	  
      <description><![CDATA[I wonder if the practice of writing to one user would still be ideal in instructional type articles. In this I am frequently diffusing and correcting common thoughts and approaches to things that just don't work. "You might have tried...", "You're probably thinking...", etc. Which assumes some level of missunderstanding on the reader. I would rather assume that misunderstanding on an unspecified audience. "Some people have attempted..", "Many think the best way is to..."]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Chris Hester</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#16</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#16</guid>         
	  
      <description><![CDATA[_"I've personally noticed that forum comments vary in certain ways depending on the sex of the article's author."_

I'd be interested to learn what these observations are.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: The Pasty</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#17</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#17</guid>         
	  
      <description><![CDATA[Interesting article, but does anyone really ask questions like these?

"What prompted the author to write this article?
What greater context surrounds this work?"]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Amber Simmons</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#18</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#18</guid>         
	  
      <description><![CDATA[First of all, let me thank yâ€™all for the feedback. Iâ€™d like to address a couple of the concerns raised here, particularly the notion of the piece being too long or wordy.

I think itâ€™s important to keep in mind whom this piece is written for. While I would be thrilled to hear that non-writers got something out of this article, essentially it is written for writers. Most writers tend to be voracious readers; we love words, and we tend to enjoy making en emotional connection with whatever weâ€™re reading (I would even argue that is true of casual readers, too.) Itâ€™s very difficult to achieve the appropriate emotional connection with a subject like this with few words. Although Iâ€™m writing for the web, I donâ€™t believe in sacrificing the human connection with my reader in order to be in line with current web writing standards.

This brings me to my second point. I accept that in todayâ€™s world casual readers donâ€™t read online; they skim.  Historically, the web has been an unfriendly place for readers: pages werenâ€™t designed for ease of reading, content (let alone grammar or style) was a secondary consideration.  Why would anyone invest time in a hostile environment like that? But Iâ€™m looking toward tomorrow.  I see writers and designers working together to make pages easy and inviting to read. I see them building pages that are engaging, accurate, interesting. Iâ€™m looking forward to when readers will read online, and I want to challenge other writers to usher in that era by writing good, engaging content, even if that means itâ€™s long. Writers train their readers, and as the content of the web changes, the way casual readers approach online content will change, too. If we donâ€™t raise the bar higher, the web will never improve. And that, to me, is unacceptable.
]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Amber Simmons</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P10/#19</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#19</guid>         
	  
      <description><![CDATA[Student Organization Guy, you make a good point. It's never good to alienate a reader, especially by making negative assumptions about him. You'll notice in my article I chose to use the pronoun "I" instead of "you". I didn't want to say, "If you're a good writer..." because that could be construed as judgmental and/or derogatory. But by using "I" instead, the reader won't take my words too personally, and can stay attentive without getting his feelings hurt or being insulted.

I do think you can write for a single reader regardless of what you're writing. It isn't necessarily about word choice, but about tone, style, and approach. If you think about it, the vast majority of people who read your work online are sitting at the computer by themselves. Reading is a solitary process anyway. I think we make the process that much more engaging when we acknowledge that and write appropriately.

Do good readers ask questions about greater context and author motivation? Yes, they do. If someone stumbles upon a piece I've written talking about why atheists can't be Christians, a good reader is probably thinking, "Why is she talking about this? Where did this come from?" If my reader doesn't have this information, then my writing is a pointless rant, and the reader can't relate. Good readers want to know where I'm coming from so that they know how to meet me head-on.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#20</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#20</guid>         
	  
      <description><![CDATA[Yeah, I do all the time.  See my previous post for several examples.

There are entire accademic disciplines built around these types of questions.  It would probably do the web design community good to get our collective toes wet in them.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Brad Garrett</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#21</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#21</guid>         
	  
      <description><![CDATA[I for one always like to look up a new word when I read an online article. Gotta expand that vocabulary.

This article seems relevant to me since I've recently begun to read Slate. It's been around forever, but only in the past couple of weeks have I desired to read something more substantive than I find on most "hyper-chunked" news sites and blogs. The fact that an editorial process is involved is one of the good things about Slate, and one of the curses of the blogosphere. At some point I get tired of the grammar mistakes and the aimless rambling.

Also, Amber, I notice that you work for UT Austin. I make frequent use of their page that links to all the college websites. I was part of a university site redesign, and it provided a great hub to see what others were doing and how we could do things better.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#22</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#22</guid>         
	  
      <description><![CDATA[I don't want anyone getting the impression that I think all web designers should get a PhD in comparative lit.  So let me break it down like this.

We've all met people who think anyone can build a website.  We may even have had them as clients or employers.  They surf the web, they make their daily rounds through the favorite dozen sites or so, they know how to use boookmarks and maybe they even know some really advanced stuff like how to subscribe to an RSS feed.

So the only thing that seperates us from them is some basic knowledge in that HTML hooey and they could learn it themselves in an afternoon but their time is way more important than that so they'd rather pay us, since they couldn't find some 16 year old MySpace user to do it for them.

Don't you hate those people?

Now, we all read everyday.  We have our favorite writers, journals, magazines, and newspapers.  If we're really good, we may be able to pull off something really advanced, like figure out an Agatha Christie mystery half way through.

The only thing that seperates us from those professional writers is a college degree in English, which is about as useful as nipples on a boar hog, right?

Isn't that the same attitude that pisses us off daily?  Is it any less assanine when we do it?

The web is driven by content, and a hell of a lot of that content is textual, ie. it has to be written.  And just like we could easily offer advice on how sites like barrygifford.com and joerlansdale.com could be improved, people who understand the fine art of writing may very well have a thing or two to teach us about improving our user experience through better writing.

The "emotional connection" Amber's talking about may sound like a bunch of fluff and fairy dust to people who spend as much time "writing" code for web servers as we do communicating with actual human beings.  But that's just it, in technical fields such as ours its all too easy to loose sight of the human element.

If you don't make an emotional connection with your site visitors, your site is doomed to fail.  That's why good visual design matters, that's why good usability design matters, that's why good branding matters, and that's why good writing matters.

To learn more about the symbiotic relationship between literature and the web, I reccomend sites like Shelley Jackson's "The Body":http://www.altx.com/thebody/body.html and books like Janet Murray's "Hamlet on the Holodeck":http://www.lcc.gatech.edu/~murray/hoh/hoh.html .]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Amber Simmons</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#23</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#23</guid>         
	  
      <description><![CDATA[bq. If you donâ€™t make an emotional connection with your site visitors, your site is doomed to fail. Thatâ€™s why good visual design matters, thatâ€™s why good usability design matters, thatâ€™s why good branding matters, and thatâ€™s why good writing matters.

I think that about nails it. Thanks, Derek; I've really enjoyed your contributions to this discussion.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Amber Simmons</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#24</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#24</guid>         
	  
      <description><![CDATA[oops; screwed that up. :) Maybe it's time to get back to work...]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Danou Nauck</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#25</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#25</guid>         
	  
      <description><![CDATA[and you see, that it*s written, but only for you!
You communicate with noone, but with yourself.
it*s not important to reach someone all the time. 
Sometimes people communicate in their ways, like in this cute website, i just found here.... Never been here bevor..

Donc, je dis: salut!
Je tire mon rÃ©vÃ©rence , et dis A+!
Salut danou

Ecoute: j*ai une squat pours les jeunes europeean! 

Venez, voir l*Wissensnetzwerk fÃ¼r Europa. Von und FÃ¼r Freidenker und KÃ¼nstler! Mehr Sein als $chein http://www.danou.eu

FÃ¼r eine Bessere Welt, lasst uns unser Wissen tauschen! Denn gemeinsam haben wir superviel im Kasten! Wir mÃ¼ssen nur unsere kollektie Intelligenz zusammenbringen und zu einem planetaren Bewusstsein verschmelzen. Dann entsteht aus unserem gemeinsamen Geist ein neues, intelligenteres Geflecht.

:: Danou.eu :: Europas Wissensnetzwerk fÃ¼r Freidenker und Individualisten :: ]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Erin Kissane</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#26</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#26</guid>         
	  
      <description><![CDATA[bq. oops; screwed that up. :) Maybe itâ€™s time to get back to workâ€¦

Formatting repaired. You wacky web people, with your fancy "HTML." :)]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Chris Hester</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#27</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#27</guid>         
	  
      <description><![CDATA[_"But that's just it, in technical fields such as ours its all too easy to loose sight of the human element."_

One very important thing in writing is also to use correct spelling.

Plus... can anyone tell me how to format a quote properly in the comments? The Textile link shows to add "bq" but that makes my reply part of the quote too! I cannot find a way to turn the style off. There must be an easy way...]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#28</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#28</guid>         
	  
      <description><![CDATA[Bickering over spelling is almost as petty as bickering over "wordiness".

bq. Plusâ€¦ can anyone tell me how to format a quote properly in the comments? The Textile link shows to add â€œbqâ€? but that makes my reply part of the quote too! I cannot find a way to turn the style off. There must be an easy wayâ€¦

The blockquote command is "bq. " in front of the block of text to be quoted.  That's bee kwoo dot *space*.  The space is probably what threw you off.  It threw me off at first.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Heidi Panelli</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P20/#29</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#29</guid>         
	  
      <description><![CDATA[Were you writing to just me?

It seemed like it. Nice work :-)

I've just begun a blog and will use your advice to try and engage my readers as you've engaged me.

I look forward to visiting your blog more often...I can see why it's so popular!
]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Britney Simpson</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#30</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#30</guid>         
	  
      <description><![CDATA[I have been running a blog since the start of the year and find that everything you wrote is true but one thing I found also is that using images and live video in posts also draws people to stay longer and surf more pages.But to Petty commentar 28 making sure your spelling and grammer are correct is essintial for keeping your readers going and coming back.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#31</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#31</guid>         
	  
      <description><![CDATA[Posts made here in this dicussion thread and main site content are two very different things in some very important ways.

On the rare occasion I'm made responsible for the content of a site rather than markup, scripting, and design, I always use at least one pass, usually several passes, through a spelling and grammar checking program.  If at all possible, I pass it under the nose of a few trusted friends and/or coworkers for some editing and advice before publication.  I don't want my imperfections to reflect poorly on my clients or whatever the site I happen to be working on at the time is representing.

Here, I'm not representing anyone but myself.  And here I am, warts and all.  As some of you have so kindly pointed out, I can't spell worth poop.  Being an intuitive thinker/learner, I'm far too caught up in the meaning behind the words to get caught up in something as insignifigant as the individual letters.

The more detail oriented of you out there probably see that as a major flaw.  I see your even bothering to notice (in the informal context of this discussion area) as a flaw.

However, I judge people not by their (_perceived_) flaws but by the (_perceived_) relative validity of the meaning they are attempting to convey.

So let's hear something meaningful.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Christian Ziebarth</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#32</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#32</guid>         
	  
      <description><![CDATA[bq. "bee kwoo"


Isn't it: "bee kyoo"?]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Derek Pennycuff</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#33</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#33</guid>         
	  
      <description><![CDATA[You're right.  A diphthong would be more technically correct.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: kenobi kenobi</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#34</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#34</guid>         
	  
      <description><![CDATA[While ignoring the first golden rule about web writing (ie front loading), this article eventually provides some advice on how to 'speak' to readers.

I'm not sure how effectively applying the Long Tail approach to web copy will work if you're writing for a diverse audience, but it'll no doubt prove useful for sites dealing with niche audiences.]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>

    <item>
      <title>Posted by: Amy Marshall</title>
	  
	      <link>http://www.alistapart.com/comments/readerstayawhile/P30/#35</link>
      <guid>http://www.alistapart.com/comments/readerstayawhile/#35</guid>         
	  
      <description><![CDATA[Amber, You note some crucial points to good writing of any kind, even print. I will definitely use your article in my web editing work and trainings... though I will have to cut it short. Like most web readers, I scan content for the most pertinent points. I think you could use some concision (as other commenters have noted)...!]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-05-22T12:00:48+00:00</dc:date>
    </item>


    </channel>
</rss>
