Add VS Code Extension v2.0.2 release content

[radurentea]

📝 Description

Publish date

Expected publish date: YYYY-MM-DD

Review process

• Initiate technical review
  • This item is N/A
  • Add subject matter experts (your team members, experts in the field)
• Once tech review mostly done, initiate editorial review
  • Add technical editors (@f-hollow, @FBEZ, and/or @pedrominatel)

Checks

• Article folder and file names:
  • Folder path is content/blog/YYYY/MM/my-new-article (articles only)
  • Folder and file names have no underscores, spaces, or uppercase letters (My new_article)
• New article's YAML frontmatter:
  • Title updated
  • Date matches the format date: 20YY-MM-DD
  • Summary updated
  • Authors added (see Add youself as an author)
  • Tags added
• Updated article's YAML frontmatter:
  
  • This item is N/A
  • If article folder is moved or renamed, the field aliases: with a new URL slug is added
  • Date of update is added lastmode: 20YY-MM-DD
• Article media files:
  • All images are in .WebP format (see Use WebP for raster images)
  • Images are compressed within 100-300 KB, with a hard limit of ≤ 500 kB
  • Where possible, Hugo shortcodes are used instead of raw HTML for content types unsupported by markdown (see Use additional content types)
• Links in articles
  • Make sure all links are valid
  • No links to Google docs present
  • Use a specific ESP-IDF version in links (avoid stable, hard no for latest)
• Git history
  • Commits are clean and squashed to the minimum necessary
  • Commit messages follow Conventional Commits format
  • Your feature branch is rebased on main

🔗 Related

🧪 Testing (Hugo)

[brianignacio5]

Small changes.

[kolipakakondal]

LGTM.

[kolipakakondal]

As many users have been asking how to set up ESP-IDF tools in a custom directory through eim. It would be helpful to include a note on this along with a reference link.

[f-hollow]

@radurentea Thank you for writing the article!

I left a couple of comments that might take some time to resolve. So I will post them now and will continue my review tomorrow.

[f-hollow]

There are other articles about the ESP-IDF Extension for VS Code, but it takes some time to find them, because we don't have the same tag to tie them together.

The tag VSCode seems to be used in most of them. But it can be used in other articles that deal with VS Code and have nothing to do with the VS COde extension.

Maybe you want a more specific tag for the VS Code extension?

I highly recommend that you pick one unambiguous tag and add it to the other articles related to the VS Code extension:

Please think what works best for you.

[radurentea]

I agree, what do you think about "ESP-IDF Extension for VS Code"?

[kolipakakondal]

We can maintain the same name across all places - ESP-IDF Extension for VS Code

1. Marketplace ESP-IDF Extension for VS Code
2. Release Page ESP-IDF VSCode Extension Release v2.0.2 (probably, this need to be changed!)
3. Project Name ESP-IDF Extension for VS Code
4. Documentation ESP-IDF Extension for VSCode

[github-actions]

🎉 A preview for this PR is available at: https://preview-developer.espressif.com/pr702/