AMP

Name: AMP
Author: AMP Project Contributors

Plugin

by AMP Project Contributors meteorgpl-plugin/amp latest 1.5.4, 6 years ago

Watch 0 Star 0

Install

composer require meteorgpl-plugin/amp

Register the repository once per project: composer config repositories.meteorgpl composer https://composer.meteorgpl.com

"meteorgpl-plugin/amp": "^1.5"

composer config --global http-basic.composer.meteorgpl.com token <your-token>

Create tokens on your tokens page; in CI use COMPOSER_AUTH.

Official AMP plugin, supported by the AMP team. Formerly Accelerated Mobile Pages, AMP enables great experiences across both mobile and desktop.

0 stars
0 watching
0 downloads
GPL-2.0-or-later

Versions 2

Newest first · every version scanned before publication

Detailed Basic

1.5.4 Latest Jun 23, 2020

311 files 694.0 KB 329 changed +60,654 −13,101 Verified
0.7.2 Jun 27, 2018

Prevent plugins from outputting custom scripts in classic templates via wpprintscripts action. See #1225, #1227. Props westonruter. Release notes

108 files 203.7 KB Verified

Show 17 versions not available yet

Releases named in the vendor’s changelog or on WordPress.org that the repository does not have yet.

2.5.5 Not available yet Apr 10, 2025

Released on WordPress.org
0.7.1 Not available yet May 23, 2018

Limit showing AMP validation warnings to when amp theme support is present. See #1132. Props westonruter.

Changelog entry
0.7.0 Not available yet May 3, 2018

Render an entire site as "Native AMP" if the theme calls addthemesupport( 'amp' ). See #857, #852, #865, #888. Props westonruter, kaitnyl, T...

Changelog entry
0.6.2 Not available yet Feb 28, 2018

Improve logic and use of escaping; limit flushing rewrite rules to only when supportedposttypes change. See #953. Props philipjohn, westonru...

Changelog entry
0.6.1 Not available yet Feb 9, 2018

Version bump to re-release plugin in order to deal with missing file in 0.6.0 release package that caused fatal error.

Changelog entry
0.6.0 Not available yet Jan 23, 2018

