2014-03-28 20:44:00 +00:00
|
|
|
{
|
2015-10-13 06:45:44 +00:00
|
|
|
"@metadata": {
|
|
|
|
|
"authors": []
|
|
|
|
|
},
|
|
|
|
|
"relatedarticles-title": "Related pages",
|
2016-01-22 12:23:08 +00:00
|
|
|
"relatedarticles-desc": "Adds a link to related pages on the sidebar or in the footer, if the user enables the beta feature.",
|
2016-02-16 14:21:46 +00:00
|
|
|
"relatedarticles-read-more-heading": "Related pages",
|
2016-02-10 20:41:01 +00:00
|
|
|
"relatedarticles-read-more-beta-feature-title": "Related pages",
|
2016-01-22 12:23:08 +00:00
|
|
|
"relatedarticles-read-more-beta-feature-description": "Suggests related pages at the bottom of a page."
|
Add Related Articles section to Minerva
If the page has related articles, is in mainspace, isn't the main page,
and the output is being rendered with the MinervaBeta skin then a
"Related Articles" section is added to the page just before the footer.
Separate loading the information necessary to render the pages, choosing
the renderer, and rendering the data so that multiple skins - currently
Minerva and Vector per the mocks - not just multiple resolutions can all
be handled the same way:
* The bootstrap script (ext.relatedArticles.readMore.bootstrap/index.js)
for fetches the page image and Wikidata description; loading the
renderer module; and, finally, notifying the renderer module that it
should render the data, which it does by emitting
"ext.relatedArticles.readMore.init" event using mw#track
* The Minerva renderer subscribes to the event and, when it's fired,
renders the data by passing it to the WatchstarPageList view
Bug: T113635
Change-Id: I651342bdf9796938fa7051828dd13bc6fe774783
2015-10-07 13:12:42 +00:00
|
|
|
}
|