The AMP team actually got up on stage and tried to tell a bunch of developers that sites could be converted in a couple of hours. Worst developer outreach I’ve ever seen.
I work for a major news publisher. Rendering is tied to legacy systems with esoteric business logic, journalists could embed any one of hundreds of first or third party embeds, and many pieces of content embed arbitrary HTML directly. It seems crazy, but this is how a lot of news organisations are dealing with content.
AMP is designed to fail on any error, is incompatible with existing HTML and CSS, and to do CSS inlining right means completely rewriting existing build pipelines.
In a Google world implementing AMP wouldn’t be that hard; code is generally high quality and you control the stack. In media organisations responsibility for domains might extends between different (poorly communicating) teams and many critical components are handled by third party systems. Doing something simple like implementing AMP’s custom CORS logic was a nightmare.
Building an AMP site is not hard. Building an AMP site that runs on legacy publishing systems IS hard. This is something the AMP team should understand, but they seem incapable of accepting any sort of feedback.
I work for a major news publisher. Rendering is tied to legacy systems with esoteric business logic, journalists could embed any one of hundreds of first or third party embeds, and many pieces of content embed arbitrary HTML directly. It seems crazy, but this is how a lot of news organisations are dealing with content.
AMP is designed to fail on any error, is incompatible with existing HTML and CSS, and to do CSS inlining right means completely rewriting existing build pipelines.
In a Google world implementing AMP wouldn’t be that hard; code is generally high quality and you control the stack. In media organisations responsibility for domains might extends between different (poorly communicating) teams and many critical components are handled by third party systems. Doing something simple like implementing AMP’s custom CORS logic was a nightmare.
Building an AMP site is not hard. Building an AMP site that runs on legacy publishing systems IS hard. This is something the AMP team should understand, but they seem incapable of accepting any sort of feedback.