Add a wiki

This guide may be incomplete. Some cases don't need Apache configs or a docroot. Look at the existing similar wikis to see what is required.

This page documents the process for adding a new wiki. This includes new languages on sister projects, and wikis for committees, chapters etc.

Preparation

The following steps need to be completed before the wiki database may be created.

Notify

• Create a Phabricator task for the wiki creation (if one doesn't exist already).
  • It should be tagged with #Wiki-Setup (Create).
• Create (if not already) a sub-task "Prepare and check storage layer for <new wiki>".
  • It should be tagged with #DBA, #wmcs-kanban and #Data-Services.
• Notify the Operations list. In particular, it needs to be made clear whether the wiki should be public, or private. If public, ops will arrange for the wiki to be replicated to Cloud Services. If private, ops will need to add the wiki to $private_wikis in operations/puppet.git:/manifests/realm.pp.
• IMPORTANT: If the wiki is a regular public wiki to appear on Cloud Services - you can continue. If the wiki is private and should not be replicated to Cloud Services DO NOT CONTINUE UNTIL YOU HAVE THE OK FROM OPS/DBAs to check no private data is leaked. There are mechanisms in place to prevent that by default, but those should be manually checked.

DNS

First of all, ensure the relevant domain names exist for the new wiki. Make the following changes in a commit for the operations/dns.git repo and submit to Gerrit for review.

• If it is a language project, ensure the language code is present in /templates/helpers/langlist.tmpl. This is shared between all sister projects. If another sister project has the same language already, then this has probably been done already.
• If it is a subdomain of ".wikimedia.org" domain (chapter wiki or special wiki)
  • Add it to /templates/wikimedia.org.
  • Make sure to also add a mobile entry.

• Merge the change in Gerrit and run authdns-update.
• Query the DNS servers to make sure it has been correctly deployed. See DNS#HOWTO for details.
• For new languages, there is also a need to regenerate zones. Run on ns0, ns1 and ns2: authdns-gen-zones -f /srv/authdns/git/templates /etc/gdnsd/zones && gdnsdctl reload-zones

Apache configuration

Apache configuration is located in the operations/puppet.git repo.

• Common configuration:
  • For a new language project, this step is usually not needed as shared configuration already covers it.
  • For a new chapter wiki, add it to mediawiki.yaml under wikimedia-chapter
• After the change is merged in Gerrit, deploy the configuration change and (if needed) gracefully restart app servers. See Application servers/Runbook#Deploying config for details.
• If there are additional domains that should point to the same wiki, add it to redirects/redirects.dat.

Language configuration

Check the following for every wiki, even if another wiki in this language already exists:

1. Make sure that the wiki's content language code appears in the language-data repository (file data/langdb.yaml; if you're adding it, make sure to follow the instructions in README).
2. Make sure that the wiki's content language code is fully configured to be supported by core MediaWiki. The code must appear in the following files:
   • includes/languages/data/Names.php (precisely this code, and not a variant)
   • The file languages/messages/MessagesAbc.php must exist (replace Abc with the language code).
3. If the language is written from right to left, make sure it is configured as such in the following files:
   • In the core MediaWiki repository, the file languages/messages/MessagesAbc.php must explicitly say $rtl = true; near the top.
   • In the MobileFrontend extension repository: src/mobile.languages.structured/rtlLanguages.js
   • In the Android app repository: app/src/main/java/org/wikipedia/util/L10nUtil.java (the RTL_LANGS list)
   • In the iOS app repository: Wikipedia/Code/MWLanguageInfo.m (the rtlLanguages list)
4. Check whether the language code appears in any extra configuration for Wikibase and Wikidata. If it appears in any of the following files, it should be removed (verify with Wikidata developers):
   • In the Wikibase repository: lib/includes/WikibaseContentLanguages.php
   • In the WikibaseLexeme repository:
     • WikibaseLexeme.mediawiki-services.php
     • If the key wikibase-lexeme-language-name-ABC exists in i18n/en.json and i18n/qqq.json, remove it from these two files.
   • In the Wikimedia's mediawiki-config repository: the wmgExtraLanguageNames variable in wmf-config/InitialiseSettings.php
5. Check that usernames in the writing system of this language are possible and aren't filtered out. If they are blocked, add support for this writing system to AntiSpoof. Example patch.