Add support for the "page" post type. A new page.php is introduced with template parts factored out (html-start.php, header.php, footer.php,...

Changelog entry
0.5.1 Not available yet Aug 17, 2017

Fix: issues with invalid tags not being stripped out (e.g. script tags) (h/t tmmbecker, fahmi182, pppdog, seejacobscott, RavanH, jenniejj, l...

Changelog entry
0.5 Not available yet Aug 4, 2017

Whitelist Sanitizer: Replace Blacklist Sanitizer with a whitelist-based approach using the AMP spec (props delputnam)

Changelog entry
0.4.2 Not available yet Oct 13, 2016

Fix: Prevent validation errors for html tag (h/t Maxime2 and everyone else that reported this error)

Changelog entry
0.4.1 Not available yet Oct 10, 2016

Fix: Don't fire thecontent for featured image output

Changelog entry
0.4 Not available yet Oct 6, 2016

New template: spiffy, shiny, and has the fresh theme smell (props allancole and the Automattic Theme Team).

Changelog entry
0.3.3 Not available yet Aug 18, 2016

Handle many more validation errors (props bcampeau and alleyinteractive).

Changelog entry
0.3.2 Not available yet Mar 4, 2016

Jetpack Stats support.

Changelog entry
0.3.1 Not available yet Feb 24, 2016

Allow custom query var (props vaurdan).

Changelog entry
0.3 Not available yet Feb 18, 2016

Fetch dimensions for hotlinked images.

Changelog entry
0.2 Not available yet Jan 28, 2016

Lots and lots and lots of compatibility and validation fixes

Changelog entry
0.1 Not available yet Release date not stated

Initial version

Changelog entry

A specific version: composer require meteorgpl-plugin/amp:<version> Full changelog

Readme

GPL-2.0-or-later

AMP

Official AMP plugin, supported by the AMP team. Formerly Accelerated Mobile Pages, AMP enables great experiences across both mobile and desktop.

The AMP Project is an open-source initiative aiming to make the web better for all. AMP enables web experiences that are consistently fast, beautiful and high-performing across distribution platforms. AMP formerly stood for “Accelerated Mobile Pages”, but now works completely across desktop and mobile. The official AMP plugin for WordPress supports fully integrated AMP publishing for WordPress sites, with robust capabilities and granular publisher controls.

Features and capabilities provided by the plugin include:

AMP-first Experiences: enabling full-site AMP experiences without sacrificing the flexibility of the platform or the fidelity of content.
Core Theme Support: enabling AMP compatibility for all core themes, from Twenty Ten all the way through Twenty Twenty.
Compatibility Tool: when automatic conversion of markup to AMP is not possible, debug AMP validation errors with detailed information including the invalid markup and the specific components responsible on site (e.g theme, plugin, embed); validation errors are shown contextually with their respective blocks in the editor.
CSS Tree Shaking: automatically remove the majority of unused CSS to bring the total under AMP's 75KB limit; when the total after tree shaking is still over this limit, prioritization is used so that the all-important theme stylesheet important is retained, leaving less important ones to be excluded (e.g. print styles).
Server-side Rendering: integrated PHP-port of the AMP Optimizer providing automated server-side rendering of AMP pages, drastically improving the Last Contentful Paint (LCP) metric.

Please note that the Stories experience has been removed from the AMP plugin in favor of the feature being released as a standalone plugin. It will be available soon!

The plugin can be configured to follow one of three different template modes: Standard, Transitional, and Reader. In Standard mode you use AMP as the framework for your site, and there need not be any separate AMP and non-AMP versions. When configured to operate in Reader and Transitional modes, a given page will have a canonical URL as well as a corresponding (paired) AMP URL. The AMP plugin is not serving as a mobile theme; it does not redirect mobile devices to the AMP version. Instead, the AMP version is served to mobile visitors when they find the content on platforms such as Twitter, Pinterest, Google Search, and others. Reader mode only supports serving AMP for singular posts, pages, and other post types, whereas Standard and Transitional mode support serving the entire site as AMP.

With the official AMP plugin for WordPress, the WordPress ecosystem is provided with the capabilities and tools it needs to build world-class AMP experiences without deviating from its standard, flexible, and well-known content creation workflow.

What it adds

WP-CLI: amp, amp validation

Installation

Upload the folder to the /wp-content/plugins/ directory.
Activate the plugin through the 'Plugins' menu in WordPress.
If you currently use older versions of the plugin in Reader mode, it is strongly encouraged to migrate to Transitional or Standard mode. Depending on your theme/plugins, some development work may be required.

Faq

Please see the FAQs on amp-wp.org. Don't see an answer to your question? Please search the support forum to see if someone has asked your question. Otherwise, please open a new support topic.

Screenshots

In the website experience, theme support enables you to reuse the active theme's templates and stylesheets; all WordPress features (menus, widgets, comments) are available in AMP.
All core themes are supported, and many themes can be served as AMP with minimal changes, Otherwise, behavior is often as if JavaScript is turned off in the browser since scripts are removed.
Reader mode templates are still available, but they differ from the active theme.
Switch from Reader mode to Transitional or Standard mode in AMP settings screen.
Standard mode: Using AMP as the framework for your site, not having to maintain an AMP and non-AMP version. Mobile and desktop users get same experience.
Transitional mode: A path to making your site fully AMP-compatible, with tools to assist with debugging validation issues along the way.
Make the entire site available in AMP or pick specific post types and templates; you can also opt-out on per-post basis.
Plugin checks for AMP validity and will indicate when: no issues are found, new issues need review, or issues block AMP from being served.
The editor will surface validation issues during content authoring. The specific blocks with validation errors are indicated.
Each Validated URL shows the list of validation errors encountered, giving control over whether invalid markup is removed or kept. Keeping invalid markup disables AMP.
Each validation error provides a stack trace to identify which code is responsible for the invalid markup, whether a theme, plugin, embed, content block, and so on.
Styles added by themes and plugins are automatically concatenated, minified, and tree-shaken to try to keep the total under 75KB of inline CSS.
A WP-CLI command is provided to check the URLs on a site for AMP validity. Results are available in the admin for inspection.

Install

composer require meteorgpl-plugin/amp

The vendor’s license checks are intact: activate the plugin in WordPress with a license key bought from the vendor.

License

Declared license: GPL-2.0-or-later. The code is redistributed under the license the vendor declared in the plugin’s own headers. License profile: gpl-full.

Artwork, fonts, media and documents that may be licensed separately are not redistributed; the licensing page explains what is replaced or removed, and the security tab lists it per version. Support and update entitlement come with the license you buy from the vendor.