[ilikenwf]

I'm not a fan of doku myself...I like mediawiki for that sort of thing...

But, scotthomas is a pro doc writer, and having something that we can package as html and/or a pdf in the releases, adapt to manpages, and also have online would be nice.

[rsjtdrjgfuzkfg]

(03-13-2012, 01:07 PM)ilikenwf Wrote: I'm not a fan of doku myself...I like mediawiki for that sort of thing...

But, scotthomas is a pro doc writer, and having something that we can package as html and/or a pdf in the releases, adapt to manpages, and also have online would be nice.

Wouldn't it be possible to export from a wiki (maybe we need a new system for the wiki?!) as HTML or PDF?
So we have both the changelog and ease of a wiki, and a nice documentation.

If scotthomas would have recommended something, I agree we should take what he wants, as we're no pro doc writers. He sounded to me that the platform doesn't really matter...

Anyway I'm fine with setting up yet another service, but probably not another wiki (two wiki-links in the header?)...

[freaktechnik]

(03-13-2012, 11:36 PM)rsjtdrjgfuzkfg Wrote: Anyway I'm fine with setting up yet another service, but probably not another wiki (two wiki-links in the header?)...

Developer link and Help link or something?

[rsjtdrjgfuzkfg]

(03-14-2012, 04:26 AM)freaktechnik Wrote:

(03-13-2012, 11:36 PM)rsjtdrjgfuzkfg Wrote: Anyway I'm fine with setting up yet another service, but probably not another wiki (two wiki-links in the header?)...

Developer link and Help link or something?

Wiki is currently more than developer, it's also about upcoming features and stuff (not help either). If we need it we can do a wiki called Help, but I'd prefer not to have yet another system.

[scotthomas]

Everyone seems to be agreeing that having HTML/PDF docs is good for the end-users, which is good for the project.

If you guys want to keep everything in one place, exporting to HTML and PDF can be done from Dokuwiki. As I understand it, this is done via third-party plugins. I don't know if anyone has seen the output quality, though. Perhaps a test-run to see whether it's a viable option?

As for having two links on the site and content in the wiki that isn't documentation; I think end-users will appreciate not having to navigate through developer content. The 'works-in-progress', 'coming features' and 'feature requests', could find a home in the end-user docs; either in Release Notes or in dedicated sections of the user doc.