I'm of fairly mixed opinion. It can be worthwhile for performance and limitation of external assets (scripts, making ads behave) and certainly makes for a content-centric page with fast page load times, but it can sure be fiddly.
Three months ago I switched my blog's format to one that implements a lightly modified version of Amplify for Jekyll. It took a while with a surprising amount of migrating data (there's always something that got missed) and reimplementing anything remotely JavaScript related into some godawful iframe based hacks; Disqus comments and gist embeds, for example. I still will never have my site 100% AMP compliant, as I want to keep a search page, which I'm not going to bother putting through an iframe hack.
On the upside, I've got an incredibly fast blog format, which makes use of virtually no JavaScript, making for an immensely fast page load. My site can load from the Google AMP CDN if it's clicked on from a mobile device via Google search result, but otherwise my page loads natively from GitHub Pages and has no redirects to the CDN version, as I went in whole-hog. The focus is the content and that's what any readers get. I also don't see the banner at the top of my pages, including when loaded from the AMP Project CDN on mobile; at least, not when navigating directly (cdn.ampproject.org/c/s/my.com, versus loading from a Google search result will display it, from google.com/amp/...).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm of fairly mixed opinion. It can be worthwhile for performance and limitation of external assets (scripts, making ads behave) and certainly makes for a content-centric page with fast page load times, but it can sure be fiddly.
Three months ago I switched my blog's format to one that implements a lightly modified version of Amplify for Jekyll. It took a while with a surprising amount of migrating data (there's always something that got missed) and reimplementing anything remotely JavaScript related into some godawful iframe based hacks; Disqus comments and gist embeds, for example. I still will never have my site 100% AMP compliant, as I want to keep a search page, which I'm not going to bother putting through an iframe hack.
On the upside, I've got an incredibly fast blog format, which makes use of virtually no JavaScript, making for an immensely fast page load. My site can load from the Google AMP CDN if it's clicked on from a mobile device via Google search result, but otherwise my page loads natively from GitHub Pages and has no redirects to the CDN version, as I went in whole-hog. The focus is the content and that's what any readers get. I also don't see the banner at the top of my pages, including when loaded from the AMP Project CDN on mobile; at least, not when navigating directly (
cdn.ampproject.org/c/s/my.com, versus loading from a Google search result will display it, fromgoogle.com/amp/...).