Developer hub/mni

This is a high-level overview of MediaWiki development, including links to the key documents, resources and tools available to MediaWiki developers. It is written for skilled LAMP developers who have experience using MediaWiki.


 * If you want to use Wikimedia web APIs, visit Web APIs hub (work in progress).
 * If you want to contribute to developing Wikimedia software, see New Developers.
 * For an introductory guide to developing MediaWiki and MediaWiki extensions, read How to become a MediaWiki hacker.
 * If you want to collaborate with other third-party MediaWiki users, the MediaWiki Stakeholders' Group (MWStake) is a MediaWiki user group consisting of MediaWiki developers, system administrators, users, consultants, and hosting providers.

ꯍꯦꯟꯅ ꯌꯦꯡꯁꯤꯟꯕ

MediaWiki is the software that powers Wikipedia, its sister projects and thousands of wikis all over the world.

MediaWiki is written in the PHP programming language. It uses jQuery as the client JavaScript library.

MediaWiki is primarily written for the LAMP platform and runs on most operating systems. MediaWiki primarily uses the MySQL and MariaDB database servers.

Development happens in an open source style, is largely coordinated online, and supported by the Wikimedia Foundation, though volunteer community developers play a huge part as well.


 * Development discussion happens on various mailing lists and IRC channels. The main developer list is wikitech-l. The main developer IRC channels are #mediawiki and #wikimedia-dev.
 * Source code is managed using the Git version control system.
 * Code review for most projects is performed on . Follow this tutorial to set up Git and Gerrit in order to submit patches.
 * Bug reports and tasks for most projects are managed on Phabricator.
 * Developers extending or interfacing with MediaWiki (instead of working on the core code) have several convenient extension points, including the API, the Hooks system and Skins – see the #Extending MediaWiki section of this page for an overview.

ꯃꯆꯪ ꯑꯣꯏꯕ ꯗꯣꯀꯨꯃꯦꯟꯇꯁꯤꯡ


Code, development and style

 * Development policy – an overview of key development policies.
 * Coding conventions – learn how to write code in the MediaWiki style.
 * Security for developers – learn how to help keep MediaWiki secure.
 * Pre-commit checklist – read this checklist before committing code.
 * Code review guide – a guide for reviewers of commits to the MediaWiki source code.
 * Requests for Comment (RfC) – read about or suggest new features for the MediaWiki ecosystem.

Debugging and testing

 * How to debug – a guide to debugging MediaWiki.
 * Manual:Errors and symptoms – an overview of common MediaWiki errors and their correlating symptoms.
 *  – learn to write UI tests for MediaWiki using Selenium.
 * Unit testing – learn to write unit tests for MediaWiki using PHPUnit.
 *  – learn how to write secure code.



Architecture

 * Manual:Code – an overview of the key parts of MediaWiki's source code.
 * Database layout – an overview of MediaWiki's database schemas.
 * Global object variables – a partial list of key global variables.
 * Localisation – learn about MediaWiki's internationalisation system.
 * Manual namespace on this wiki – documentation for developers.
 * [//doc.wikimedia.org/mediawiki-core/master/php/ MediaWiki Class Reference] – technical documentation generated from the MediaWiki source code. (Note: The class reference is a large, slow-to-load page.)
 *  – manuals, guides, collections of selected articles.

ꯄꯤꯛꯊꯕ-ꯊꯧꯁꯤꯜꯁꯤꯡ

 * API – MediaWiki's API provides direct, high-level access to the data contained in the MediaWiki databases.
 * ContentHandler – MediaWiki's framework for supporting custom types of page content.
 *  – an overview of using databases in MediaWiki, including a brief guide to the database abstraction layer.
 *  – MediaWiki's framework for processing long-running tasks asynchronously.
 *  – MediaWiki's framework for providing localized application messages with PHP or JavaScript.

Extending MediaWiki
MediaWiki has been designed to allow for modification without changing the "core code". This makes it easy to update to a new version of MediaWiki without having to manually merge in old extension code changes. There are six main extension points that allow developers to change or extend what MediaWiki can do. The extension points are:


 * API – access the data and metadata of MediaWiki instances through its web API.
 * Hooks – every time a given event happens, do something.
 * Parser Functions – create a new command like:.
 * Skins – change the look and feel of MediaWiki.
 * ꯑꯈꯟꯅꯕ ꯂꯥꯃꯥꯏꯁꯤꯡ – ꯑꯅꯧꯕ ꯑꯈꯟꯅꯕ ꯂꯥꯃꯥꯏꯁꯤꯁ ꯍꯥꯞꯆꯤꯟꯂꯨ ꯫
 * Tag Extensions – create a new tag like:.
 * Extending wiki markup – add a parser hook to modify the content of wikitext.

Help for extension developers

 * Manual:Developing extensions – a guide to developing extensions.
 * Project:WikiProject Extensions
 * Extensions FAQ
 * See Category:Extensions, for a list of extensions.
 * Manual:$wgExtensionFunctions – use to defer setup (or run other callbacks) for extensions until after the MediaWiki core is setup.
 * Extension:BoilerPlate - a blank extension template.

Help for skin developers

 * Manual:Skinning Part 1 – instructions on how to create a skin for MediaWiki.
 * Manual:Skin configuration – a guide to configuring skins for a wiki.

Help for library code reuse

 * – a guide to packaging third-party libraries for use with MediaWiki.

Third-party wiki uses

 * - For Enterprise wikis
 * - For Academic wikis