pqc blog first draft

[Pranav1904]

📝 Description

This PR adds a new March 2026 blog post on hybrid secure boot with post-quantum verification for ESP32-class targets at content/blog/2026/03/hybrid-pqc-secure-boot-esp32/index.md. The article explains the quantum threat model (Shor’s impact on RSA/ECDSA), introduces the hybrid trust model (classical + PQC), documents flash/signature layout, verification flow, measured performance, and includes practical build/test steps for pqc_boot_verify.

This change is needed to publish a technical walkthrough of the PQC secure boot prototype in a format aligned with the Developer Portal’s Hugo syntax and section structure, so the content can be reviewed and rendered directly as a production blog entry.

Publish date

Expected publish date: 2026-04-03

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)

[github-actions]

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

[f-hollow]

@Pranav1904

Thank you for your contribution!

Is the PR ready for review? If not yet, please click Convert to draft on the right hand sidebar.