kiss-community / kisscommunity.org Goto Github PK

We have so many packages in the community repository that it's getting hard to keep track of them. Not to mention that some of them require specific post-install steps to be taken by the user which currently are not really documented anywhere.

I've previously tried starting a wiki in this repository's Wiki tab, but I don't think hosting it on Github is a good idea for multiple reasons:

• Discoverability

  It's very difficult to find out about the existence wiki since it's hidden in a small tab in the website's repository, which not many people will ever visit. Even if there's a link added to the main page of kisscommunity.org about the wiki, it will mean redirecting the user to a different website which is a bad user experience.

• Github's wiki system sucks

  As of the writing of this issue, there are currently 401 packages in the community repository. While Github's wiki system might be fine for small wikis with only a handful of pages, Github wikis tend to be slow to navigate and cumbersome with a large number of pages.

• Hosting a separate wiki service like MediaWiki allows for more control

  Hosting our own wiki service would allow a much higher degree of control over who edits pages and how the wiki is set up in general. Furthermore, it has the potential to integrate perfectly with the rest of the community website and would give the opportunity of people without a Github account to contribute.

Per kisslinux/kisslinux.github.io#88 we should look into making the fact that we aren't officially associated with KISS more transparent.

I think a solid and easy way of doing this on the website is adding some extra blurb at the top with the other two that exist ("When dylan..."\n "KISS Linux..."\n) saying something like "KISS-Community is a coalition of KISS users and is not affiliated with or officially supported by Dylan Araps or KISS Linux" (add and subtract words as necessary; this is just an example to show the spirit of what should be said).