Determine if this is a new language project (like Spanish Wikibooks) or a chapter wiki (like Wikimedia Denmark), or something else (special wiki or private wiki).

For a new language project, make sure the language has been approved by the Language committee at Requests for new languages on Meta-Wiki. Usually, the Phabricator task will contain a link to the approval page. For all other wikis, go directly to #Install.

Install

IMPORTANT: For Private Wikis

• Private wiki databases must not be replicated to the Cloud Services DB MySQL instances!
  • Before creating a database for a private wiki, make sure to add the db name to the puppet global array $private_wikis in operations/puppet.git:/hieradata/common.yaml.
  • Deploy this config change with puppet and manually restart the Prelabsdb-db MySQL instance (Sanitarium) on the server that will house this wiki's db (most likely s5).
  • If you need help with this, please ask a member of the DBAs for help. This is very important.
• If you enable local upload for a private wiki, you must get the SRE team to check the permissions on the swift containers for your new wiki (you risk the contents being world-readable otherwise) - refer them to Swift/How To#Checking / Fixing container ACLs for private wikis for details. If you have disabled local upload (i.e. Local file uploads: disabled), then this isn't necessary, as no swift containers should exist.

MediaWiki configuration

Gather all relevant information about the new project. Each wiki has different requirements (project name, namespaces, extensions to be enabled etc).

Make the following changes on your own checkout of operations/mediawiki-config.git and submit to Gerrit for review:

• For a new language project, add the language code (ISO 639 code: usually provided in the task) to langlist. This will be used at Special:SiteMatrix and for interwiki linking etc.
• Create the YAML definition of the wiki in wmf-config/config, including making it inherit from relevant settings profiles, as follows:

Wiki grouping	Group options	Purpose
All All wikis must be tagged against 'all'	all.dblist	The primary listing of what wikis exist, used as the basis of all tools.
DB cluster Every wiki must be in exactly one of these	s1.dblist s2.dblist s3.dblist s4.dblist s5.dblist s6.dblist s7.dblist s8.dblist s11.dblist	Database lists of wikis in each MySQL database cluster. In most cases, wikis should just be added to s5
Wiki size Every wiki must be in exactly one of these	small.dblist medium.dblist large.dblist	Database lists of wikis arranged into their relevant size.
Wiki family Every wiki must be in exactly one of these (or one plus in special)	wikimania.dblist wikimedia.dblist wikibooks.dblist wikinews.dblist wikipedia.dblist wikiquote.dblist wikisource.dblist wikiversity.dblist wikivoyage.dblist wiktionary.dblist special.dblist	Sister project, Wikimania, chapter, or special. NOTE: Some wikis maybe in special and one other list.
Closed	closed.dblist	Any closed (no write access, full read access) wikis
Deleted	deleted.dblist	Wiki databases which MediaWiki is no longer configured to access
Wiki privacy	fishbowl.dblist	All fishbowl (restricted write access, full read access) wikis
	private.dblist	All private (read and write restricted) wikis
Extension configurations	flaggedrevs.dblist	All wikis running the FlaggedRevs extension
	securepollglobal.dblist	$wgSecurePollCreateWikiGroups wikis: Board Election wikis
	visualeditor-nondefault.dblist	All wikis where VisualEditor is not enabled by default
	commonsuploads.dblist	All wikis which should have local uploading soft-disabled. Uploads go to Commons instead.
Wikidata-related wiki groups	wikidata.dblist	All wikis running the Wikidata repo
	wikidataclient.dblist	All wikis running the Wikidata client (most new language-project wikis should start off like this)

• Once your YAML file is created, add a dummy entry to wikiversions.json mapping the database name to a version string, then run composer test which will update the automatic "dblist" files and spot any issues. Alternatively, you can run composer buildDBLists which only builds the dblists.
• If the new wiki is created at a different shard than s3 (which is likely, as new wikis are created at s5 as of August 2020), you need to add the wiki to wmf-config/db-production.php. Check with DBAs if you're unsure how to properly edit the file, this is very important.
• Update the configuration files (located in /wmf-config). Some may have sufficient defaults but the following are often wiki-specific in InitialiseSettings.php:
  • $wgServer, $wgCanonicalServer - For language projects, the defaults work fine.
  • $wgLogos (see below), $wgSitename, $wgExtraNamespaces, $wgLocaltimezone.
  • groupOverrides.
  • Ensure $wgCategoryCollation is set to the appropiate sorting for this wiki's language. If you are not sure, ask on the task.
  • If an extension needs to be enabled, this is usually done by setting a wmg-variable to true in InitialiseSettings along with custom configuration there. Some extensions' configuration are located in a dedicated files in the /wmf-config directory.
  • SUL wikis on wikimedia.org or another non-standard domain name must be added to $wgLocalVirtualHosts. This is necessary to make cross-wiki HTTP requests work (used by ie. cross-wiki notifications).
