Better documentation/ using the wiki
#3
So what has a "real" wiki got what the current one doesn't have?

I know of two major problems that the current wiki has: it's hopelessly outdated, and its start page is constantly being defaced by spambots. Will creating a "real" wiki fix either of these problems?

There may be a different approach, taken by the "book" subproject - it's not exactly a wiki, but rather a github repo that has individual pages in it, and it is then being compiled into a web form. By using GitHub, it prevents the spambot defacement; on the other hand, it's even worse off than the wiki on the outdatedness. Also what I personally don't like about it is the lack of documentation on how to actually add content there, properly.

A similar approach would be to use a normal static website, with all the pages saved in a GitHub repository. This would have the advantage of easy editing, but the disadvantages of needing to know HTML and CSS in order to edit it, and doing things the hard way - if you wanted to add something to a sidebar menu, you'd have to edit ALL the pages.
Reply
Thanks given by:


Messages In This Thread
RE: Better documentation/ using the wiki - by xoft - 10-26-2014, 06:33 PM



Users browsing this thread: 2 Guest(s)