TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: When is it too much information? From:Stuart Burnfield <slb -at- westnet -dot- com -dot- au> To:Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 19 Feb 2013 13:59:04 +0800 (WST)
> Another question I'm always asking myself is, when is it
> too much information for one topic?
> When should a topic that is chock full of goodies be split
> into two topics?
When you're mixing a substantial amount of information of different types (concept, reference, task, troubleshooting, ...). When writing a procedure it's tempting to lump in a lot of conceptual stuff "just in case they don't know that - it would be handy to say it here". The main thread of the task gets lost under all the digressions. It's better to explain the terms and background concepts elsewhere, and provide 'related topics' links at the end of the procedure.
It's like giving visitors directions to go shopping - just tell them how to get there. Alternate routes, traffic reports, local history and nearby tourist hotspots might all be interesting and useful, but it's better to give them that information in another form when it's needed.
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.