Extension:CentralNotice/es

The CentralNotice extension delivers announcements (usually in the form of banners) to Wikimedia wikis. It is used heavily by the Fundraising team to solicit donations, and for announcements of interest to Wikimedia communities and users. CentralNotice can target announcements by country, language, project, device and logged-in status.

This page has information for CentralNotice developers and wiki administrators who want to install CentralNotice on their own sites. To learn how to create and configure CentralNotice campaigns, please see Help:CentralNotice on Meta-Wiki. For information about the CentralNotice setup on the Wikimedia Foundation's cluster, see CentralNotice on Wikitech.

CentralNotice allows central distribution of announcements to many wikis (called subscribing wikis) from a central wiki (the infrastructure wiki). If you only need to post messages to a single wiki, consider using Sitenotice instead.

For all wikis
If the  cookie is pre-populated, however, its value will be used. For local development, you can enable a client-side implementation that uses https://freegeoip.net as follows. For more information, see #GeoIP lookup.
 * 1) Download the latest snapshot and extract it to your extensions directory.
 * 1) Add to the following:
 * 1) By default, GeoIP lookup is disabled.



La infraestructura wiki
For example If additional groups are needed, assign them the  and   permissions.
 * 1) Desde la línea de comando, ve al wiki raíz y ejecuta
 * 2) Edita   y especifica...
 * 3)   para "true"
 * 1)   to be an array of projects that will subscribe to the central wiki.
 * 1) By default the   group is the only group with the ability to administer CentralNotice.

Subscribing wikis
Edit  and set...

For example ; For example:.
 * 1)   to  ;
 * 1)   to be an entry in  ;
 * 1)   to the protocol (potentially neutral) and domain of the central wiki.
 * 1)   to the URL of Special:BannerLoader on the central wiki, for example:  ;
 * 1) either   to the name of the infrastructure wiki's database, or   to the API endpoint of the infrastructure wiki; and
 * 1)   to the URL of Special:RecordImpression on the central wiki.

Quick developer setup
For most development tasks, you can use a single wiki in both infrastructure and subscribing roles. Following are sample lines to include in. (See notes in comments.)

All code that runs on subscribing wikis should be smoke-tested with, to ensure they work on the mobile version of the site.

Dependencies
Some CentralNotice features require other MediaWiki extensions, including and.

Getting help
The WMF team are the maintainers of CentralNotice. For questions about installation, bug reports, or usage of CentralNotice please send an email to the mailing list wikitech-l@lists.wikimedia.org or join us in the IRC channel.

Permissions
Relevant only to the infrastructure wikis (see also 26377).
 *   — Permission required to modify campaigns and banners.
 *   is required to edit banner content.

Design concepts
From a user facing perspective, the high level CentralNotice objects are campaigns (a.k.a. notices) and banners (a.k.a. templates). These are affected by the back end concepts of selectors and allocation.

The user status, device type, UI language selectors are applied to banners. All banners in a category share user side cookies, such as the hiding cookie that is set when a user clicks a banner close button. The project, country and content language selectors apply at the campaign level. The system allows as many active campaigns at the same time as you want dynamically calculating an allocation for each banner in an active campaign. Campaigns are defined as active if the central wiki time is greater than the campaign start time, less than the campaign end time, and the campaign is marked as enabled. Buckets are yet another selector, and weight affects the relative allocation of banners inside a campaign. Higher priority campaigns will get a greater allocation of page views. This allows, for example, different banners to be shown to logged in versus logged out users in Argentina browsing Wikipedia in English.
 * Banner — a single block of translatable html/wikitext/css/javascript that will display at the top of pages.
 * Banners may be grouped by category.
 * Campaign — a collection of banners.
 * Banners in a campaign are assigned a bucket and weight.
 * There are four priority levels in CentralNotice.
 * Campaigns may be locked which will prevent editing and deletion of the campaign; but not the banners inside a campaign.
 * Selector — any property which may be filtered on for the purposes of allocation.
 * A selection vector is the complete set of selectors a user presents to the central wiki when requesting a banner.
 * Allocation — The chance a banner will be shown to a user under a given selection vector.

Design documents

 * Design Research Project 2017
 * Banner allocation algorithm
 * Database schema / table layout

GeoIP lookup
By default, CentralNotice has no client-side GeoIP lookup service configured. This is optimised for the Wikimedia Foundation production configuration where Varnish populates the  cookie from the server-side. (See Geolocation.) You can configure CentralNotice to use a custom data source client-side through the  configuration variable. This variable expects the name of a ResourceLoader module that exports a function. The function will be called without parameters and should return a Promise that resolves with an object containing the following properties:


 * country: string - Two-letter country code.
 * region: string - Implementation specific.
 * city: string - City name.
 * lat: number.
 * lon: number.

Usage
Full usage instructions can be found at meta:Help:CentralNotice.

New Banner

 * 1) Load Special:CentralNoticeBanners
 * 1) Click on the add banner link at the bottom of the page (must be logged in as an admin).
 * 1) Enter in a name and the raw HTML for the given banner.
 * 1) If this banner is going to be translated then enclose any text to be translated with triple parens -.
 * 1) Submit

(TODO: move and expand this snippet)


 * Each banner has its banner definition stored in MediaWiki:Centralnotice-template-&lt;name>
 * All of its messages are stored below the banner defined in MediaWiki:Centralnotice-template-&lt;name>-&lt;message>/&lt;language_code>

New Campaign

 * 1) Load Special:CentralNotice
 * 1) Add a campaign with a given start time at the bottom portion of the page, leave a comment, and click submit.
 * 1) If this campaign is only run on a specific wiki and or language then select it from the pull downs.
 * 1) Click on the new campaign and add the banners you want within this running campaign and their respective weights.
 * 1) If all looks well then set this campaign to enabled and it will show at the corresponding time.

Overriding selection
Add any of the following URL parameters to preview a specific banner, defeat "diet" schemes, or debug pseudorandom banner selection.


 * banner
 * You can test a banner directly on any wiki by adding  to the end of the URL.


 * randomcampaign
 * A decimal number between 0 and 1, to be used as the "random" seed for choosing a campaign.


 * randombanner
 * A decimal number between 0 and 1, to be used as the "random" seed for choosing a banner among banners available in the chosen campaign.


 * country
 * Override the country code, before filtering to geotargeted campaigns. Accepts two-character ISO 3166-1 codes.


 * uselang
 * Its usual meaning in MediaWiki, this determines which banners you may be shown. Beware of content language vs. user language.


 * force
 * Override any banner hiding code, show the banner.


 * reset
 * Zero out any cookies being used to customize banner display (e.g. delivered impression count).

For example,


 * []
 * https://it.wikisource.org/wiki/Speciale:RandomRootpage?randomcampaign=0.142

Limitations
Banners do not display on pages in the  namespace, as well as edit pages and diff pages.

API
CentralNotice adds two API modules,  and. (The API module centralnoticeallocations was deprecated and removed in MediaWiki 1.25.)