Skip to content

C++ Components for ESP-IDF / Components for the Minimal Working Environment#669

Open
elrebo-de wants to merge 4 commits intoespressif:mainfrom
elrebo-de:main
Open

C++ Components for ESP-IDF / Components for the Minimal Working Environment#669
elrebo-de wants to merge 4 commits intoespressif:mainfrom
elrebo-de:main

Conversation

@elrebo-de
Copy link

@elrebo-de elrebo-de commented Mar 5, 2026

📝 Description

For beginners it is not easy to establish a minimal working environment for the ESP32 SoCs with e.g. Wifi, buttons, LEDs and waking up from Deep Sleep. Unfortunately such a minimal environment is necessary to get things done. This article describes some components which help to set up this environment. By using C++ the complexity is hidden inside the component classes.

Publish date

Expected publish date: 2026-03-30

Review process

@f-hollow, @FBEZ: would yo please review my first article?

  • 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)

I have run hugo server locally and verified there are no build errors.
I have checked the rendered output on Desktop view.

@pedrominatel pedrominatel requested review from FBEZ and f-hollow March 6, 2026 09:22
Copy link
Member

@pedrominatel pedrominatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much, @elrebo-de, for your contribution! Interesting article.
Please take a look at our CI and fix the underscore in the file name.

…in CMakeLists.txt of the program using a component.
@github-actions
Copy link

github-actions bot commented Mar 6, 2026

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

@f-hollow
Copy link
Collaborator

@elrebo-de Thank you very much for your contribution!

I will try to finish my review this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants