From the Doc Side - All Comments

re: Twitter - Can it Make You a Better Technical Writer?

LarryXA — Sat, 07 Nov 2009 00:30:06 GMT

Thx, this has definitely made my day!

_______________________

wtf

re: Journey from Structred Frame to SharePoint Server Wiki

Fedorcuk — Fri, 06 Nov 2009 06:35:43 GMT

Все нравится. Большое спасибо!

re: The Business Case for Twitter

Escort London — Fri, 06 Nov 2009 00:24:44 GMT

It was certainly interesting for me to read that blog. Thanks for it. I like such topics and everything that is connected to them. I would like to read a bit more soon.

re: The Business Case for Twitter

Mobile blocker — Thu, 05 Nov 2009 18:38:46 GMT

Cool story as for me. I'd like to read something more concerning this topic.

re: Journey from Structred Frame to SharePoint Server Wiki

Gavrik — Thu, 05 Nov 2009 11:02:49 GMT

Мне кажется или автор что-то недоговаривает?

re: The Business Case for Twitter

StephanJade — Wed, 28 Oct 2009 21:31:34 GMT

Great article you got here. I'd like to read something more concerning this topic.

re: How do you explain technical writing to a kid?

Justin Ward — Wed, 11 Mar 2009 18:42:03 GMT

It's tough with kids that age. My oldest (8) thinks my job is to explain how to use computers, because he doesn’t really get the concept of software. My middle child (6) thinks I race bikes for a living.

re: How do you explain technical writing to a kid?

Lindsey Salmony — Tue, 24 Feb 2009 17:42:41 GMT

Great post Lindsey! I especially like that you:

1. Thought about your audience

2. Tailored you message

3. Got the audience involved

Three key elements we should all remember (but sometimes forget) when sending a message.

re: Klingon Technical Writers

JD Hickey — Mon, 15 Sep 2008 17:16:21 GMT

That list would be mine. I wrote it a few years ago and it's made it's way through the Internet. Proud, I am.

And yes, I'm definitely a Star Wars guy, but there's more to spoof in Star Trek.

re: Meet the Team - John

Neal Osti — Tue, 26 Aug 2008 20:05:52 GMT

Sorry, John. I guess I'm one of those "fresh out of college" people. You play basketball at 6 a.m., you're not old! Well, that is pretty early to be getting up, so there could be some debate there. Haha.

re: Why we need technical communicators?

Justin Baden — Thu, 07 Aug 2008 14:31:39 GMT

That's it... I'm off to Toshi Station to pick up a retro magneto reluctance encabulator with logarithmic casings and a turbo flux capacitor.

re: A Great Visual Communication Resource - Worldmapper

Christopher Donahue — Tue, 15 Jul 2008 17:29:37 GMT

At first I thought something was messed up with the images you posted...then I actually read your post and all made sense. I luv maps. Pretty groovy stuff.

re: Meet the Team - Betsy

Justin Baden — Thu, 26 Jun 2008 16:13:32 GMT

Right on! However… Atari 2600 FTW!

BTW – that smurf game video is hilarious. Nice to know that fences and tufts of grass are perilous for smurfs…

re: Wikis Need Some Love (and best practices)

Lindsey Robbins — Thu, 29 May 2008 20:43:27 GMT

Thanks! I think a wiki is a great place for a policy / procedure manual especially if you want a manual that will evolve and grow with an organization.

Which wiki would win? Which wiki would win? Which wiki would win? Well... lol, it really depends on what's available to you and what your resources are.

I always advocate using the resources you already have. For example, we have SharePoint at Blackbaud so I'm learning how to best use that resource for my team. It may not be my favorite tool, but it's a resource we already have. The only thing I will have to do in this scenario is spend more time planning and testing before implementing.

If I had dev resources, I would take base code from a wiki like Media Wiki and use that to customize out the features I need. Then, you get the features you need and nothing you don't. Customized is always nice.

However, if I could use a hosted version on a 3rd party website, I'd always choose Wetpaint. You can control who can see and edit the site. Very feature rich. Easy to use. Very easy to moderate. Also, if you are creating a wiki for the "education" sector, you can create a wiki that is private AND ad free.

And like I mentioned in a previous blog, I'm still looking into the recently release Google Sites. That may be something to look into since we know Google does a great job with usability and integration across apps.

Hope this helps and let me know how the wiki adoption goes!

re: Wikis Need Some Love (and best practices)

Brad Swafford — Wed, 28 May 2008 17:36:11 GMT

Great post. I've been contemplating the use of a wiki for the policy / procedure manual my organization is currently working on. A wiki seems like a no brainer for a document composed mainly of short but related documents.

Can you recommend a good wiki program to start with? If you had to use only one, which wiki would win? (say that three times fast).

Thanks for your tips!