Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Software for creating documentation
0 views
Skip to first unread message
D.M. Procida
Nov 27, 2009, 1:13:34 PM11/27/09
to
What would you recommend for producing a user-guide (print and/or web)
for web-based software? I know that there are applications intended to
make this process easier, but I've never used any.
for web-based software? I know that there are applications intended to
make this process easier, but I've never used any.
Daniele
--
Roland TB-303: http://cgi.ebay.co.uk/?ViewItem&item=220516703621
Roland TR-606: http://cgi.ebay.co.uk/?ViewItem&item=220516716343
Both as new, boxed, immaculate condition
Justin C
Nov 28, 2009, 9:52:29 AM11/28/09
to
In article <1j9uqj1.buxvck101gqt9N%real-not-anti...@apple-juice.co.uk>, D.M. Procida wrote:
> What would you recommend for producing a user-guide (print and/or web)
> for web-based software? I know that there are applications intended to
> make this process easier, but I've never used any.
> What would you recommend for producing a user-guide (print and/or web)
> for web-based software? I know that there are applications intended to
> make this process easier, but I've never used any.
html and grab. That's my preference. If you want it to look good in
print then LaTeX.
Justin.
--
Justin C, by the sea.
Dr Geoff Hone
Nov 30, 2009, 1:05:17 PM11/30/09
to
From past experience (with some specialised task analysis software)
then HTML is the easy way to go.
Any good HTML editor will do the job, and there is then the advantage
that the user can print all the documentation off and also use the
on-screen version as a quick-finder.
Like most things, we found that a fair bit of pre-planning was needed
to make sure that all the possibilities were covered, followed by a
good long test session.
I have heard the view that it is better to write the manual first and
then develop the software, , but we were committed to the RAD
approach.
then HTML is the easy way to go.
Any good HTML editor will do the job, and there is then the advantage
that the user can print all the documentation off and also use the
on-screen version as a quick-finder.
Like most things, we found that a fair bit of pre-planning was needed
to make sure that all the possibilities were covered, followed by a
good long test session.
I have heard the view that it is better to write the manual first and
then develop the software, , but we were committed to the RAD
approach.
SM
Nov 30, 2009, 5:55:54 PM11/30/09
to
D.M. Procida <real-not-anti...@apple-juice.co.uk> wrote:
> What would you recommend for producing a user-guide (print and/or web)
> for web-based software? I know that there are applications intended to
> make this process easier, but I've never used any.
You could take a look at Tinderbox. Matt Neuberg praised it for
producing documentation:
<http://macdevcenter.com/pub/a/mac/2004/03/30/online_help.html>
Stuart
--
cut that out to reply
0 new messages