Update Project Profile: VRMS Add Jack Haeger

[theogguu]

Fixes #7473

What changes did you make?

• Added Jack Haeger to leadership variable in the VRMS .md file

  github-handle: JackHaeg
  role: Lead Product Manager
  links:
    slack: https://hackforla.slack.com/team/U059005TN1L
    github: https://github.com/JackHaeg
  picture: https://avatars.githubusercontent.com/JackHaeg

Why did you make the changes (we will use this info to test)?

• To keep project information up to date so that visitors to the website can find accurate information.

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied

Visuals after changes are applied

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

---

From your project repository, check out a new branch and test the changes.

git checkout -b theogguu-update-profile-add-haeger-7473 gh-pages
git pull https://github.com/theogguu/website.git update-profile-add-haeger-7473

[pluto-bell]

Great work.

The new profile is added correctly in the code base and the new profile card populates on the VRMS project page like it should.

Provided a good explanation as to why the changes were made and visuals for before and after.

My only suggestion is to be more specific with your git branch naming in the future. In this case, it would allow us to quickly know the profile is being added to the VRMS project specifically.

[DrAcula27]

@theogguu Great job on your Good First Issue! Your code passed the ABC's, including:

• PR is made from the correct branch
• PR links to the correct issue:
  • Update Project Profile: VRMS Add Jack Haeger #7473
• The correct file _projects/vrms.md was edited
• No extra edits were made
• Appearance of the website looks just like your screenshots (Chrome and Firefox)
• I agree with the nitpick from the other reviewer: naming your issue branch so that which project was modified is in the name would be more clear.
  Approved! 👍

[NolaDodd]

Hey! Your pull request looks good!

• PR is the correct branch and references the correct issue
• The explanation is good
• The correct file and changes were made
• The appearance of the updated website looks correct

Other than a clearer branch name like the others mentioned, everything looks good to me!

[NolaDodd]

Great job!

[codyyjxn]

@theogguu Great job on your Good first issue.

Things that went well:

• The correct branch name
• The correct file _projects/vrms.md was edited
• You provided screenshots
• Set this up in my end I was able to see what the changes you made.

Keep it up!

[Sujay-Anantha]

Great Job @theogguu,

• The PR uses the correct naming format.
• The PR is linked to the original issue: Update Project Profile: VRMS Add Jack Haeger #7473.
• The summary of the work done is concise and accurately describes the changes.
• The visual changes on the website match the screenshots provided.

[daras-cu]

Thanks for taking on this issue @theogguu, nice work. Don't forget there are a couple more action items to check off on the original issue #7473 now that this is merged.