Closed tobie closed 3 years ago
Assuming the SXG path, the biggest issue seems to be about the amount of effort (other costs) it takes to deploy SXG versions of the AMP content. Not every publisher can roll out a DIY solution.
Support via CDN is an approach that is known to address the problem (i.e. publishers who are using CloudFlare didn't have these concerns). So, one goal could be to get more support from CDNs.
There are likely other leverage points to consider too and we could also identify how to lower the cost of a DIY solution, e.g. automating various aspects such as SXG certificate management.
Related Jamboard for Brainstorming: https://jamboard.google.com/d/1gDMTMn_ywDkCZzHTMSdrhtrI0UTb_OrnSJ984ZdCNzI/viewer?ts=5e29bc85
I did a pass on the Jamboard (blue post-it notes).
A few question ahead of the next meeting:
I hope this will seed an interesting discussion. Stay safe!
Display the publisher's URL in the address bar, not the cache's. How can we make it easier to have the right outcome?
@ampproject/ac: the goal of this issue is to define what we want to achieve in 2020 for that focus area. Please comment below with you suggestions regarding that topic.
Next Steps:
See all URLs issues