Cool! It would make the installation of MobileFrontned a lot easier for third parties (ok, I only talk about me :P), if this would be a composer module, but having it in it's own extension sounds reasonable nontheless! Best, Florian Gesendet mit meinem HTC ----- Nachricht beantworten ----- Von: "Sam Smith" <samsmith(a)wikimedia.org> An: "mobile-l" <mobile-l(a)lists.wikimedia.org> Betreff: [WikimediaMobile] Breaking apart MobileFrontend's front and back ends Datum: Di., Sep. 1, 2015 15:52 Hey all, I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin. Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally. My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly. My short-term goals are: * to *cover* the new extension in integration tests so that I can make structural changes * to get the unit tests passing without hitting the DB * to document the new extension thoroughly * to reduce the binding between the two extensions to exactly one call [2] * to get the extension deployed Cool? Cool! –Sam * Not a typo [0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions-MobileFrontend/blob/dd9e99e0…