ampproject / ampproject/amphtml

I2I: Deployment and serving of AMP via Cloudflare

Open
#36,152 9 comments 2 reactions 0 assignees View on GitHub
INTENT TO IMPLEMENT P1: High Priority Stale WG: caching WG: Caching: Triaged WG: infra
Dominant language
JavaScript
Stars
14.9k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

### Summary

This I2I discusses the concrete steps and timeline for performing the disentangling of the AMP runtime CDN and the Google AMP Cache.

#### Implementation guidelines — * * * _this is the thing that needs reviewing in this I2I_ * * *
https://docs.google.com/document/d/1QD0SBwgmZxrvJTpv68ytTI2oKxq4EOi-mkSCKm2JTPc/edit

### Design Document

Design document with analysis of alternatives considered, privacy, and security consideration: https://docs.google.com/document/d/1IMfhVgxCRW0Cq1N7xvflfcoxGdnVshvA92je_wDxAY0/edit

### Motivation

- https://github.com/ampproject/wg-caching/issues/13
- Public announcement of intent: https://openjsf.org/blog/2021/08/13/an-update-on-how-amp-is-served-at-the-openjs-foundation/

### Alternative Solutions

- See **design document** above for alternatives considered with respect to the goal
- See **implementation guidelines** above for alternatives considered with respect to the implementation details

### Launch Tracker

https://docs.google.com/spreadsheets/d/1QL42wafo1jODim8EN5HujEbxw12EeG-trGECnbzDjQA/edit

### Notifications

/cc @ampproject/wg-infra @ampproject/wg-performance @ampproject/wg-security-privacy @ampproject/wg-caching @ampproject/wg-foundation-onboarding @ampproject/tsc

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.