# How about Discourse Support Google AMP? **URL:** https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697 **Category:** Feature **Created:** [2 Dicembre 2016, 4:42pm UTC](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697 "2016-12-02T16:42:57Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![purldator](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@purldator](https://meta.discourse.org/u/purldator) #### Post date: [4 Dicembre 2016, 6:39pm UTC](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697/5 "2016-12-04T18:39:48Z")
I like this answer, for I see Discourse’s devs on par with Google themselves. Understanding [AMP’s mechanisms of action, their parts, how they work together, flow](https://github.com/ampproject) then becomes a blueprint for Discourse; by adding these little JavaScript parables and lessons to their own Ember.js foundation. Sam, you already do this behavior elsewhere and for the same reason as I stated above. You did it by [creating launcher](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205) in lieu of using Docker Compose. This be only a suggestion–one that, if taken, can be tackled over time (as you all do well already in other areas) and improve Discourse’s perf: the reason. `*smile*` --- _[View the full topic](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697)._