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.
Maria (maria -at- msd -dot- measurex -dot- com) says:
> I agree with Bonni. Presentation and content are not separate
> issues. I designed the layouts for my manuals to fit the content. I
> organize my content to fit the layouts that I designed to fit the
> content...
Tammy (Tammy_Williams -at- OCLC -dot- ORG) also says:
> There has been a good deal of discussion about whether writing and
> presentation (formatting) go hand-in-hand. I, like Bonni Graham,
> agree that they can go hand-in-hand. I'll even take it a step
> further--I think it's crucial that they go hand-in-hand.
I think we're working with some inaccurate assumptions here;
presentation and content *are* two distinct issues, but they are
issues that must (as with many other issues) be considered in relation
to each other in constructing a document.
The idea behind SGML is to separate the two issues as much as
possible, to work with each individually, develop them as far as you
can - THEN deliberately brings them together. Currently, both issues
are interwoven so densely that you can't conceptually separate them,
thus making the task of comprehending and crafting the document more
confusing. SGML is not an end, but a means.
