-
Notifications
You must be signed in to change notification settings - Fork 14
Status Update February 2020
Greg Grothaus edited this page Feb 4, 2020
·
2 revisions
Previous Update: October 2019
-
AMP Packager Version 3.0 release. Google currently supports v1 - v3, but would prefer to increase the minimum supported version soon. Includes:
- bug fixes
- ACME certificate management in AMP Packager. Labelled experimental currently.
- self-signed certs in development mode
- health check endpoint
- Attendance at IETF 106. Discussed the Signed Exchange specification at the Birds of a Feather.
- Released SXG nginx module. Accepted into the nginx debian distribution.
- Progress on web packager and as a web server. Incomplete, expect completion by next status update.
- Provided analysis into CSS usage distribution in the AMP Cache to contribute to discussion about how to help publishers manage the CSS byte limit.
- Completed C++17 html parser implementation. Still working through the release process inside Google before adding this to github repo
- Java AMP Validator implementation contributed.
- Draft plan in progress for disentangling cache domain from publisher runtime.
- AMP Cache now provides image blurring on AMP documents as a placeholder until image network load.
- Rewrite of the AMP Cache URL Format doc to describe more accurately the way URLs are formed on the AMP cache.
- I2I for changes to AMP Cache URLs for a small fraction of origins to improve readability.
- Cloud-native implementation and deployment instructions for the AMP Signed Exchange Packager.
- Attend IETF 107.
- Open Source the C++17 implementation for use by AMP Email providers, AMP Caches, etc.
- Implement validator changes for on publisher self-hosting of AMP Javascript.
- Relax CSS byte limit.
- Implement I2I for improved AMP Cache URLs.
- Share draft plan for disentangling AMP Cache Domain from Google.
- Explore ways in which the AMP Cache can reduce the runtime validation requirements for Mustache Templates. #26544