-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Document what AMP prerendering means #1353
Comments
+1 |
cc @jmadler |
Just checking, was there any progress on this that hasn't been documented here yet? |
@cramforce - Can you elaborate? Is this more than the general info at loads pages in an instant? If there are specific properties and guarantees, where can I find those details? |
I think that is basically it, but it would be good to iterate on it a bit. Maybe @pbakaus has a text somewhere that is a bit more coherent than my mumbling. |
I sadly don't have a better write up, but maybe makes sense to steal some stuff from https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exist/ as well. |
In addition to speed/CPU/data benefits mentioned in Load pages in an instant, it would also be good to mention how AMP correctly handles privacy related mechanisms in prerendering mode e.g., no tracking/analytics/no ads etc. |
Any updates here?Thanks |
will look @ in: Q2 |
What the properties and guarantees are.
This would be helpful to have in many discussions and a good doc for new AMP developers (people working on AMP, not with AMP).
The text was updated successfully, but these errors were encountered: