Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Amp Optimizer Beta release Roadmap !!!
Hi, Thanks for working on the module. Is there a Roadmap for a beta or stable release? I am proposing a few ideas of my own. Once agreed upon we can also open dedicated Issues for it.
TBD
Limit only for the Html renderable requests by using the render api instead of the events apiDisable amp optimizer for logged in users as its not cached or crawled by searched engines.- Tests
- Documentation
Issue fork amp_optimizer-3194432
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
voleger1. The possible way is to move the optimizing method call to the #post_render callback stack of html render element. But the problem is that is never performing the #post_render callbacks for html render elemement. So I decided to keep the approach (using event subscriber), but use best practice to limit the response cases which need to be optimized. See similar implementation in minifyhtml module https://git.drupalcode.org/project/minifyhtml/-/blob/8.x-1.x/src/EventSu...
2. This is doable by introducing an earlier check of the user status.
3. Tests will require the testing module which implements the controller with testing AMP response. Then we can cover some specific test cases of integration. The library which used by this module is well tested itself.
Comment #4
volegerCurrent changes are enough to publish beta stability level release.
Comment #6
volegerNow the target is to release a stable release.
Comment #7
kneek commentedThis works great now , thanks !