Merge pull request #7 from DirtyF/patch-1

Add import to Forestry button

README.md

@@ -2,6 +2,8 @@
 
 This is a Gatsby starter for creating a static site with content sourced from markdown files. This project is pre-configured for use with the Forestry CMS.
 
+[![Import to Forestry](https://assets.forestry.io/import-to-forestryK.svg "Import to Forestry")](https://app.forestry.io/quick-start?repo=forestryio/gatsby-starter-forestry&branch=master&engine=gatsby)
+
 This starter is based on the [gatsby-starter-blog](https://github.com/gatsbyjs/gatsby-starter-blog) project and uses the [gatsby-transformer-remark](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-transformer-remark) plugin to enable content to be sourced from markdown files.
 
 For styling, this project supports SCSS via [gatsby-plugin-sass](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-sass), and uses the [Bulma](https://bulma.io/) CSS framework.
@@ -52,4 +54,4 @@ If you are publishing the site to a subdirectory, such as GitHub pages, you will
 
 ## Limitations
 
-The build will fail if there isn't at least 1 instance of a given front matter value used in your content. For example, if every markdown file had an empty `date` field, the build would fail because `frontmatter.date` is referenced in the graphQL queries for the page templates. (If anyone knows a way to query front matter without this limitation, I'd love to hear about it - post an issue!)
+The build will fail if there isn't at least 1 instance of a given front matter value used in your content. For example, if every markdown file had an empty `date` field, the build would fail because `frontmatter.date` is referenced in the graphQL queries for the page templates. (If anyone knows a way to query front matter without this limitation, I'd love to hear about it - post an issue!)