In my copious spare time I have been known to design and build websites. The first website I ever built was for the first company I worked for, back in 1996, so I’ve been at it a while.

However it’s only been the past couple of years that I’ve started to get some larger clients with grander ideas, and that has meant getting a bit more organised. As such I now have a standard questionnaire that I ask all prospective clients to fill in, a standard design proposal document which I use to present back my ideas based on the answers to the questionnaire, and I have a nice little area of my PC which is dedicated to building websites.

The key part of which is XAMPP.

I discovered this marvellous application about 3 years ago, and if you are building websites, or installing and customising anything that requires MySQL and PHP then you must give it a look.

Many people know from their own experience that it’s not easy to install an Apache web server and it gets harder if you want to add MySQL, PHP and Perl.

XAMPP is an easy to install Apache distribution containing MySQL, PHP and Perl. XAMPP is really very easy to install and to use – just download, extract and start.

It really is that simple. Once you’ve downloaded it, start up the Control Panel, start Apache and MySQL, then head to http://localhost. Done!

A lot of my web design work is creating custom themes based around WordPress, sometimes it is just a look and feel but more often than not custom code is required. Now, rather than having to upload a file to a test web server somewhere, I can work locally on the php files, and just refresh the browser to see my changes. Much faster.

XAMPP is one of those applications that, after you’ve used it once you think “how the hell did I manage without this!”.

Given that a lot of technical communicators are looking towards other distribution models (blogs, Wikis and so on), then XAMPP is an easy (and free) way to get a test system setup, allowing you to run short proof of concept projects. I hope you find it as useful as I do.

It’s safe to say that I’m fully hooked into the Web 2.0 world. I manage my email, calendar and task list online, as well as write and share the occasional document. I blog (in three places), I twitter, and I follow a wide swathe of information via RSS feeds. If the internet disappeared overnight I’d be lost, for any time I think ‘information’ I think internet, I don’t think book, or library, or even online help. I think internet.

This is even more prevalent when I’m looking for a solution, an answer to my current burning issue. At that point I’m looking for information from my peers, from other users or anyone else who has had, and solved, a similar problem, and nine times out of ten I’ll turn to the internet to search for that information.

Whilst such answers can be hard to track down, it feels productive to be searching for the specific answer to my specific issue, even if that takes some time and effort on my part. Once I’ve found an answer I’ll usually do a little bit of double checking – perhaps others have added a comment to say that it worked for them – and then I’m happy to accept that it is correct, knowing that if it’s not I can always head back to Google and start again. Caveats apply here, of course, depending on the severity of the issue I’m dealing with.

My point is that I freely trust the information I find based on some cursory checks, I am fully hooked into the Web 2.0 world and believe in the wisdom of the crowd (thankfully I have evidence of this as well, it’s not all hearsay).

Providing information and answers is a key part of our job as technical communicators but I am concerned that my view of the information world and how I use it may be tainting my thoughts. Do the people who use the information we produce really want to ‘just google’ for information? Am I projecting the way I think and work onto the people who use our documentation?

The obvious answer is to ask those people, and I’m in the fairly lucky position that I can do just that. A large portion of our documentation is used by our own staff, so I have direct access to my audience. So, obviously, I should just ask them: “How would you like to access the documentation?”

But I think that’s the wrong question.

Whilst it will be useful to hear the answers to that question, it is far too open ended and, to repeat an old adage, ‘the customer doesn’t always know what the customer wants’. Instead I need to figure out what the most common usage scenario is and work from that, before presenting a limited set of choices from which the audience can make an informed decision.

One thing is certain, the way I access information, the way I think about how information is structured and presented, from my professional background and my knowledge of some of the information design theories that are in use, is very different from the way I use information in my day to day life. The more I find myself leaning towards more ad-hoc, random and casual sources of information, the more I begin to wonder if the world of the professionally written and presented technical communications needs to change tack and find a comfortable middle ground, embracing all that is good about the web 2.0 internet.

Social media works because it is based on people and the availability of information (and metadata about that information). It seems all too obvious that the world of technical communications needs to make bigger strides in that direction. Many technical writers have started that journey, and whilst it means yet another set of skills that you’ll need to learn, ultimately it means that the technical information you produce will be more valuable in the longer term.

As well as my full-time job, in my spare time I also design and build websites. It’s something which fits well with my skillset as a technical communicator, and allows me an insight into the world of development as well and has mirrored my career every step of the way.

The first company I worked for sent me on a training course to learn how to create web pages and, since then (13 years ago), I’ve continued to follow the trends and techniques involved. I’ve been through using tables for layout, to the introduction of frames, the launch of Internet Explorer and the first release of CSS.

The parallels between the theories of technical communications and those of web design are very similar, the key aim is to keep the audience in mind at all times. The way you structure and present the information is also important, as is a sense of usability of the content itself.

