Donation data shows that more specific site names like "English Wikipedia" work better than generic ones like "Wikipedia" and we'd like to take advantage of that in interface texts. Since this is probably useful across many components and we don't want to limit it to Wikipedia, and other sites don't always need a language (e.g. Wikidata doesn't), or could be special in some way (e.g. en.wikisource is "English Wikisource", www.wikisource is "Old Wikisource"), we can't just lego together language and sitename in the affected messages. The best approach is probably a new magic word, {{FULLSITENAME}}.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | MMiller_WMF | T227728 [EPIC] Growth: Newcomer tasks 1.0 | |||
| Invalid | None | T236195 Newcomer tasks: create {{FULLSITENAME}} magic word |
Event Timeline
Comment Actions
@Tgr -- will we need this for v1.0? If so, I think it should be in Ready for Development.
Comment Actions
That's a product call. The existing code uses {{SITENAME}} (so just "Wikipedia" instead of "English Wikipedia").
I'd put it as a stretch goal - better to deploy without it than to not deploy because of it. So maybe the bottom of Ready for Development?
Comment Actions
@Urbanecm_WMF pointed out that this has been solved already via rEWMEf8e3cddd81b4: Add a list of human-readable localized project names.
Comment Actions
IIUC, this was solved in 2016, so doesn't need a Tech News mention now. I'm removing User-notice accordingly. Please clarify if I'm incorrect.