Wikimedia Developer Summit/2016/T114542

T114542 - This is the session pad for the Next Generation Content Loading and Routing session, slated to begin at 10am on Monday, January 4.

Purpose
An attempt to identify and resolve disagreements and misunderstandings in the following areas:
 * T114542 - Next Generation Content Loading and Routing, in Practice - Adam Baso
 * T111588 - API-driven web front-end - Gabriel Wicke
 * T106099 - Page composition using service workers and server-side JS fall-back - Gabriel Wicke

Agenda

 * 20 minutes - introductory presentation: Next Generation Content Loading and Routing - Adam Baso, Jon Robson, Joaquin Hernandez, Gabriel Wicke, Sam Smith
 * 60 minutes - open discussion

Etherpad
https://etherpad.wikimedia.org/p/WikiDev16-T114542

Goals
Please fill in this section during the course of the meeting discussion starts to clarify these anwers:
 * Which stakeholders will likely benefit from an API-driven UI approach?
 * Which stakeholders will be negatively impacted by an API-driven UI approach?
 * What alternatives should we consider for API-driven UI?
 * Single-page application
 * ServiceWorker composition
 * (any others?)
 * For each approach, what functionality would need to be reimplemented? Who is responsible for making the change?
 * For each approach, what functionality would need to be dropped? Which stakeholders care?
 * For each approach, what functionality would need to be reimplemented? Who is responsible for making the change?
 * For each approach, what functionality would need to be dropped? Which stakeholders care?

Chronology
''This section is where an attempt is made to capture the gist of who said what, in what order. A transcript isn't necessary, but it's useful to capture the important points made by speakers as they happen.''
 * (speaker): (important point they made)