docs(*): New blog article on using VS Code for development #8948
Conversation
|
|
||
| The Gatsby.js platform and ecosystem is composed not only of the [core Inkteam members](https://www.gatsbyjs.com/about/), but a huge group of community members as well. I have no doubt that part of the success of Gatbsy is due to the core team really encouraging the community to be involved. They even give you [free swag for becoming a contributor](/docs/contributor-swag/). | ||
|
|
||
| Now that I have convinced you to get involved, the first thing you should do is review the existing [how to contribute guide](/docs/how-to-contribute/). That will go over the basics of checking out the project and getting set up. |
There was a problem hiding this comment.
First of all - thanks :)
But... I'd maybe just dive right into the topic at hand? People are going to come here for info on VSCode, so I'd recommend diving right in from the get go!
There was a problem hiding this comment.
no problem @DSchau.
Do you want me to just remove these two paragraphs totally and just get right into it?
|
|
||
| ## Conclusion | ||
|
|
||
| In this article we have learned some of the basics about configuring and using VS Code for development on the Gatsby project. The Extensions and configuration discussed here can be applied though to a project that **uses** Gatsby just the same. |
There was a problem hiding this comment.
Maybe just say any project, be it a Gatsby project or something else? Largely, these are great VSCode settings for a modern front-end project.
| --- | ||
| title: "Using VS Code for Supercharged Gatsby.js Development" | ||
| author: Michael Holtzman | ||
| date: 2018-10-09 |
There was a problem hiding this comment.
We'll need to update this for the date it's published. Maybe we shoot for Thursday or Friday @lindaleebumblebee?
|
thanks @DSchau I'll go over the comments and make the updates tonight. |
DSchau
changed the title
|
@DSchau I made the updates requested, I changed the publish date for today but that can easily be updated to tomorrow or next week. |
| Now that I have convinced you to get involved, the first thing you should do is review the existing [how to contribute guide](/docs/how-to-contribute/). That will go over the basics of checking out the project and getting set up. | ||
|
|
||
| The remainder of the article will talk about using VS Code if you want to contribute to the core [Gatsby project](https://github.com/gatsbyjs/gatsby). That being said everything mentioned here can be applied to just about any JavaScript project. | ||
| In this article I will talk about using VS Code Editor if you want to contribute to the core [Gatsby project](https://github.com/gatsbyjs/gatsby). We'll learn how to easily configure the Editor to make development easier and help ensure your Pull Requests are ✅ and get accepted. That being said everything mentioned here can be applied to just about _any_ JavaScript project. |
There was a problem hiding this comment.
Let's tweak this opener a bit. Open to further tweaks on this, too!
VS Code is a truly great choice for your code editing needs. In this article, I'll show you some great tips and tricks, extensions, and more to maximize your productivity and get to what matters, building out great products. Some of these tips and tricks will make it even easier to contribute to the Gatsby core repo, and help ensure your pull requests are ✅ and accepted. That being said everything mentioned here can be applied to just about any JavaScript project.
|
@DSchau those last couple of changes look good 👌 |
|
@mikelax thanks for being so receptive and prompt with the feedback! I'll merge this 🎉 |
|
@mikelax we're gonna push this out to Monday. Would you mind (or I can) updating the date to 10-15-2018? |
|
@DSchau date and folder name updated to 15th 🚀 . |
|
We had one post come in that we're gonna do first (relating to the webinar!). Sorry for the back and forth on this, but could we do Thursday, the 18th? I promise it'll go up then :) Thanks for your work and patience on this! |
|
@DSchau no worries on the changing dates, I get it. |
|
@mikelax finally got this merged. Thanks so much for your contribution. We'll get gatsbyjs.org built out with this change, and I'll comment on this PR when it's live! |
|
@mikelax, thanks for the post. I believe adding a hint concerning the webpack sourcemap config following #6877 (comment) would be a valuable addition. Only after setting the |
…8948) * feature: New blog article on using Code for development. * feature: Updates to blog article based on Feedback 👌 * feature: more tweaks to article. * chore: Update date of blog post to 15th. * chore: update date for blog post. * Update index.md
Overview
New blog article on using VS Code for developing on gatsby.
Focuses on setting up eslint and prettier and debugging in chrome
Came from idea in PR #7803