article: MCUboot Getting Start Guide for ESP32

[almir-okato]

Description

Article translated and updated from my original from Embarcados portal.

Related

Testing

Built and visualized using local hugo server.

---

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.

[FBEZ]

Thank you @almir-okato for this article!

I’ve left a few comments for you to review. I also noticed that MCUBoot is in bold every time. I suggest keeping it plain or using a monospaced/verbatim style if needed.

[almir-okato]

Thank you @almir-okato for this article!

I’ve left a few comments for you to review. I also noticed that MCUBoot is in bold every time. I suggest keeping it plain or using a monospaced/verbatim style if needed.

Thanks @FBEZ

Regarding the bold style for MCUboot and some other names, I've tried to keep the directions suggested on the review of my previous article in the Developer Portal.
Should I change for MCUboot and the other terms?

[FBEZ]

@almir-okato thank you@ I’ve just added a final comment regarding the annotation block.
I still see MCUBoot in bold throughout. Would you like to keep it that way? I find it a bit eye straining.

[almir-okato]

@almir-okato thank you@ I’ve just added a final comment regarding the annotation block. I still see MCUBoot in bold throughout. Would you like to keep it that way? I find it a bit eye straining.

I think you are right, I reduced the amount of names in bold, tried to keep only for first occurrences or some highlight notes. Thanks!

[f-hollow]

Thank you @almir-okato for this article!
I’ve left a few comments for you to review. I also noticed that MCUBoot is in bold every time. I suggest keeping it plain or using a monospaced/verbatim style if needed.

Thanks @FBEZ

Regarding the bold style for MCUboot and some other names, I've tried to keep the directions suggested on the review of my previous article in the Developer Portal. Should I change for MCUboot and the other terms?

@almir-okato Francesco is right about the formatting of MCUboot and other software names.

To be honest, I am not sure why we ended up with all terms in bold in your previous article. I checked all my comments and only found this edit related: #363 (comment)

However, I only proposed to make these words bold, because these are the summary words in bullet points, not because all software titles should be in bold. Sorry if I didn't make it clear!

[f-hollow]

@almir-okato Thank you for contributing this article!

I pointed a out a few nitpicks and shared some ideas on further content polishing.

[almir-okato]

Thank you @almir-okato for this article!
I’ve left a few comments for you to review. I also noticed that MCUBoot is in bold every time. I suggest keeping it plain or using a monospaced/verbatim style if needed.

Thanks @FBEZ
Regarding the bold style for MCUboot and some other names, I've tried to keep the directions suggested on the review of my previous article in the Developer Portal. Should I change for MCUboot and the other terms?

@almir-okato Francesco is right about the formatting of MCUboot and other software names.

To be honest, I am not sure why we ended up with all terms in bold in your previous article. I checked all my comments and only found this edit related: #363 (comment)

However, I only proposed to make these words bold, because these are the summary words in bullet points, not because all software titles should be in bold. Sorry if I didn't make it clear!

I think I misunderstood that at the time, sorry! I'll try to make it right for the next ones.

[almir-okato]

@FBEZ @f-hollow thanks for your review! I've applied your suggestions.

[f-hollow]

@almir-okato Please rebase on main to fix preview deployment.

Otherwise, LGTM!

Regarding the publishing date, with Christmas and New Year approaching, let’s schedule the publication for, say, 9 January? Releasing it once everyone is back at work will give this article more visibility and focus.

If you agree, please update the date.

[github-actions]

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

[f-hollow]

@almir-okato

The last touch: Can you please move the article to 2026/01 folder so that the article date matches the year-month folder?

To my surprise, I found that this edge case is not verified in our CI. Created a fix in #626