[docs][tutorial] building a source plugin tutorial

[marcysutton]

Summary

Build a “real” source plugin that fetches data from a remote API and each step adds a new feature, e.g. caching, remote images, foreign key relationship, etc. The goal is to show some specific topics that aren't already covered in the Pixabay Source Plugin Tutorial, such as foreign-key relationships, set plugin status, handling caching, linking and transforming nodes to some content type, and more.

Motivation

To support people building integrations with Gatsby, we want a solid plugin authoring tutorial in addition to what's on the Gatsby docs.

[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/contributefor more information about opening PRs, triaging issues, and contributing!

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

[marcysutton]

Hey @DSchau, there's a related issue to the plugin authoring stuff that may be worthwhile to include as part of this work: #8697

[marcysutton]

Hey @DSchau and @amberleyromo, how's this going?

[marcysutton]

Learning is going to take this over. Internal doc with more details: https://docs.google.com/document/d/1U8U7lQgsHWjMBuzvG0lpX3JiiDJ5QMHBBHMmcMYFPyk/edit#

[laurieontech]

Hey @gillkyle is this content covered in the plugin workflow? Do we need both issues?

[gillkyle]

Yeah true, I do have this listed on the workflow evaluation. The other issue (#20232) is getting pretty close, and the content covered here is one of the last things to get taken care of. I think I'll close the other issue and we can instead focus on this one to narrow the scope a little.

[marcysutton]

There's a meeting next week to discuss plugin authoring material for first-class integrations, so this issue could be satisfied as part of that discussion!