Extension:Gadgets/Roadmap

Use-cases

 * Centralised gadgets repository (on MW.org ? Meta-Wiki? on a dedicated wiki?)
 * Projects still may define local gadgets (for example, gadgets related to specific policies/guidelines)
 * Centralised localisation (MediaWiki:-namespace,, RL2: Loading of extra messages for gadgets)
 * No more manual editing of gadgets definition, everything should have its GUI
 * Gadget JS/CSS should still be stored on wiki pages
 * Instead of scaring people with a huge list, provide a selection UI with category-based browsing
 * Sort-of done already (sections, checkboxes, descriptions)
 * .... and full-text search
 * Sites may want to enable a global gadget for everyone by default -> bug 13742 / 85902
 * Create ResourceLoader modules on-wiki to be shared between gadgets. Just like gadgets that have their modules, but are not available for people to select explicitly.
 * ResourceLoader-V2 plans to create a way for client modules to be registered (bug 27561?), perhaps via Gadgets (hide modules from view, but usable as a dependancy), perhaps via Core (mw.loader.register ? )