Add Sourcing from Flotiq documentation entry

[andrzejwp]

Description

This is a Sourcing from Flotiq documentation page that describes how to setup Gatsby for development with content pulled from Flotiq.

Documentation

Related Issues

[moonmeister]

If you could add it to the table on CMS page: https://www.gatsbyjs.org/docs/headless-cms/ The guide column will link to this document, the docs column will link to the source plugin docs and, starter to your primary starter (probably the one used in the guide).

[andrzejwp]

Done, @moonmeister

[moonmeister]

@AishaBlake can you help get this reviewed and merged? thanks

[marcysutton]

Thanks for the PR, this is going to be great! I ran into some issues with the custom project installation, so that's what most of the comments are about aside from some tweaky style guide stuff. Let me know if you have any questions.

[andrzejwp]

Thank you @marcysutton for a thorough review! I included your suggestions and amended the gatsby-node.js file as well as provided the post template. Let me know, please, if you see anything else.

[marcysutton]

Thanks for making the quick updates! I'm still having an issue with .env in a custom project using the plugin (approach # 2), and I have no idea why. When I copy the file to another project it works fine....and I can't tell why it fails. I checked my code into GitHub if you want to take a look at it: https://github.com/marcysutton/gatsby-flotiq-example

[muescha]

@marcysutton

In .env both variables have the GATSBY_ prefix. But in config one key is missing the Gatsby prefix:

baseUrl: process.env.GATSBY_FLOTIQ_BASE_URL,
authToken: process.env.FLOTIQ_API_KEY,

[andrzejwp]

@marcysutton

In .env both variables have the GATSBY_ prefix. But in config one key is missing the Gatsby prefix:

baseUrl: process.env.GATSBY_FLOTIQ_BASE_URL,
authToken: process.env.FLOTIQ_API_KEY,

Yes, I amended that yesterday, after the initial set of comments.

@marcysutton I opened a PR to your repo with this fix.

[andrzejwp]

@marcysutton can you please take another look. I think I covered everything.

[marcysutton]

Thanks, I must have missed that change! I'm still having issues with the API url, even with the right authToken key and restarting the terminal. Still not sure why!

[moonmeister]

@andrzejwp The docs you've sent me previously for cloud integration and https://github.com/flotiq/gatsby-source-flotiq indicate FLOTIQ_API_KEY as the correct key. Has this changed for some reason?

[andrzejwp]

@andrzejwp The docs you've sent me previously for cloud integration and https://github.com/flotiq/gatsby-source-flotiq indicate FLOTIQ_API_KEY as the correct key. Has this changed for some reason?

Good point - the team has recently updated all our starters to use the GATSBY_ prefix. I just sent the updated integration docs via email and updated the source plugin readme as well.

[marcysutton]

Ah, I had totally missed dotenv in the starter. It works now! Thanks so much, I think we can merge.

[muescha]

@marcysutton i am interested what was wrong. is your final fix in the commits here? https://github.com/marcysutton/gatsby-flotiq-example/commits/master

[marcysutton]

@muescha two things: the original doc had an incorrect value for authToken, and was missing the dotenv package to read environment variables. Those things fixed it up! I have updated my repo so it should work now.

[muescha]

thx :)

[andrzejwp]

@muescha two things: the original doc had an incorrect value for authToken, and was missing the dotenv package to read environment variables. Those things fixed it up! I have updated my repo so it should work now.

Thanks and apologies - I wanted to keep the examples in the docs concise and I overdid it :(