• If you added a new language code to the langlist (see above), you probably need to add it to the InterwikiSortingOrder.php file too
• For "*wikimedia" suffix databases, add the subdomain to the list in MWMultiVersion::setSiteInfoForWiki
• Adjust the entry in wikiversions.json to the current production version. See Deployments (one week) and Deployment Train.

Logo

Projects, in particular Wikipedias, usually have a localized logo.

Check the following:

• The project has a full localized logo in Commons (image + wordmark). For Wikipedia, the filename is usually File:Wikipedia-logo-v2-LANGUAGE.svg, for example File:Wikipedia-logo-v2-fr.svg for French. If there is no localized logo, ask the project's editor to provide the localized text and get the logo created and uploaded to Commons.
• The project has versions of the logo in all the necessary sizes and resolutions uploaded. If not, create, upload, and configure them according to the instructions at Wikimedia site requests#Change the logo of a Wikimedia wiki.
• The project has a localized wordmark without the image. This is shown at the bottom of the mobile site and in some other places. This is not necessary if the name of the project is completely identical to the default English name, but necessary if it's not identical. For Wikipedia, the filename is usually File:Wikipedia-wordmark-LANGUAGE.svg, for example File:Wikipedia-wordmark-fr.svg for French.

Database creation

Once the above is reviewed, merged and pull down on the deployment host also pull it down on mwmaint1002 (scap pull), but do not yet deploy to main app servers until after the database is created.

Now it's time to actually create the database using the addWiki script. This also performs other tasks, such as notifying the "newprojects" mailing list.

The installation script must be run from mwmaint1002 (not the deployment host). If the wiki is going to be a Wikidata client, make sure it's present in the wikidataclient.dblist file and that the new version of that file has been pulled down on mwmaint1002 **before** running the installation script, or things will break.

The dummy wiki (noted as muswiki in the code) is shard-dependant. Wikis at s5 should be created using muswiki, while wikis at s3 were created via aawiki. Wiktionaries needs to be created via mhwiktionary (s5) and aawiktionary (s3).

The syntax is as follows:

mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=muswiki <languagecode> <projectname> <databasename> <domain>

• For a new Wikipedia - for example Lingua Franca Nova Wikipedia:
  mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=muswiki lfn wikipedia lfnwiki lfn.wikipedia.org
• For another new language projects - for example a Spanish Wikinews:
  mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=muswiki es wikinews eswikinews es.wikinews.org
• For a new chapters wikis - for example a Finnish chapter wiki:
  mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=muswiki fi wikimedia fiwikimedia fi.wikimedia.org
• For non-standard special wikis (such as committees, or unique projects like meta or commons) - for example strategy.wikimedia.org:
  mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=muswiki en wikimedia strategywiki strategy.wikimedia.org

1. Merge the config change in Gerrit, and pull it onto the deployment host.
2. Verify that the *.dblist files now contain the new wiki.
3. Pull the whole on mwdebug1002 and mwmaint1002 through scap pull
4. Run the addWiki maintenance script, as described above (important to do before any sync of dblists or wikiversions, as some components like login use that)
5. Run scap sync-world
6. Unless it's a language project, add the project to the meta:Interwiki map.
7. Regenerate the interwiki cache and deploy it. (For all new wikis, not just new language projects.)
   • scap update-interwiki-cache (and then follow the instructions)
   • Edit meta:Interwiki map/updated and update when the last update was.

RESTBase

RESTBase is a service providing a RESTful API for the projects' wikis. This service is in a process of deprecation, below is an outline for the current process.

Before proceeding with these steps please reach out to the #platform-engineering team directly.

To enable it to serve the new wiki as well, create a task tagged with #platform_engineering, then create a patch for mediawiki/services/restbase/deploy adding its domain to the appropriate section in RESTBase's configuration, and link that patch with the phab task.

After the patch is merged, a restart of the RB service across the cluster is required, which can be done by ops or restbase-admins/restbase-roots.

