[BD-3275] Simplify Dev Guide Nav

[internetisaiah]

Why are you making this change? (required)

In preparation for the full dev guide detangle, this PR aims to clean up the nav bar. Note: I did my best to not change directory names and only change nav_title: keys, to minimize the amount of redirects needed. All the top-level directories will be renamed in the future though--all at once.

NOTE TO REVIEWERS!

To auto-generate a list of all the old URLs so you can easily test the redirects, enter the following commands into the terminal, then follow the prompts in the terminal window.

cd braze-docs
git checkout simplify-dev-guide-nav
git fetch origin simplify-dev-guide-nav

./bdocs redirects

Related PRs, issues, or features (optional)

• N/A

Feature release date (optional)

• N/A

Contributor checklist

• I confirm that my PR meets the following:
  • I signed the Contribution License Agreement (CLA).
  • My style and voice follows the Braze Style Guide.
  • My content contains correct spelling and grammar.
  • All links are working correctly.
  • If I renamed or moved a file or directory, I set up URL redirects for each file.
  • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
  • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

• Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
• Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
braze-docs-ko	⬜️ Ignored (Inspect)	Visit Preview		Nov 7, 2024 5:18pm

[internetisaiah]

All that needs to be completed before merging:

• Create redirects for files
• Fix all the Git conflicts
• Update references to specific headers that were changed (as needed)

[internetisaiah]

@cla-bot check

[internetisaiah]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[Bucimis]

lgtm when comments addressed

[lydia-xie]

looks good from my end! feel free to merge when you're ready :) great work