I’ve been lucky enough to have a fairly constant stream of web design work, largely by word of mouth, and have just finished chatting with another potential client. Part of my approach is to ask to have a questionnaire filled in, largely to help me understand the requirements for the website, as well as to have something to focus the initial conversations around.

Two of those questions are:

1. Who will be using your website? What is the intended/current audience?
2. Does your current website meet the needs of your audience? If not, why not?

Which, as I’m sure many of you will already have realised, is exactly the kind of questions we, as technical communicators, should be asking ourselves on a regular basis.

I try and follow as many technical writing blogs as I can but beyond the dedicated blogs there are other good sources of information and ideas out there. Finding these additional articles can be tricky as they can be found in a huge number of different sources.

To help with this Tom Johnson set up Writer River as a way to allow anyone (with an account) to post links to interesting blog posts and articles. The website has been running for a whlie now and continues to provide links to useful and topical articles.

I monitor an RSS feed of the website and whilst that is adequate it does mean that I can go a week or more without checking which can lead to a build of too many links to check. That usually means I skim the link titles rather than click through them all and the likelihood is that I’ve missed something that may have been useful.

So I’m delighted to hear that Writer River now has an auto-updating Twitter feed. Every link posted on Writer River will be pinged over to Twitter, and as I’m following Writer River on Twitter, I’ll see the links as they are added, increasing the chances of me taking a few minutes to click through to the linked website.

Time will tell but this is either a great use of social networking tools, allowing me to keep bang up to date and probably meaning I won’t skip any links, or another challenge to my time keeping, a quick check of Twitter during a context-switch* moment at work may lead to a longer break than I had intended?

We’ll see but, as ever, Tom continues to push his ideas forward to the benefit of us all.

I dropped Tom an email about Writer River last week, and he alluded to some of the issues he mentions in his post in his reply. Little did I know that Writer River was soon to be hacked!

I love the idea behind the website though, so it’s good to see Tom is still keen on pushing things forward. If you previously registered I’d urge you to go back and register on the new version of the website. The premise is the same, a website which will collate the best Technical Communications stories and blog posts.

Head over to Writer River, the more people who sign up and join in, the better it will become.

A quick welcome to anyone visiting from the ISTC Communicator magazine. I feel a little spoiled getting two mentions in subsequent pages (10 & 12 if you are wondering) but I’m not really complaining.

Over the past year or so I’ve definitely got the feeling that the ISTC is changing, and it certainly feels like a more modern and dynamic organisation than it has seemed to be in the past. Perhaps that’s natural, but it’s amazing how little things like a redesign magazine and newsletter, and hopefully a new design for the website, can refocus the energies of those involved.

Anyway, thanks for dropping by, there are plenty of links and opinions to be found in the archives (scroll down a bit, they are on the right), and here are a few of the more popular posts:

• Everything is Connected
• DITA is not the answer
• Technical Writing evolved

Or perhaps you just want to download the RSS feeds.

Question: How much investment does Web 2.0 really take?

Answer: A lot.

I’ve seen the same quote repeated in several different locations recently. It was uttered by O’Reilly and has the twin benefits of being short, quantitative, and seemingly true. As I’m in the midst of setting up a new website for our company, focussed on the developer community that already exists (in number if not in action), it was a phrase that made me realise just how much work lay ahead of me.

Part of the work I’m doing is to replace the existing website, rebranding and updating it in one fell swoop. Most of the work is largely concerned with uploading documents and files to make sure that everything that is currently available will be available from the new website, but there are already thoughts around how we can use the website to drive further adoption, innovation and so on.

And, of course, because Web 2.0 is the phrase of the moment there are quite a few eyes waiting to see what will appear.

One thing I have realised, and I’m still winning over minds on this, is that most of what Web 2.0 is about isn’t the technology and, whilst this may seem like an odd statement, it’s not really about the people who use the website, not initially at any rate. No, for me the big issues that surround Web 2.0 adoption by corporations are centred around information and transparency, about being part of the conversation.

That last sentence is important. You cannot drive a conversation on the internet, you can start it, you can contribute to it, but once you’ve set it free you no longer have control over it. All you can do is hang in for the ride, and that’s where transparency kicks in. As the numbers of conversations grow the easier they are to manage if you are open and upfront. For, as Tim O’Reilly said of Web 2.0 (and I’m paraphrasing here):

“The more people that use it, the more uses we’ll find”

So, just as the benefits of having a more connected community of users will increase what they can acheive both individually and collectively, so to do the number of pitfalls awaiting the cumbersome.

What this confirms is that most of the challenges around setting up a community website are largely about the individuals and being able to reach out to them, to be able to consistently engage them and ultimately offer them benefits for their time and input.

Which doesn’t half take a lot of work.