-
Notifications
You must be signed in to change notification settings - Fork 30
Delete AMP #14534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete AMP #14534
Conversation
|
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
ioannakok
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how thorough we can be but I can still find references to AMP in the codebase.
Also, should the decision to stop supporting AMP be documented? Has it already been somewhere? https://github.com/guardian/dotcom-rendering/blob/main/dotcom-rendering/docs/architecture/011-amp.md
Approving - these are just some non-blocking thoughts
Co-authored-by: Ioanna Kokkini <ioannakok@users.noreply.github.com>
Great spot thanks! I've updated. I think it's going to be a case of whack-a-mole to find all the 'live' references to AMP |
Very good point. I will create an ADR for it. |
…000-structure-for-initial-milestone-amp.md
2023379 to
44723c8
Compare
What does this change?
Delete AMP
Why?
We no longer render any content on AMP
ADR:
https://github.com/guardian/dotcom-rendering/blob/44723c8da0b825c2cb8b53540a34c29bf7f5695f/dotcom-rendering/docs/architecture/030-amp-removal.md