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'm in no way trying to be obstinate or confrontational, simply presenting a
different point of view.
For example, I've created a few different sites using RoboHelp HTML and
WebHelp output. Seems to work well for anything that you need to present
similar to what a reference book would contain. For example, I had one site
that served as a repository for local lunch places. I would regularly pick
up menus and scan them into images. Then pop them into a RoboHelp project
and index them by classification (Mexican, Asian, Italian, etc./Price
range/Whatnot)
Then there were other sites that held information used as job aids and
reference systems. Even had scripts that call center employees would read to
customers while troubleshooting calls.
I've often enjoyed finding other ways than those traditionally accepted for
doing things. I do see what you mean with the Swiss Army knife/saw
connection, but what if the person facing the situation is tremendously
comfortable with a Swiss Army knife, but has no electricity for operating a
circular saw and can produce something regarded as nearly flawless and even
creative using the knife? Likewise, if a person is totally familiar with
something like Flare or RoboHelp and is quite happy with what the output
looks like and how it operates, does it make it any less a web site?
I do agree that it shouldn't be used willy nilly and for all sites. Only for
those where it can help with what it brings to the table. Sometimes that's
in the form of a help system and at other times it may be totally suitable
for whatever need the person creating it sees.
That could be true, but when someone says "website" I don't see Help. I
see Help as a component of some websites. Seems to me that developing and
maintaining a "website" using a Help tool is like trying to cut a board
using a Swiss Army knife. It will work, but why not use a saw? If you're
maintaining a Help attached to a website, then that's different.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
