Looking to add an extension to your Gamepedia wiki? Please follow the steps below:
- See if Gamepedia currently allows the extension by viewing the Extensions page.
- If it is listed on the page and isn't a forbidden extension: Go to the section Extensions approved on Gamepedia.
- If it isn't listed on the page: Go to the section Extensions not yet approved on Gamepedia.
- 1 Extensions approved on Gamepedia
- 2 Extensions not yet approved on Gamepedia
- 3 Requested extensions pending review
- 4 Reviewed extension requests
- 5 FAQ
Extensions approved on Gamepedia[edit | edit source]
Reach out to the Wiki Manager for your wiki to request the extension. In your message to the manager, be sure to include the name of the extension and the wiki on which you'd like it installed. You can contact the manager via one of the following ways:
- The wiki's admin noticeboard or community portal
- The manager's talk page
- The manager's profile comments
If you cannot reach the Wiki Manager in any of these ways, feel free to email firstname.lastname@example.org to reach our community team.
Coordinate with the manager and the wiki's admin team. Sometimes, new extensions can have an impact on a wiki's existing configuration. It's recommended to work with the wiki's administrators to ensure the extension doesn't cause a negative impact. The manager and/or admin team may have a suggestion on an alternative route to take.
For extensions which create additional namespaces, like Gadgets, Scribunto, Widgets, and others, please wait until after the extension has been installed before trying to create documents in these namespaces.
Extensions not yet approved on Gamepedia[edit | edit source]
- Find a site that discusses the extension and copy the link. The MediaWiki Extensions category is a good place to look.
- Add the extension to the list below.
- Create a new section on the talk page with the following information:
- Extension name and link
- Your username
- Wiki the extension is requested on
- Description of your use case(s)
- Any other users that would also like to use the extension on their wiki should add a new comment with their information to the talk page.
Extension approval guidelines[edit | edit source]
Every new external extension added to Hydra creates a new set of external dependencies and potentially the need for Hydra to take over development of a third party extension. To prevent being wholly dependent on a third party we have a strict set of approval guidelines for new extensions.
- Extensions should be applicable to more than one wiki. Sometimes we will approve an extension for a single wiki, but there must be a very compelling reason to do so.
- If the extension replicates an existing extension's functionality it either needs to fully replace that extension or have that new functionality rolled into the old extension.
- Code standards for extensions must be followed. That means the extension should be using extension registration loading, follow MediaWiki coding standards, and be soundly designed.
Requested extensions pending review[edit | edit source]
- Highlight Links in Category (MIT license)
Reviewed extension requests[edit | edit source]
These requests were reviewed (Q2 2019). They will be added to the Extensions article once completed and removed from this list after the Q2 2019 review.
Implemented[edit | edit source]
Approved[edit | edit source]
Approved, pending Engineering review[edit | edit source]
- Numbertext (LGPL/BSD dual-license, no MediaWiki version mentioned) - Approved
- CustomLogs (GNU General Public License v2.0, this extension was created by River) - Approved
- TemplateStyles (GNU General Public License 2.0 or later) - Approved
- GlobalCssJs (GNU General Public License 2.0 or later) - Probably, as long as there isn't a security issue and doesn't require significant dev time to make it work. (From the extension page: Warning: If you are not using shared user tables or CentralAuth, this extension can open up a XSS vector, which allows other users to hijack the user's account, among other things. See #Hook for information on how to integrate your authentication extension with this one.)
- Header Footer (GNU General Public License 2.0 or later) - Approved, if this tests out ok on staging and fulfills the need.
Denied[edit | edit source]
- DiscordNotifications (GitLab ticket) - The code is not suitable for our platform, but we like the functionality. This is something we'd like to investigate doing ourselves in the future.
- FixedHeaderTable (GitLab ticket) - We like the idea of the functionality and will implement something similar ourselves.
- GlobalUsage - Requires too much development work to get it working on our platform that we can't invest at this time. We can revisit it in the future, if there's a strong case for it.
- Kartographer (GitLab ticket) - We'd rather develop an easier to use tool ourselves for mapping.
- PortableInfobox - Not at this time. Requires more discussion on the future of integrated platforms and features.
- StructuredDiscussions - Not at this time. Requires more discussion on the future of integrated platforms and features.
- UrlGetParameters - Requires disabling the parser cache which will not be done for use of an extension.
- Wikibase - Not at this time. Requires more discussion on the future of integrated platforms and features.
- Quiz - No, we are developing/adding in our own system soon.
FAQ[edit | edit source]
How long will the extension take to be added?[edit | edit source]
Extensions on the approved list can take less than one day to be added. Extensions not on the list have to be reviewed, with reviews happening on a quarterly basis. Your wiki manager will be able to give you a better timeline once you've reached out about the extension you're interested in.
- Next review of requests: Q3 2019
Am I guaranteed to have a new extension approved?[edit | edit source]
Each new extension will undergo a vetting process by the Gamepedia team. If the extension appears problematic for security, licensing, or compatibility reasons, sometimes our teams can suggest alternatives that will serve a similar purpose. We typically make every effort to help our editors find a solution for the situation at hand but cannot guarantee extensions will be approved.