blog: Article for promote BSP Generator

[espzav]

📝 Description

This is the article about new tool - BSP Generator.

Publish date

Expected publish date: 2026-06-30 or earlier

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)

• I have run hugo server locally and verified there are no build errors.
• I have checked the rendered output on Desktop view.
• I have verified that internal links and syntax highlighting work correctly.

[espzav]

@PetrESP, @tore-espressif, @igrr, @georgik PTAL

[georgik]

Lgtm. Just trim screenshot borders. It is visible in dark mode. There is a lot of unused whitspace. Probably only portion of ui is necessary.

[PetrESP]

I really like the pictures and that goes straight to the point. I have some comments and suggestions from my point of view

[PetrESP]

To me this is AI being AI. The paragraph already says exactly what to do and what it achieves. I think that this is unnecessary and I would remove this

[PetrESP]

To me this whole paragraph does not make sense because this customer that uses BSP selector will not maintain the small, generated board package. He only has to save the json somewhere and the BSP team is maintaining the generated board package.
I think that this whole paragraph can be shortened and merged with Your application keeps calling the same BSP entry points:

[espzav]

I think, we can keep this paragraph.

[PetrESP]

Here I would say it is also a bit misleading. I would say that even the generated component has to be maintained by the BSP team because once you start editing the generated package you can't really do what you advertise in ESP-IDF upgraded? Regenerate, don’t rewrite

[espzav]

I am not sure, if I understand right, but generated custom board cannot be maintained by BSP team.

[PetrESP]

No I mean that the customer also should not maintain it. Ideally they should not touch the generated package because of they do then it can't be re-generated in the future because it would be missing those changes that they did.

[f-hollow]

@espzav Thank you for writing the article!

Here are a few general suggestions. Please implement them, then I will review the article content.

[f-hollow]

About this one and all other screenshots in the article.

Consider using a dedicated syntax for including images.

Please remember that articles can be read not only by humans, but also by AI these days.

If big chunks of information are only available in a screenshot, the possible scenarios are:

• The agent needs to process the image which takes many more tokens
• The agent might not be able to analyze images at all

Another question: is the information in the screenshot really important in the article context (like, let's say, you want to discuss certain things that are not clear from the web interface)? If yes, write this information out in text. If no, reduce or remove the screenshot.

Also, why make screenshots of large areas of web pages if they can be easily viewed by clicking a link?

[espzav]

@PetrESP Thank you for review, updated by your comments.

[github-actions]

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

[espzav]

@f-hollow Thank you for your review. I made some updates by your comments, but...:

Also, why make screenshots of large areas of web pages if they can be easily viewed by clicking a link?

I am sorry, but I really hate articles about something without images. I know that many things are clear and you can see it on the web but I don't want to change browser tabs. I want to see parts of the page that are about. I updated images a little for more focus.
We are still making it for people not for AI. Yes, we can optimize for AI but we want to make it good for reading by people. :-)

[espzav]

@georgik Thank you for the review. I updated images.