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 Sat Apr 02 2022What was accomplished
- created document for render blocking font loading
- added render blocking font loading classes (to be reviewed)
Lessons Learned
What's Next
- additional monitoring for server services
- amp e2e use mjs files
- design document for version locking alternate binaries (such as ones without css in the JS binary)
Performance
Status Update Fri Apr 01 2022What was accomplished
- amp story translations server changes design document
- amp-story request transformer changes to handle translation language fallback
Lessons Learned
What's Next
- amp e2e use mjs files
- design document for version locking alternate binaries (such as ones without css in the JS binary)
Performance
Status Update Tue Jan 04 2022What was accomplished
- 🚀 Launched amp-story inlining css experiment.
- 🐛 Fix "latestVersion" bug in amp-toolbox.
- 🧪 Created tests for
amp-toolboxAmpStoryCssTransformer in regards to LTS. - 💅 Add TS to Core and Bento.
- 🚀 Migrated build system to esbuild.
- 🐛 Fixes for AMP LCP for various LCP issues in amp-analytics.
What's Next
- Manual testing for amp-geo experiment
- Amp cache url rewriting code in amp-toolbox
- Typechecking more Bento directories
- WASM Jolt prototype
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