Add new mentorship program details and audio brief for veterans

[jeromehardaway]

This pull request adds a new blog post to the src/data/blogs directory, introducing the updated Vets Who Code Mentorship Program. The blog highlights the program's focus on tactical guidance and practical skills for veterans transitioning into tech careers. Below are the key changes:

New Blog Post Addition:

• A new markdown file, updated-mentor-program.md, has been created with details about the Vets Who Code Mentorship Program, including its goals, structure, and application process. The blog emphasizes mentorship by recently transitioned engineers, weekly check-ins, pair programming, and practical career guidance.

Content Highlights:

• Key takeaways and benefits of the mentorship program are outlined, such as GitHub fluency, collaborative problem-solving, and career strategy development.
• The blog includes a detailed step-by-step guide for joining the program, covering roles, application, and matching processes.
• An embedded audio brief and call-to-action links are added to enhance engagement and provide additional resources.

This update aims to promote the program and provide veterans with a clear pathway into tech careers.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vets-who-code-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 6, 2025 2:44am

[Copilot]

Pull Request Overview

This pull request adds a new blog post that details the updated Vets Who Code Mentorship Program for veterans, including an embedded audio brief and a step-by-step application guide.

• New markdown file added with comprehensive program details
• Inclusion of an embedded audio brief in a styled HTML block
• Step-based guide to joining the mentorship program

Comments suppressed due to low confidence (1)

src/data/blogs/updated-mentor-program.md:6

• The image front matter block uses a JSON-like structure spread over multiple lines. Consider using standard inline YAML mapping (e.g., image: { src: "..." }) or proper YAML indented mapping for consistency and to avoid potential parsing issues.

image: