amp-follow-up-notes.md

Does AMP provide guidance on what we can do on the site to get speed gains?

Can we learn from AMP to do some of the things they suggest?

• Need to include AMP.js library
• Needs to be styled with AMP
• Looks like it's a specification for complying with their framework,

being cached and featured. We couldn't get this on our own

How would Google treat dictionary entries?

Weird to give content to someone else to have them host and control it.

• My impression is that everything gets styled the same

How would this affect analytics (esp. server side)?

• Looks like they have their own analytics method and it plugs into our Google Analytics
• We would need to recreate our server side analytics (test_groups) on there
• faq analytics

How would this affect cookies?

• may be available at the time of the Authorization and Pingback requests
• only for internal mapping
• no guarantees to read or write cookies given all platforms
• "Reader ID" is calculated by them an guaranteed to work
• Reader ID and server-side storage.

Can we control who sees AMP?

Auth endpoint

• Authorization endpoint provided called by AMP Runtime or Google AMP Cache
• Credentialed CORS endpoint
• Access parameters that can be used by Markup to hide or show parts of document

Redirect

• We could identify the location in nginx, we could proxy to another app
• We could also do this in neodarwin

What would it do to our metrics?

• No answer

Anything in Ghost?

• No, we would have to build our own
• This would involve changing ghost core
• We could plan it as a reusable module/app for others to use

A/B testing

Doesn't look possible with AMP articles