As of release 2.11.0 of the Core Components, AMP - Accelerated Mobile Pages - are fully supported.
This document gives an overview of how AMP is supported as well as how to enable it for your sites. However for full technical details, please see the GitHub developer documentation.
Accelerated Mobile Pages or AMP is an open-source framework originally designed by Google to optimize pages for mobile browsing. AMP pages typically load much more quickly than standard web pages, offering better mobile experiences.
Support for AMP in the Core Components is fully configurable. AMP versions of pages can be served exclusively, alongside the standard HTML versions, or not at all.
The Core Components use amp
as a Sling selector to render an AMP page. For example example.html
would render the normal page and example.amp.html
would be the AMP version.
Individual projects can decide whether or not to leverage AMP. In fact, because AMP and standard HTML pages can be delivered in parallel, a project can choose to use AMP on only certain pages of the project.
Although AMP support offers a great deal of flexibility, to get started with it quickly requires only a few simple steps:
To enable AMP for a page, the AMP Mode must be selected in the Page Policy.
The AMP settings for a page can also be overridden in the Page Properties for an individual page.
When using AMP with the Core Components, the main difference is that AMP requires all CSS to be inlined in the <head>
element as well as optimized.
To support this, a customized page component is used, which loads just the AMP-specific CSS for components present on the page.
Due to AMP design limitations Adobe does not support the use of the Responsive Grid with the AMP version of your page.
For further requirements and technical details, please see the GitHub developer documentation.