Full site being migrating to AMP. I want to integrate admin functionality to AMP pages, like simple links for deleting content, and huge forms(not mobile friendly) for editing content. It will be visible after login, and non mobile content will be in iframes(to not broke AMP, as incompatible). In other words I want single, same pages for user and admin front-end - AMP pages what will work on any device for user, and same AMP pages for admin what will require desktop screen, where admin actions performed in pop-up windows(iframes in lightbox). What should I do, to make this correctly:
- password protect admin version of page - in other words page will be different depending on session cookie,
- make absolute links to admin items, not relative, full url including my domain, to avoid hit cached content? Do Google change relative links when caching AMP or not touch it at all?
- Make different headers, allowing cache page by headers with user content(and login form), and disables cache by http headers for logged in admin? Is it really needed?
Something I miss? Will it work as expected? Is it a good way, in case separate admin area not worth developing, and not desirable?
Will Google do cache pages in AMP cache even with preventing cache-control headers? Are different cache-control headers needed for default page and for 'logged in' page?