Closed moul closed 8 months ago
@iuricmp will take a look how the web site is using AMP and if we need it.
To remove Google AMP we need to replace all the amp components in favor of native ones.
amp-*
(around 800 occurrences) components and switch to native ones.I don't see any benefit in doing this right now. I vote to close this issue.
OK. If we keep AMP, what do you think about the related issue https://github.com/berty/www.berty.tech/issues/152 ?
It should be ok once the website doesn't have the #152 button anymore.
Will ask @moul if it's still relevant to remove AMP.
Closing this since it is not more relevant, according to the reporter.
The idea is to keep the good practices that come with google AMP, but remove the trigger that forces to be 100% consistent + that says to google “hey, you can AMPize my website in your cache”
So, if I’m not wrong, just remove the :zap: from the HTML head, but it needs to be double-checked
Clearly, I don’t like being in the Google cache system, and I don’t like having warning because of the limitations introduced by AMP, but it’s by far, my current favorite good practice handbook in term of performances, and organization
hint: pretty sure that there are blogposts explaining how other people made the same thing