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.
Are you asking whether it's a good idea to format a procedure (ie. a series of numbered steps that you follow to perform a task) as a table?
If so, I can't think of any advantages.
Aside from the obvious disadvantage of having to manually number each step, putting instructions in a grid form creates a dense block of information, so its harder to visually track/keep your place within the block of information.
From: techwr-l-bounces+lynne -dot- wright=tiburoninc -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lynne -dot- wright=tiburoninc -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Sean
Sent: Thursday, October 24, 2013 9:45 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Using tables for content
So, whilst I search the archives, can we have a live discussion on the pros and cons of using tables for tech writing content. Consider a traditional procedure that uses step: in the left column, the action, and in the right column, the result. It seems, for Word, each row needs to be numbered manually.
Conversely, there is standard ordered list approach without using a table.
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.