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.
>I gotta ask: How is it a healthy development
>environment where online help *isn't* part
>of the functional spec from the git go?
That's currently an issue being discussed as we speak :-) OTOH, we're
VERY early in the development, so almost nothing was impacted. It's not
even at the point of having a UI yet.
>Oh yeah, my condolences about having
>to use RH.
Are you kidding? Within 4 hours of walking out of the meeting, I had
proof-of-concept 150 topic help generated from my FrameMaker document in
my management's inbox that I created from the Functional Specs. He was
FLOORED. He showed it to the VP of Development. She was too. I look
great, he looked great, she looked great, and she can conclude her
executive stakeholder presentation on Monday with an "Oh, BTW..wanna see
the help for it?
>See, my comment would be to find out if this
>new feature could be designed so that its use
>was inherently understandable. Failing that,
>embedded just-in-time content is preferable
>to content that user have to take an extra
>step or two to read.
This wasn't a documentation meeting, it was a developer's meeting where
the actual functionality was being discussed....how do check marks get
cleared, populated, etc. I just happen to make a comment...ya had to be