This is an old revision of the document!
UbuntuUsers.de uses a repeating layout/structure on every site. This makes the wiki extremely convenient to use, because sites are built on use cases (Example).
Question to the community: Does anybody have any experience with defining dokuwiki site templates?
The new blog should be part of dokuwiki, so that there is only one content base for the global search on the X2Go site.
Question to the community: Has anyone some experience with the blog plugin?
Alternatively we could use the announcement mailing list for this purpose (RSS reader on start page)
Index/start pages should be available for every namespace. Those start pages should technically all be the same. Those pages should definetely be plugin-independent (i.e. not using any dokuwiki plugin).
Extended edit functions such as renaming or deleting a page.
Find orphan pages and wanted pages.
Inserts TOC in the place you specify in your Wiki page.
Inserts a ToDo button into the editor toolbar
Supports the easy setup of a multi-language wiki.
Use a CAPTCHA challenge to protect DokuWiki against automated spam.
Displays a maintenance message on all pages to notify of upcoming downtime, can also disable editing for all users.
Should changes be allowed to take place immediately after pressing the “save” button?
Survey:
Nobody should delete pages or articles of others without informing the community or author.
Not tested or poorly tested setups should definately be marked as “suggestion” or “untested setup”.
There was a lot of criticism regarding “only to offer a wiki” as documentation source. People are really looking for downloadable and readable installation guidelines. If they are searching on the net, they normally are looking for PDF-files.
A lot of the contributing people would like to have a more wiki like page template. The logo bar should be removed and the layout should be spread over the whole page. The CSS file should not modify the major tags like h1, h2, P or SPAN - this should be in the hand of the user (configuration of the client/Browser).
—-