User Tools

Site Tools


doc:wiki:discussion

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:wiki:discussion [2012/02/20 17:41]
h1
doc:wiki:discussion [2012/03/06 22:11]
tan [Documentation vs. Wiki]
Line 2: Line 2:
 ===== Good Content Examples on the Net ===== ===== Good Content Examples on the Net =====
 ==== UbuntuUsers.de ==== ==== UbuntuUsers.de ====
-UbuntuUsers.de uses a repeating layout/structure on every site. This makes it extreamly convinient to use this wiki, because sites are build on use cases ([[http://wiki.ubuntuusers.de/NX|Example]]). Has anybody some experience defining dokuwiki site-templates?+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 ([[http://wiki.ubuntuusers.de/NX|Example]]).  
 + 
 +===== ===== 
 + 
 +**Question to the community:** Does anybody have any experience with defining dokuwiki site templates? 
 + 
 +===== Templates ===== 
 +[[:doc:wiki:discussion:template|Example template used for discussion]]
  
 ===== Blog ===== ===== Blog =====
-The new blog should be part of dokuwiki, so that there is only one content base for the global search on the x2go site. Has anybody some experience with the blog plugin? Alternatively we could use the announcement group for this purpose (rss reader on startpage)+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)
  
 ---- ----
Line 11: Line 23:
 ====== Structure ====== ====== Structure ======
 ===== Index Sites ===== ===== Index Sites =====
-Index/start pages should be available on every namespace. Those startpages should technically all the same. ([[heinz-m.graesing@obviously-nice.de|Heinz]]don't think the graphical menues are a good idea. I would prefer some really clean index site with only one information per line. Those sites should definately plugin independend.+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). 
 + 
 +  * [ [[heinz-m.graesing@obviously-nice.de|Heinz-M. Graesing]] ] I don't think the graphical menues are a good idea. I would prefer some really clean index page with only one information per line.
  
 ---- ----
Line 18: Line 32:
 ===== Needed Plugins ===== ===== Needed Plugins =====
 ==== editx ==== ==== editx ====
-Extended edit functions such as renaming or deleting a page+Extended edit functions such as renaming or deleting a page.
 ==== orphanswanted ==== ==== orphanswanted ====
-Find orphan pages and wanted pages+Find orphan pages and wanted pages.
 ==== toc ==== ==== toc ====
-Inserts TOC in the place you specified in your Wiki page+Inserts TOC in the place you specify in your Wiki page.
 ==== todo ==== ==== todo ====
 Inserts a ToDo button into the editor toolbar Inserts a ToDo button into the editor toolbar
Line 29: Line 43:
  
 ===== No longer required ===== ===== No longer required =====
-===== captcha ===== +==== captcha ==== 
-Use a CAPTCHA challenge to protect DokuWiki against automated spam+Use a CAPTCHA challenge to protect DokuWiki against automated spam.
  
-===== maintenancemessage =====+==== maintenancemessage ====
 Displays a maintenance message on all pages to notify of upcoming downtime, can also disable editing for all users. Displays a maintenance message on all pages to notify of upcoming downtime, can also disable editing for all users.
  
 ====== Access/Restrictions ====== ====== Access/Restrictions ======
 ===== Realtime Contribution ===== ===== Realtime Contribution =====
 +
 Should changes be allowed to take place immediately after pressing the "save" button?  Should changes be allowed to take place immediately after pressing the "save" button? 
 +
 +**Survey:**
 +
 +  * [ [[mike.gabriel@das-netzwerkteam.de|Mike Gabriel]] ] +1 (yes, and only with commit mails of recent changes to the x2go-commits mailing list)
 +  * [ [[teranders@gmail.com|Terje Andersen]] ] yes, this is a wiki; if something goes wrong revert to earlier versions. Can we get some sorts of conclusion on where to send mail with info regarding changes made ?
  
 ---- ----
Line 43: Line 63:
 ====== Code Of Ethics ====== ====== Code Of Ethics ======
 ===== Do Not Delete Work of Others ===== ===== Do Not Delete Work of Others =====
-Nobody should delete sites or article of others without informing the community or author. In my eyes ([[heinz-m.graesing@obviously-nice.de|Heinz]]) this should be done by using a documentation mailing list+Nobody should delete pages or articles of others without informing the community or author. 
  
-===== Only Tested Articles ===== +  * [ [[heinz-m.graesing@obviously-nice.de|Heinz-Markus Graesing ]] ] This should be done by using a documentation mailing list. 
-Not tested or poorly tested setups should definately marked as "suggestion" or "untested setup".+  * [ [[mike.gabriel@das-netzwerkteam.de|Mike Gabriel]] ] I would rather prefer one of the already existing channels (x2go-dev or x2go-user ML)
  
 +
 +===== Only Tested Articles =====
 +Not tested or poorly tested setups should definately be marked as "suggestion" or "untested setup".
 +  *  [ [[teranders@gmail.com|Terje Andersen]] ] yes, sounds like a good a idea. I think we should go for the "untested setup" of those two proposed, and maybe use the "Warning" sign in red, as seen on the template example page?
 ---- ----
  
Line 53: Line 77:
 ====== Criticism ====== ====== Criticism ======
 ===== Documentation vs. Wiki ===== ===== Documentation vs. Wiki =====
-There was a lot of criticism regarding "only to offer a wiki" as documentation source. People are really looking for downloadable and readable installation guidlines. If they are searching on the net, they normally are looking for PDF files.+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. 
 + 
 +  * [ [[mike.gabriel@das-netzwerkteam.de|Mike Gabriel]] ] Use dokuwiki offline plugin, find a doku2pdf (or docbook XML or ...) converter 
 +  *  [ [[Teranders@gmail.com|Terje Andersen]] ] We could present a button for creating the pdf as Mike here suggests. Additionally we could regularly produce a snapshot of the wiki which is further tailored (handcrafted pdf) for different readers, like system administrators, users, developers and so forth. I would like us to start "small" with the first suggestion though ;-)
  
 ===== Wiki Layout ===== ===== Wiki Layout =====
-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). 
  
 +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).
  
 +  * [ [[bd.dali@gmail.com|Daniel Lindgren]] ] I suggest that X2Go's wiki is changed to use either the default DokuWiki template (as seen on  [[http://www.dokuwiki.org/dokuwiki|www.dokuwiki.org]]) or, if sidebar(s) is wanted, [[http://www.dokuwiki.org/template:arctic|Arctic template]].
 +  * [ [[Teranders@gmail.com|Terje Andersen]] ] I agree with Daniel here, of the two mentioned here I would choose the Arctic theme. 
 ---- ----
- 
-