article: working with ESP-IDF in CLion

[olegznv]

Description

This article is a tutorial about how to work with an ESP-IDF project in CLion, a cross-platform C and C++ IDE. The tutorial explains how to build an application, flash it to an ESP32-S3 board, debug it, and more.

Related

Testing

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[f-hollow]

@olegznv Sorry for my belated review!

I merged the article because I know it should be online faster. It looks good!

If you have a chance, you can do a couple of things in a follow-up PR:

• Please check my only comment about mini USB.
• Feel free to update the article date.

Another general comment: I am not sure what your JetBrains style guide says, but we tend to pay attention to list hierarchies. You have numbered lists mixed with bullet lists at the same indentation level. I guess the bullet lists should be sublists to the numbered lists to highlight the underlying hierarchy and, eventually, provide better orientation to the readers. Likewise, the screenshots should be indented accordingly.

So if you have a chance, please submit a follow-up PR. Thank you!

[f-hollow]

ESP boards always have micro USB ports. Also, please mention that it should be a data cable, because you can accidentally run into a cable for charging only.

Suggested change

	- USB-C to mini USB cable.
	- USB-C to micro USB data cable.

[f-hollow]

@olegznv I also noticed that you don't appear as an author. I know it is a bit counterintuitive with Hugo.

As documented in the Contribution guide, you still need to create the file data/authors/<author-name>.json and populate your information there. For examples, please refer to other files in that folder.

[olegznv]

@f-hollow thank you! Sorry for these mistakes and inaccuracies. I'll fix them in a follow-up PR.