Showing posts with label web writing. Show all posts
Showing posts with label web writing. Show all posts

Thursday, April 2, 2009

hot tip options

Optional ‘standards’ task
Think about any differences between the articles: for example, is the advice in Nielsen’s paper -- written in 1997 – still current?

I believe all the three sites are basically giving the same advise for writing for the web.
  1. start with your best information first, give the critical data first and they might read on if they need to.
  2. structure the text so it can be quickly scanned (read).
  3. don't write too much, people don't have time to read epic tales.
However, some differences do start to appear on Jerz site which I believe is due to the natural progression of the web—improvments in graphical user interface and web applications. You just need to look at Nielsen's site to compare how web site design has progressed due to the increased bandwith and more powerful computer processing. Nielsen's site has a 90s feel about it, a garish colour scheme and a design that reflects the web from the past.
Jerz has included some general design advise for page development that is aimed at reducing reader interference by not including distracting page elements well as breif writting methods. Nielson has included information regarding low literacy that crosses over the same boundary.

However, read between the lines, the advise on all three sites are still current. It just shows that when researching, you need to take in multiple view points and get a second opinion to achieve a balanced web site.

Anyway, this is getting too dry again, where's the jam?

Tuesday, March 31, 2009

Five hot tips—writing for the web

Hot toast with yummy stuff!

I have read the suggested information on "writing for the web" and assimilated the data and have compiled MY tips for writing for the web. My tips are a combination of the information from these sites and from my experience in using the web, what I like and how I perceive useful information. In attempting to complete this post I have written and rewritten it a few times, but it keeps coming out so dry, like a piece of "old toast" (Goetzman, Hanks, Zwick & Vardalos 2002), but I want it with butter and raspberry jam. So here are the:

five hot tips:
five tips:
five
Six toastie soldiers with butter and raspberry jam:
  1. structured text—use easy to read text that can be quickly scanned, like the leading points of this text so readers can jump to the information they require. (Dennis, 2008)
  2. best foot forward—give the reader the most useful information first, if they like what they see or want more information they keep reading. Otherwise, like me, I'll bugger off and find something better—lifes too short and too quick these days to hang around. When do we want the information—we want it now! (Ibid)
  3. low word count17% users of the web only view a page is 4.4sec (Nielsen, 2008). Writing for the web you need to get the message across without beating about the bush, no procrastinating, be precise in the use of language, be economical with your words, a stitch time time saves something but not this para. "cut the fluff" (Nielsen, 2007) blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. It's all Greek to me!
  4. low literacy level—write to "6th grade" (Nielsen, 2005) level, even the highly literate people appreciate the simple things in life.
  5. straight to the pointcut the crap, don't get to flowery or overly descriptive with the words, given them the facts without the hype. (Nielsen, 1997)
  6. chunkingwrite like your talking to a person you have never met before. Give them all the essential facts of the article in one place, don't let them gather the information from several pages because they will probably miss some vital point. This style may result in some repetitive writing on other pages of similar topics but grouping to information so it can be accessed quickly will save frustration. (Horton, 2001)
As I was skimming through the "Writing for Web" on the useit.com site when I remembered my earlier post about this topic on 7 March, see Reflections on Week 1 Point 2, the fact I usually only browse web pages. It confirms that I'm just a statistic.

The odd thing about writing for the web according to Dartmouth College is you need to take into account if people are going to print the web page and read it offline. My experience this the printed pages tend to be very disjointed and you usually get a lot of extra crap on the side (side bar menus and adds) so I don't do this very often. My extra bit of toastie advise would be, if you expect people to print it, you should supply a fully formatted print version in PDF to download.
Don't just repurpose the text, rewrite it for the approiate media. Maybe that should be points 7.


Reference:
Nielsen, J. (2006). F-Shaped Pattern For Reading Web Content. http://www.useit.com/alertbox/reading_pattern.html

Nielsen, J. (2007). Blah-Blah Text: Keep, Cut, or Kill?. Retrieved March 31, 2009, from http://www.useit.com/alertbox/intro-text.html


Nielsen, J. (2005). Lower-Literacy Users. Retrieved March 31, 2009, from http://www.useit.com/alertbox/20050314.html

Nielsen, J. (2008). How Little Do Users Read? Retrieved March 31, 2009, from http://www.useit.com/alertbox/percent-text-read.html

Nielsen, J. (1997). How Users Read on the Web. Retrieved March 31, 2009, from http://www.useit.com/alertbox/9710a.html

Horton, S. (2001). Writing for the Web. Retrieved April 1, 2009 from http://www.dartmouth.edu/~webteach/articles/text.html

Dennis, J. (2008). Top 5 Web Conventions (Writing and Design). Retreived April 1, 2009, from http://jerz.setonhill.edu/writing/e-text/conventions.htm

Goetzman, D. & Hanks, T. (Producers), & Zwick, J. (Director) & Vardalos, N. (Writer) My Big Fat Greek Wedding[Motion picture]. United States: Gold Circle Films

Get a second opinion

Bugger, has all this time been wasted of time?

After reading a few posts on the uni Blackboard by Peter Fletcher and taking his advise to have a read of the great articles on Dave Carr's blog, I became a bit concerned of the way I have approached my studies. This is the the my first unit of study after returning to Uni from a break of ten years and I think I have confused speed with quality—trying to keep up with the Jones to finish the modules as quickly as possible. Reading Dave's blog has been a great eye opener to see that doing just a bit of extra research adds validity to his argument—I think I'll take a leaf out of his book and do the same. Slowly, slowly catch a monkey! This type of writing was also advised in Rebecca Bloods Book, The Weblog Handbook but I can't quote from it because I have already sent it back to the library.

As for a waste of time—no I don't think so, I'm taking it as a learning experience!

So the moral of the story is, I may not blog as often but try to put more convincing content into it.

Saturday, March 28, 2009

How to write blog post

Before I get into the details of the next question I would just like to state my views on writing for blogs. I have read Rebecca Blood's book, The Weblog Handbook.
"Write each entry as if it could not be changed: add to, but do not rewrite or delete, any entry."(Blood 2002, p. 118)

As much as I respect Rebecca's experience, I will reserve the right to edit and rewrite as necessary to make my point clear and concise—I know I do sometimes have a rant, I will uphold her views about not deleting entries.

If you would like to read more about Rebecca, visit her site.

anyway, that's all.

Reference
Blood, R (2002). The Weblog Handbook: Practical Advice on Creating and Maintaining Your Blog. Cambridge: Perseus Publishing.