- Use Microsoft Word? Then might want to read this post about using track changes
- Paul Pehrson offers some advice for novice technical communicators
- While you shouldn’t need it, here’s a business case for tech writers to get access to development information
- Kai Weber looks at two words every lone writer should know: later and no
- Learn what a help authoring tool gives you over Drupal
If you missed them, take a read. If you read them, then read them again. You never know what you may have missed!
- Sprinting to a manual
- Larry Kunz answers the question Content strategy for technical communicators: what happens to my doc plan?
- Technical writing and journalism: yes, there are parallels
- Blurring the lines between the Web and the desktop
- Three simple and subtle ways to improve your writing
- Idealism and realism
While out for dinner one night, the subject of conferences came up. We talked a bit about Open Source-specific writing conferences for a while, and things seemed to be left at that.
A couple of months ago, a message from Shaun found its way into my inbox. The subject? Something Shaun was putting together: a three-day conference in Cincinnati focusing on documentation for Open Source. He asked me if I wanted to get involved, and I immediately said Yes!
Shaun’s brainchild is the Open Help Conference. Scheduled for June 3-5, 2011, the conference will bring together people who work on open source or community-based help and help tools.
This isn’t going to be a traditional or even typical technical communication gathering. The Open Help Conference will combine the best elements of a formal conferences, unconferences, and camps. The conference will include traditional presentations, workshops, and open-participation sessions.
While the conference is still in the planning stages, Shaun has a solid group of people working with him. I’m definitely looking forward to this one.
The conference Web site is bare bones at the moment. But keep checking the site for more information about the speakers and the schedule. And if you’re interested in sponsoring the conference, contact Shaun.
A while back, I attended a very interesting seminar given by a couple of consultants in Toronto. The seminar was an overview of various techniques to help kick start your creativity. It was an interesting experience, and I learned a number of interesting techniques.
One of techniques that I really dove into mind mapping. While mind mapping isn’t new to me, in the past I wasn’t really as comfortable as I should have been with it. During the seminar, something clicked and I finally saw how I could use mind mapping to effectively plan my writing. Not just the freelance writing that I do but any kind of writing, including technical writing.
- Some important traits for the content strategist
- Making things hard to read can boost learning
- Thoughts on usability for handheld devices vs. computers
- Using personas during design and documentation
- Six steps for learning difficult subjects quickly. Yes, you can apply these to technical communication (or any other career)