Skip to content
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

Making pages amp compatible #130

Open
xRahul opened this issue Dec 27, 2017 · 3 comments
Open

Making pages amp compatible #130

xRahul opened this issue Dec 27, 2017 · 3 comments

Comments

@xRahul
Copy link
Contributor

xRahul commented Dec 27, 2017

Having amp ready pages will again be a boon for SEO. As the theme is minimal with non-existent dynamic content, we can make amp version of the pages for higher preference in mobile searches.
I have checked out some packages also like amp-jekyll. If we can incorporate them, we should do it.
I really like this theme and want to take it to the next level now! I guess going PWA route is too soon though. ;)

@migueldemoura
Copy link
Contributor

migueldemoura commented Dec 27, 2017

AMP is a double-edged sword, and one ought to be careful before jumping into it with both feet. Not to mention the obvious downsides, its only benefits are performance/latency and SEO.

Chalk is properly designed, and with a CDN is should match AMP's speed. As for SEO, it would certainly improve it, but unlike structured data (#129), the only reason for such increase is Google's apparent content prioritization.

In my opinion, and for those willing to accept the downsides, this could be offered as a option behind a config flag.

Edit: Much smaller comment :)

@xRahul
Copy link
Contributor Author

xRahul commented Dec 28, 2017

YEah, it was purely for SEO. I know making a web page amp-lified is an undertaking by itself, but having that lightning symbol in the search results would be quite good. I agree that it should be under config and turned on only if required. As there are many things that do not work in amp pages, user should have the option to choose.
Also, I was joking about PWA. I don't see why someone would need to make their blog an app. It would be an optional feature at most. Lets keep that shelved for now though.

@xRahul
Copy link
Contributor Author

xRahul commented May 21, 2018

I have added both PWA and AMP on my fork of Chalk. It looks great so far.
There are many changes that need to be done, but having AMP version of Posts would be good.
Ref: AMP post, Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants