An overview of this topic was presented toward the end of a [session at Wikimania 2015](https://wikimania2015.wikimedia.org/wiki/Submissions/Templates_are_dead!_Long_live_templates!).
We now have separate different proposals for revamping navboxes and infoboxes:
* [A wikia-inspired design for a specialized infobox editor](https://wikimania2015.wikimedia.org/w/index.php?title=File:Templates_are_dead!_Long_live_templates!.pdf&page=45)
* [An implementation from the mobile team](https://wikimania2015.wikimedia.org/w/index.php?title=File:Templates_are_dead!_Long_live_templates!.pdf&page=41)
* [Capiunto/Wikidata](https://wikimania2015.wikimedia.org/wiki/Submissions/Making_Infoboxes_easier_to_edit_and_maintain_with_the_help_of_Wikidata)
* [Content Widgets](https://wikimania2015.wikimedia.org/w/index.php?title=File:Templates_are_dead!_Long_live_templates!.pdf&page=48)
In addition, @brion has proposed a new content model for articles in core which would allow storage of infoboxes/navboxes separate from the article content. 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. [@brion
We should try to leave the summit with a unified plan for replacing/revamping 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).
(@brion, if I've misattributed or misdescribed the "article is a collection of items" idea, please feel free to correct and/or elaborate.)