chore: swap to jpeg to see if that helps

DSchau · Jan 21, 2023 · bb6e49a · bb6e49a
1 parent a46deca
commit bb6e49a
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/content/blog/2017-07-17-getting-started-with-gatsby/images/my-first-blog-post.jpeg b/content/blog/2017-07-17-getting-started-with-gatsby/images/my-first-blog-post.jpeg
diff --git a/content/blog/2017-07-17-getting-started-with-gatsby/index.md b/content/blog/2017-07-17-getting-started-with-gatsby/index.md
@@ -360,7 +360,7 @@ The `createPage` API accepts an object which requires `path` and `component` pro
 
 We can run `yarn develop` at this point, and then navigate to `http://localhost:8000/hello-world` to see our first blog post, which should look something like below:
 
-![My first blog post with Gatsby](./images/my-first-blog-post.png)
+![My first blog post with Gatsby](./images/my-first-blog-post.jpeg)
 
 At this point, we've created a single static blog post as an HTML file, which was created by a React component and several GraphQL queries. However, this isn't a blog! We can't expect our users to guess the path of each post, we need to have an index or listing page, where we display each blog post, a short snippet, and a link to the full blog post. Wouldn't you know it, we can do this incredibly easily with Gatsby, using a similar strategy as we used in our blog template, e.g. a React component and a GraphQL query.