[docs] [workflows] Implementing Google Amp

[brolag]

Part of the Top 25 Learning Workflows initiative. See #13708 for the meta issue that this issue falls under.

User story

As a new Gatsby user, I want to implement Google AMP.

Evaluation

[Change emoji below based on your evaluation.]

Search	Discover	Complete	Linked	Tone	Style	Overall
😄	😞	😐	😄	😐	😐	😐

Steps taken to implement

1. Searchability
   i. Searched gatsby implement google amp; clicked first result.

2. Discoverability
   i. Searched google amp in search bar but didn't find the package link.

3. Completness
   i. Followed steps in Gatsby Plugin Amp
   ii. Installed Gatsby Plugin Amp
   iii. Replaced Img component with amp-img
   vi. Success!
   Notes: no tall tags are completed and documented.

4. Linked
   i. Link to general information about Google AMP.
   ii. Link to analytics types.
   iii. Available components link is broken.
   iv. Link for Google Analytics Client ID tutorial.

5. Tone
   i. Very technical tone for options section and caveats section.

6. Style.
   i. Minor issues only such as periods at ends.

7. Overall
   i. Not all tags are completed however plugin documentation is very self explanatory, it requires previous AMP knowledge.

Recommendations

• Provide examples for YouTube, Twitter and iframe, like it is described for amp-img.
• Fix end of paragraph punctuation.
• Try Google Analytics, YouTube and Twitter implementations.

Feel free to edit this issue with more results about other HTML tags.

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!

[marcysutton]

Reopening this as the workflow evaluation still needs to be implemented. Thanks so much for opening this issue!

[joyfulelement]

There had been discussions on #13454 about the proposed requirement, POC experiments and action items on how Gatsby could provide first-class support for Google AMP.

As much as myself also looking for information about how to support Google AMP with Gatsby, correct me if I am wrong, but base on what I understand on people's prior attempts with various plug-ins such as gatsby-plugin-amp mentioned by @brolag, gatsby-plugin-google-amp and gatsby-plugin-html2amp, there are still work to be done in Gatsby core or plug-ins in order to complete the support for Google AMP.

I believe this would continue block the recommended docs items until there is a clear path on how Gatsby decide to support Google AMP. Any idea if this is still on Gatsby's current roadmap @marcysutton? while AMP continue to evolve, which is also supported by Next a year ago. Thanks.