Build a Gatsby Blog using the Cosmic JS source plugin

[tonyspiro]

Gatsby 🔥 + Cosmic 🛠 🚀

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit ba23be2

https://deploy-preview-5783--using-drupal.netlify.com

[tonyspiro]

@KyleAMathews got this random netlify link from @gatsbybot

[gatsbybot]

Deploy preview for gatsbygram ready!

Built with commit befbafd

https://deploy-preview-5783--gatsbygram.netlify.com

[pieh]

Preview of blog post: https://deploy-preview-5783--gatsbyjs.netlify.com/blog/2018-06-07-build-a-gatsby-blog-using-the-cosmic-js-source-plugin/

[jlengstorf]

@tonyspiro Thanks so much for sending this over! I just went through and made some edits to the post (see my commit message above for details), but overall this looks like a great intro to CosmicJS!

A quick clarification: in the tutorial, the source plugin config has a field for an API key. Is there a link or instructions for getting one of those keys? Do I need one to get data loaded from CosmicJS? Will my local blog have data if I don't create a CosmicJS account and add some blogs beforehand?

If this is a special demo so people don't need to create an account, it may be worth adding some clarification on that, because I found myself wondering if this tutorial would work for me without first creating a bunch of content to work with.

[tonyspiro]

Thank you @jlengstorf! Your edits look good to me.

1. For the API key, this is optional and can be set in the Cosmic JS Bucket dashboard. I can add a line to indicate where to do this (Your Cosmic JS Bucket > Settings > Basic Settings).

2. As for the blog content, if you download the full GitHub repo, it defaults a connection to a demo Bucket with all of the demo data and it will work right out-of-the-box. To be able to edit content, you would need to install the app (with demo content) and config in the code to connect to this Bucket. I can add a line to explain this as well.

Let me know if you want me to add these. Thanks!

[jlengstorf]

Hey, @tonyspiro — yes, please do! I think it will help keep things clear for readers. Thanks!

[tonyspiro]

Hey @jlengstorf, changes pushed. Let me know if you need anything else, thanks!

[jlengstorf]

@tonyspiro This looks great!

@shannonbux has been managing the blog publishing schedule, so I'll tag her in here for any remaining edits and/or pushing the button to take it live. 😄

[tonyspiro]

Thank you @jlengstorf! And thank you @shannonbux, let me know if you need anything.

[KyleAMathews]

Looks great! Will release this tomorrow.

[KyleAMathews]

Can you add canonicalLink here to your original post so you get to keep the google juice ;-)

gatsby/docs/blog/2018-04-10-how-to-handle-comments-in-gatsby-blogs/index.md

Line 5 in 82d9188

canonicalLink: https://www.gatsbycentral.com/how-to-handle-comments-in-gatsby-blogs

[tonyspiro]

Thank you @KyleAMathews! This is done.

[KyleAMathews]

Thanks!

[jlengstorf]

Hiya @tonyspiro! 👋

This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here.

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (We’ve got t-shirts and hats, plus some socks that are really razzing our berries right now.)
2. If you’re not already part of it, we just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again! 💪💜