An overview of this topic was presented toward the end of a session at Wikimania 2015.
We now have a number of different proposals for revamping navboxes and infoboxes:
- A wikia-inspired design for a specialized infobox editor
- An implementation from the mobile team
- Content Widgets
- T114251: [RFC] Magic Infobox implementation
The goal of this task is to separate out infoboxes and navboxes from article content, and to provide fluent editors for them. This would allow mobile (for example) to more easily tweak the presentation of infoboxes, without having to parse the article content, recognize them, and pull them out. A desirable side-effect is to make it more routine to source data and label texts for infoboxes/navboxes from wikidata, so that they can be shared among wikis in different languages. An extensible design would allow a local wiki to inherit most of an infobox, but still override, delete, or add fields, to empower local editors and account for political sensitivities.
A key component could be T107595: [RFC] Multi-Content Revisions, which has proposed a new content model for articles in core which would allow storage of infoboxes/navboxes separate from the article content.
- Leave with a unified plan for the future of infoboxes and navboxes, including buy-in from wikidata, the mediawiki-core team (for storage separate from article content), mobile (to replace their current display hacks), editing (to create the necessary tools), and analytics (to ensure that infoboxes remain easy to edit, but not significantly easier to vandalize).
This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey
This proposal received 49 support votes, and was ranked #16 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Wikidata#Make_it_easy_to_build_infoboxes_that_display_information_from_wikidata