The AMP Project Roadmap
The ongoing development of AMP is conducted in working groups, each with knowledge or interest in a specific area of AMP.
To make their work visible to the community all groups provide regular status updates with details of what they have accomplished and what's up next.
All of the updates listed here are available as issues on GitHub and we'd love you to join the conversation there!
Select working groups
Performance
Status Update Wed Sep 01 2021What was accomplished
- did investigatory work for non amp team [internal]
Lessons Learned
What's Next
- get baseline performance numbers for amp-story
- possibly incorporate changes needed to accomodate stories requirement for SemiTransformedDocument
Performance
Status Update Tue Mar 02 2021What was accomplished
- fixed the new ts server not respecting the host and font when transforming the documents https://github.com/ampproject/amphtml/pull/33425
- ongoing work to support avif
Lessons Learned
What's Next
- additional font testing exploration focused on sub font and fallback font
Performance
Status Update Fri Jan 01 2021What was accomplished
- v0.js and extensions are now more resilient to double loading of the amp library (https://github.com/ampproject/amphtml/pull/31828)
- fixed module build bug where
AMP.requirewould sometimes not exist (caused by race condition https://github.com/ampproject/amphtml/pull/31988) - turned down module build to fix p0's
- added bento component generator
gulp make-component --bento --name=my-component
Lessons Learned
- separate out test features in isolated PR as they are hard to cherry pick if they are merged with runtime features/additions/removals