-
-
Notifications
You must be signed in to change notification settings - Fork 450
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
Use AMP for blog pages #1027
Comments
@tlienart Should we have a franklin label for improvements to Franklin? |
But... isn't AMP evil? 🙀 Jokes aside, @ViralBShah yes a label sounds good, and I can link to relevant issues. Re AMP-ifying, I don't know what's involved, at what stage (pre or post build) or how easy this is so I need to do some research. Note: #1022 is kind of the same thing |
:-) Added a few |
So from a short amount of research it looks really easy to do, it's mostly a templating thing where you add specific stuff on the pages so that Google can cache them more easily (https://amp.dev/documentation/guides-and-tutorials/start/create/basic_markup/?referrer=ampproject.org) I'll try to give that a shot soon for blog pages. |
AMP is no longer necessary to achieve the carousel, and there may no longer be any benefit to using AMP. From a recent Google update:
I first learned about this from a (highly editorialized) post on the Plausible blog. |
Great! |
Our blog pages are simple enough that it seems like it should be trivial enough to AMP-ify them, which would make them eligible to appear in the top carousel of search results.
The text was updated successfully, but these errors were encountered: