Accelerated Mobile Pages and concrete5
Permalink
I have a client who is requesting a site designed from the ground up on the AMP HTML model:
http://www.ampproject.org/
The site will need a slew of add ons and it will be version 5.6. Does anyone have any experience with AMP to know the pitfalls. On the surface it seems pretty straightforward but the add on may have to be modified to conform to the requirements.
On their site they mention all the wonderful companies backing this project, but I've yet to find ONE that actually implements it.
http://www.ampproject.org/
The site will need a slew of add ons and it will be version 5.6. Does anyone have any experience with AMP to know the pitfalls. On the surface it seems pretty straightforward but the add on may have to be modified to conform to the requirements.
On their site they mention all the wonderful companies backing this project, but I've yet to find ONE that actually implements it.
There is a current discussion on the pros and cons of AMP and how it might be used in concrete5:
https://www.concrete5.org/community/forums/chat/google-amp-html-supp...
AMP implementation using concrete5 looks very involved and the existing implementation by community member hissy does not support 5.6.
https://github.com/hissy/concrete5-amp...
When using Google on a mobile device, AMP results now show up at the top of the results. Many large scale sites have adopted it, examples being Forbes, TNW, TechCrunch, and NewsWeek.
Since AMP is designed to provide lightweight and fast loading pages, the alternative would be careful creation of a lightweight theme, only using certain blocks, making lightweight custom blocks, create a performance budget, educate the client on how to keep the page content to a minimum size, and use aggressive caching like Varnish.