I would have fun being the docu admin if you don't already have a person in mind for that job.
But whoever will do that job, he should probably post a "call for documentation" in this forum?! Maybe some people already have some work done, something they can submit - maybe just a quickstart guide or a checklist or anything. I might get done with a "backend user manual" this week myself.
I think we should start collecting what we have. There has to be something out there already.
Great! What could be the rules? Clear language, keep it short and simple, screenshots should only show what is necessary (not the entire screen) and so on?
A template sounds good. I think, submission should be in either of these formats: RTF/RTFD, SXW and/or PDF. I could offer PDF conversion for those who can't or don't want to do that. Or do you think an HTML version on phpwcms.de would also or alternatively a good idea?
If that's easily done, go ahead... but I don't think you need to put that much effort into it. I think it's not a problem to manually copy&paste a given Word file into phpWCMS so it is available right on the phpwcms.de-documentation site.
What are your thoughts about the documentation rules, though? And when do you think you find the time to design those template(s)?
why not doing documentation with docbook-xml?
so the rules where given by the dtd and we could easily transform it into web (html) and print (rtf, pdf)?
when i worked with docbook, it always used XMLmind XML Editor.
it is java based, so it should work on other platforms too.
but i just worked with the windows version.
maybe someone has also tried this editor? and on another platform than windows?
Interesting idea, jmeyknecht, but I agree with Oliver that it should be as simple as opening a standard text editor for the folks who want to write some documentation otherwise the base for contributing documents will be too small.
So, let's think about what rules should apply for people who want to write documentation. As I said, I will have to write some form of "backend manual" this week, so it would help me if I could already do it in a form I can later-on publish on the new phpWCMS-Website.
hehe, I'm trying to implement docbook into OpenOffice.org
maybe this solves our problem of finding rules.
in my opinion it's better to have rules defines by programs, because they are hard to break. the disadvantage of using Word or OpenOffice without program defined rules is, that people will ignore them after a certain time. i hope this won't happen to this project ;-)