We are looking for ways of improving the handling of common content structures like infoboxes, data tables, citations or navboxes. We'd like to
- make their rendering more adaptable to different devices and use cases,
- improve the editing experience, and
- support the integration of different data sources.
An idea that was discussed several times recently is the concept of **page components**, data-driven widgets that improve on template-based solutions. Wikia are working on similar ideas (see below), focusing on infoboxes.
This task is intended to collect resources in this area, and serve as a starting point for the discussion. Please update the task description with more information.
## See also:
- Declarative infoboxes at **Wikia**: The Wikia folks are gradually replacing infobox templates with widgets, by replacing top-level infobox templates with an <infobox> tag extension wrapping an XML infobox definition. They are doing this in cooperation with the community, and provide migration tools based on heuristics on template parameters and typical values (ex: parameters whose value normally starts with Image: are rendered as images). The primary focus is on moving towards a declarative infobox widget definition, as a first step towards inline editing and flexible styling across different devices.
- [Announcement thread](http://community.wikia.com/wiki/Thread:841717)
- [Interactive edit / preview tool](http://infoboxpreview.appspot.com/) built by @inez.
- [Wikidata-generated infoboxes](http://git.wikimedia.org/blob/mediawiki%2Fextensions%2FMobileFrontend.git/2e992fd1c8e4a22c57f3913fb67f6bce42d6f582/resources%2Fmobile.infobox%2FInfobox.js) by @jdlrobson
- https://www.mediawiki.org/wiki/Parsoid/Content_widgets: Older notes from the Parsoid team
- https://www.mediawiki.org/wiki/Parsoid/DOM_notes: Parsoid notes on self-contained templates and content model constraints