collective.behavior.amp 1.0a3

Installation

To enable this package in a buildout-based installation:

1. Edit your buildout.cfg and add add the following to it:

[buildout]
...
eggs =
    collective.behavior.amp

After updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.

Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.

Check the box next to Accelerated Mobile Pages Support and click the ‘Activate’ button.

Usage

Go to ‘Site Setup’ and select ‘Accelerated Mobile Pages’; set the publisher logo and the AMP analytics code, if available.

Go to ‘Site Setup’ and select ‘Dexterity Content Types’ and enable the ‘Accelerated Mobile Pages’ in your content types. A new view named @@amp will become available in all instances of your content type. The view will display the logo of your site, a global navigation sidebar, and the main fields of your content type (including title, byline, resume, body text, and related items, if available); it will also include metadata as structured data.

Capture of analytics data from AMP documents is supported using the amp-analytics tag. Refer to the examples in Adding Analytics to your AMP pages for more information on how to use this feature.

If sc.social.like is installed, a list of social share buttons honoring the configured plugins will be displayed between the byline and the resume. Note that you have to enter a valid Facebook app_id if you want to enable the Facebook button.

How does it work

AMP is a way to build web pages for static content that render fast. AMP consists of three different parts:

AMP HTML

AMP HTML is HTML with some restrictions for reliable performance and some extensions for building rich content beyond basic HTML.

AMP JS

The AMP JS library ensures the fast rendering of AMP HTML pages.

Google AMP Cache

The Google AMP Cache can be used to serve cached AMP HTML pages.

This package adds an alternate view to display your content as AMP HTML page, and adds a link to it in the header of any other view:

<link rel="amphtml" href="${context/absolute_url}/@@amp">

The body text is processed to remove invalid elements or to replace them by the corresponding AMP components.

1.0a3 (2017-04-13)

• Fix i18n and update Brazilian Portuguese and Spanish translations (fixes #44). [hvelarde]

• Set correct language information (fixes #43). [hvelarde]

• Add support for the amp-sticky-ad tag. [hvelarde]

• Fix support for the <amp-analytics> tag. [agnogueira, hvelarde]

• Fix CSS error in logo position. [kakshay21]

• Avoid exception when related items relation is broken. [rodfersou]

• Fix loading order for main AMP script. [hvelarde]

• Add class for social icon <div> tag. [agnogueira]

• Move description to article header. [agnogueira]

• Do not fail if an image doesn’t have a src attribute, or if it was referenced inside the body text as an external resource. [hvelarde]

• Clean up invalid AMP HTML attributes (fixes #26). [rodfersou]

• Explicitly disable any Diazo theme on the AMP HTML view. [hvelarde]

• Use byline field (if present) to get the name of the content’s author. [hvelarde]

• Fix various exceptions raised when content has Archetypes based lead images. [hvelarde]

1.0a2 (2016-10-06)

• Fix exception on the AMP HTML view when content has no lead image. [hvelarde]

1.0a1 (2016-10-06)

• Initial release.