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:analyzing/mapping a process from a doc From:Jay Maechtlen <techwriter -at- laserpubs -dot- com> To:TechWrl list <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 6 May 2016 09:40:23 -0700
I'm not sure of terminology here-
We are publishing our docs on a SharePoint 'wiki', using Kaboodle to
translate from Word to the wiki.
There are some limitations on doc size and complexity, which are not
well defined.
Anyway - we have a few docs that are too long, and we'd like to refactor
or split them up into smaller chunks.
Can anyone suggest tricks/methods to analyze links and structure of a
doc or body of docs, to determine logical groupings and break points?
Thanks
Jay
--
Jay Maechtlen
626 444-5112 office
626 840-8875 cell
www.laserpubs.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com