Parsoid

Parsoid is now integrated with core, and should pick up the wiki automatically.

cxserver

For project families in which the ContentTranslation is installed (as of 2018—only Wikipedia projects): Add the language code to the ContentTranslation registry - mediawiki/services/cxserver repository, file config/languages.yaml (included by config.dev.yaml and config.prod.yaml).

Once merged to master, ping the ContentTranslation developers to deploy the change. That requires to sync repositories, ie to update mediawiki/services/cxserver/deploy to match mediawiki/services/cxserver. See: https://gerrit.wikimedia.org/r/c/303763/ for an example commit.

Search

Search indices need to be initialized for new wikis starting with 1.36.0-wmf.10. For a typical wiki creation only the following command is necessary. See Search#Adding new wikis for more information.

$ mwscript extensions/CirrusSearch/maintenance/UpdateSearchIndexConfig.php --wiki=$wiki --cluster=all

Swift

Necessary changes are made automatically by the addWiki.php script. For a private wiki with local upload enabled, you must get SRE to review the permissions on the swift containers, however (refer them to Swift/How To#Checking / Fixing container ACLs for private wikis).

Wiki Replicas

These steps are necessary to make the wiki available in the Wiki Replicas.

Before maintain views: DBAs' work

First, the DBAs need to run this on both sanitariums (eqiad and codfw) and all cloud replicas of that section (clouddb10xm):

root@db1154:~# redact_sanitarium.sh -d gpewiki -S /run/mysqld/mysqld.s5.sock | mysql -S /run/mysqld/mysqld.s5.sock gpewiki

Then:

root@db1154:~# check_private_data.py -S /run/mysqld/mysqld.s5.sock | mysql -S /run/mysqld/mysqld.s5.sock

And then run check_private_data.py -S /run/mysqld/mysqld.s5.sock to make sure there is no private data. Also wait for some edits to be done in the wiki and run it again to make sure triggers work fine.

Once that's done, create the ${wiki}_p database and granted access to labsdbuser in the cloud replicas (otherwise a bug in MariaDB will cause the scripts to fail). This what DBAs need to do on each cloud replicas (not sanitariums):

$ sudo -i mysql --skip-ssl
mysql:root@localhost [(none)]> create database ckbwiktionary_p;
mysql:root@localhost [(none)]> GRANT SELECT, SHOW VIEW ON `ckbwiktionary_p`.* TO 'labsdbuser';

Maintain views

When the task is ready for WMCS, run the cookbook sre.wikireplicas.add-wiki on the any of the cluster management hosts (cumin1002.eqiad.wmnet, cumin2002.codfw.wmnet). The following example is for smnwiki and it's task. Replace those values with the wiki database name you are adding and the correct task ID:

$ sudo /usr/local/bin/secure-cookbook sre.wikireplicas.add-wiki --task-id T264900 smnwiki
START - Cookbook sre.wikireplicas.add-wiki
Generating views...
Adding DNS
Finalizing meta_p
Added views for new wiki: smnwiki T264900
END (PASS) - Cookbook sre.wikireplicas.add-wiki (exit_code=0)

The "Adding DNS" step takes quite a while to complete. Do not panic!

If you are adding more than one wiki that day or several tickets have been opened to add wikis, you may find that the DNS step creates all of them at once. After that has been done, it doesn't need to be done again. You can save yourself lots of time by using the --skip-dns option on the command line so it doesn't sit there scanning for new wikis.

If in doubt you can always use the --dry-run option on the secure-cookbook command so that you just see what it would do. For example:

$ sudo secure-cookbook --dry-run sre.wikireplicas.add-wiki --task-id T260551 thankyouwiki
DRY-RUN: Executing cookbook sre.wikireplicas.add-wiki with args: ['--task-id', 'T260551', 'thankyouwiki']
DRY-RUN: START - Cookbook sre.wikireplicas.add-wiki
DRY-RUN: Generating views...
DRY-RUN: Executing commands ['/usr/local/sbin/maintain-replica-indexes --database thankyouwiki', '/usr/local/sbin/maintain-views --databases thankyouwiki'] on 4 hosts: labsdb[1009-1012].eqiad.wmnet
DRY-RUN: Adding DNS
DRY-RUN: Executing commands ['source /root/novaenv.sh; wmcs-wikireplica-dns --aliases'] on 1 hosts: cloudcontrol1003.wikimedia.org
DRY-RUN: Finalizing meta_p
DRY-RUN: Executing commands ['/usr/local/sbin/maintain-meta_p --databases thankyouwiki'] on 4 hosts: labsdb[1009-1012].eqiad.wmnet
DRY-RUN: Added views for new wiki: thankyouwiki T260551
DRY-RUN: END (PASS) - Cookbook sre.wikireplicas.add-wiki (exit_code=0)

Manual method in case Maintain views fail

Once it is replicating to the clouddb* servers (e.g. clouddb1013), run the following 2 commands on each replica server:

localhost:~$ ssh clouddb10xx.eqiad.wmnet
clouddb10xx:~$ sudo /usr/local/sbin/maintain-replica-indexes --database $wiki --debug
clouddb10xx:~$ sudo /usr/local/sbin/maintain-views --databases $wiki --debug

Note the section for use with the wikireplica dns next

clouddb10xx:~$ grep $wiki /usr/local/lib/mediawiki-config/dblists/s*.dblist* | grep -o '\w[0-9]'
:# Should return a shared, like s3, s5, etc

From a cloud control host, add the wikidb alias in the Wiki Replicas service name:

localhost:~$ ssh cloudcontrol1003.wikimedia.org
cloudcontrol1005:~$ sudo -i
cloudcontrol1005:~$ source novaenv.sh
cloudcontrol1005:~$ /usr/local/sbin/wmcs-wikireplica-dns --aliases --shard <sN>
:# Use the shard arg only if you know the shard (which you can get on a replica server as noted above)
:# If the shard is s3 or a full rebuild is done it will take quite a while to run

Insert a new row in meta_p.wiki for the new wiki by running the following on each of the replica servers that host the s7 instance.

localhost:~$ ssh clouddb10xx.eqiad.wmnet
clouddb10xx:~$ sudo /usr/local/sbin/maintain-meta_p --database $wiki

Finish up for either method

Before resolving the ticket, log into a Toolforge bastion as yourself and run:

localhost:~$ ssh login.toolforge.org
tools-sgebastion-07:~$ sql $wiki
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 470351380
Server version: 10.1.43-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [$wiki_p]> select * from page limit 2;

If you get an error from the select * from page limit 2; statement, you may have missed a step or need to do some troubleshooting. You should just get a couple records.

WikimediaMessages

Translatable project name

Add a message with the wiki name to extensions/WikimediaMessages/i18n/wikimediaprojectnames/en.json and qqq.json. The message keys should include the wiki database name (WIKI_DBNAME below) and official "human readable" name (WIKI_NAME below) as follows:

en.json

Key	Message
project-localized-name-WIKI_DBNAME	WIKI_NAME

For example, "project-localized-name-enwiki": "English Wikipedia",

qqq.json

Key	Message
project-localized-name-WIKI_DBNAME	{{ProjectNameDocumentation|url=WIKI_URL|name=WIKI_NAME|language=WIKI_LANG}}

For example, "project-localized-name-enwiki": "{{ProjectNameDocumentation|url=https://en.wikipedia.org|name=English Wikipedia|language=en}}",

Cross-wiki (a.k.a. interwiki) search result title

If this is a new language Wikipedia, add a message with the wiki name to extensions/WikimediaMessages/i18n/wikimediainterwikisearchresults/en.json and qqq.json in the list of search-interwiki-results messages.

Wikipedia mobile apps

If you are creating a new Wikipedia, add an entry for the new language.

For the Android app, you must run the following two scripts, which will update the list of languages known to the app (including the corresponding language codes, autonyms, English names, etc.):

$ cd scripts
$ ./generate_wiki_languages.py
$ ./make-templates.py

This should update several .java and .xml files that you may then submit in a pull-request to our repository.

(TODO: Is there anything to do for the iOS app?)

Post-install

General announcement in Tech/News

Add an entry to m:Tech/News so that people know the new wiki exists, and can adjust their tools/bots/etc. as appropriate.

Wikidata

See also: WMDE/Wikidata/Enable Client

Only needed if the new wiki is supposed to be a Wikidata client.

In order to be able to link the new wiki from Wikidata, and to allow interwiki links from Wikidata to the new wiki, run extensions/Wikibase/lib/maintenance/populateSitesTable.php --force-protocol https on at least all Wikidata clients (including wikidatawiki itself and testwikidata).

foreachwikiindblist wikidataclient extensions/Wikibase/lib/maintenance/populateSitesTable.php --force-protocol https

That script is known to be troublesome, you might want to ask Marius (hoo) or Amir Sarabadani (Amir1) run it for you or just create a ticket (that may be done anytime after the wiki was created).

Beware: The script sometimes fails with a duplicate key conflict. In that case, go to the wiki's master database and empty the sites and site_identifiers tables, then run the script again. It's probably also wise to backup these tables from Wikidata and at least one Wikipedia before running the script across the whole fleet. Breaking the sites, site_identifiers tables will break page rendering of many wikis!

Data Engineering

Most wikis are added to the Pageviews definition, which means that the log events are extracted from the Webrequest stream and saved as distinct datasets.

Exceptions to this include:

• private wikis
• Wikimania conference wikis
• Other special cases such as usability,outreach,login,vote,strategy etc.

If you are unsure about whether or not the wiki should be included,check with the Data Engineering team.

In order to add the new wiki to the pageview definition, submit a change proposal to the analytics/refinery repository, adding the wiki to static_data/pageview/allowlist/allowlist.tsv.

Incubator

If there's something to import (as is often the case in new language projects), someone will do so. Their process is described at Incubator:Importing from Incubator (logged at Incubator:Site creation log).

Clean up interwiki links

After any import Incubator is completed, Inform the community and make a Phabricator task for removing old interwiki links and migrating them to Wikidata (For example T134991 for edits such as d:Special:Diff/336584053 and jam:Special:Diff/12330). You can do it by yourself using interwikidata.py in pywikibot.

python3 pwb.py scripts/interwikidata.py -lang:LANGCODE -clean -start:! -always

Tell wikistats Cloud VPS project to add the wiki

If the wiki is a public wiki, create a Phabricator task (subtask of the main task to create the wiki) with the tag "VPS-project-wikistats" and just ask for the wiki to be added. (What needs to be done can be seen f.e. in https://phabricator.wikimedia.org/T140970#2531977)

Tell Pywikibot project to add the wiki

Create a Phabricator task (subtask of the main task to create the wiki) with the tag "pywikibot" and just ask for the wiki to be added.

Mobile apps

Wikipedia has mobile apps for Android and iOS. A Wikipedia in a new language must work in the app after the import from the Incubator is complete. Report a bug under the apps tags in Phabricator if any of the following doesn't work:

• You are supposed see the language in the user preferences.
  • Android: Settings -> Wikipedia language.
  • iOS: Settings -> My languages
• You see the language in the interlanguage links list. Find an article that exists in the new Wikipedia and in English. Go to the English Wikipedia, tap the 文Α icon at the bottom and find the article in the list. In particular:
  • The article name must appear.
  • The language name (autonym) must appear.
  • The item must be findable using the language name in English and the autonym. (If you don't know how to type the autonym, try pasting the autonym or ask somebody who writes in that Wikipedia.)
  • Tapping the item must show the article.

Portal

Add the new site to the wikimedia/portals repository:

• If the language is right-to-left and the site is a Wikipedia, make sure it appears in src/wikipedia.org/rtl-languages.json.
• Check that the language name is written in translatewiki and exported to the appropriate json file under l10n/.

After creating the wiki and deploying the portal changes, test that the language name appears correctly in the wikipedia.org portal.

Kiwix

Tell Kiwix to add support for the new wiki. Kiwix is an external project, but it works quite closely with Wikimedia to provide regularly-update offline versions as ZIM files. To ask the adding of a wiki, file an issue on the https://github.com/openzim/zim-requests GitHub repository. Boilerplate for Wikipedia:

Website URL: https://CODE.wikipedia.org
License: CC-BY-SA 3.0
Desired ZIM Icon –png (URL or attach one): https://drive.farm.openzim.org/wikipedia_all/favicon-48x48.png
Language (ISO 639-3): kcg
Is this a MediaWiki?: yes

Comments:

• Make sure to correct the language code in the URL.
• For non-Wikipedia projects, make sure that you use the correct URL.
• If it's the first wiki in the language, make sure to mention the three-letter language code, the English name of the language and the autonym, so that Kiwix developers can add the language to their database.
• If the default license ever changes from CC-BY-SA 3.0 to CC-BY-SA 4.0 (or something else), write it there, and update the documentation here.

See also

• Close a wiki
• Delete a wiki