reframed NGF getting started as a deployment guide

[travisamartin]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Give a brief overview of the problem or feature being addressed.

Solution: Explain the approach you took to implement the solution, highlighting any significant design decisions or
considerations.

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/313/

---

[ADubhlaoich]

Generally LGTM, with two points:

• Moving the document up a folder means the weight on all other top level items should be adjusted
• This PR is in draft state, so the stakeholders from NGF are not aware of its existence. Nothing in the PR description justifies the changes, so there is no context to why this change is being made.

[sjberman]

Is this change going to prevent users from visiting this doc now?

There are definitely smaller scale users who could utilize this guide for their own setups, but this title may not draw them in as we previously intended.

If I have the thought "I just want to quickly get a basic NGF installation up and running", a guide that says "Get Started" feels more likely to get my attention than this new title.

[sjberman]

By removing the link to the standard installation guide here, are users who come to this guide and realize it's not what they want going to be confused as to where to go next?

[ADubhlaoich]

I'm concerned about this too: benefit of the doubt suggests maybe the title change suggests the user flow leads them to a different document before they get to this point.