Universal Plugin Wiki

Discussion in 'Bukkit Discussion' started by BeeJayMendrinos, Jul 2, 2013.

?

Would you use this

  1. Yes

    30.0%
  2. No

    70.0%
  3. Sometimes

    0 vote(s)
    0.0%
  4. Maybe

    0 vote(s)
    0.0%
Thread Status:
Not open for further replies.
  1. Offline

    BeeJayMendrinos

    I am thinking of starting a universal plugin wiki where players can go and simply click on the plugin they want help with, and it would display the commands and what they do in an orderly list which is easy to read. However I am not sure whether people would use this and I do not want to waste my time if no-one will use it.
     
  2. Offline

    Lolmewn

    So basically BukkitDev?
     
  3. Offline

    BeeJayMendrinos

    No. A wiki with in depth descriptions, screenshots and it brings all the plugins to one place neatly instead of a huge list and endless pages...
     
  4. Offline

    tanveergt5

    I had a idea, thinking of making a wiki based of the media wiki(wikipedia) script, what I was going to do is have every plugin listed there with youtube tutorials, and descriptions and all the info you need really, I got a web host for this now, but I never went through with it.
     
  5. Offline

    toothplck1

    So you want to make a separate wiki for the over 8000 plugins on DevBukkit with in-depth descriptions that people need to maintain in addition to their project page on DevBukkit? And all of this without a large list or multiple pages... Good luck!
     
    Hoolean and drtshock like this.
  6. Offline

    BeeJayMendrinos

    Haha people will have to apply unless it is a well known plugin because I am not doing over 8000 pages.....

    I'm just thinking of using wikia to start off with but maybe changing to a different site after a while

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jun 2, 2016
  7. Offline

    Bertware

    You could start of by scraping bukkitdev or bukget to get basic pages for each plugin (default ones) then provide more information / let user provide more information. Though it seems like bukkitdev covers a lot of this alright.
     
  8. Offline

    BeeJayMendrinos

    Good idea
     
  9. Offline

    toothplck1

    If you aren't going to have every plugin then it won't be Universal... and people won't be able to just go and click, because it would only work for the plugins that people put on your site... And who is going to maintain and keep all those wiki pages up to date and accurate?
     
    Jozeth likes this.
  10. Offline

    Jozeth

    Nice idea but why would a plugin developer create detailed help pages on their sites and DBO page then have to put it on a wiki which can be changed by anyone?
     
  11. Offline

    Me4502

    How about this, don't store actual info for plugins - But have a central area with links to documentation, downloads, issue trackers, source, etc for every plugin. That means you don't need to maintain the docs, and its up to the plugin author to maintain them.
     
  12. How about a system like PluginMetrics? Where you, as a developer, have to add some code in your plugin that will send data to this site with the information/you have to add this to get a basic page on the site (with some basic data e.g. name, description, author, projectsite, commands,...) and then you, as developer, have to make an account on the site, claim the plugin and then you can add extra information...
     
  13. Offline

    toothplck1

    Why would it need to be sent from the plugin... Thats unnecessary connections being forced on users when it doesn't send any user specific or even user related data.... Not to mention that still doesn't make it "Universal" but rather just a place with a couple plugins...
     
  14. True :/ let's just all use devbukkit instead of this project that never will happen...
     
    Jozeth likes this.
  15. Offline

    Stevensaurus

    Any half decent plugin will tell you how to use it; no need to make a whole wiki.
     
Thread Status:
Not open for further replies.

Share This Page