NGF: Update user architecture guide

[salonichf5]

Proposed changes

Updates user architecture guide to be less verbose and more readable with high level overview

• simplified diagrams
• descriptions for diagrams are put into tables
• restructuring some of the content
• linked Developer guide in the introduction

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[sjberman]

Does this have anything specific to our 2.1 release? If not, it can target main.

[salonichf5]

Does this have anything specific to our 2.1 release? If not, it can target main.

don't we want these changes in release 2.1 ? Does not have anything specific to release 2.1.

[sjberman]

If we publish to main, then it becomes public immediately. It's not inherently tied to the release, so we could publish it as soon as it's done. And if this doesn't get merged before we release, then the 2.1 branch will be deleted, so we would merge to main anyway.

[salonichf5]

If we publish to main, then it becomes public immediately. It's not inherently tied to the release, so we could publish it as soon as it's done. And if this doesn't get merged before we release, then the 2.1 branch will be deleted, so we would merge to main anyway.

Thanks for clarifying, I thought the release branch is our latest branch on changes that get reflected.

[sjberman]

Thanks for clarifying, I thought the release branch is our latest branch on changes that get reflected.

Nope, the main branch is what gets published. The release branch is for changes upcoming in our release, that will be merged into main when we release and those features become available.

[ADubhlaoich]

Generally LGTM, added edit suggestions for sentence case headings.

There's also an ambiguous sentence that should be reworked.

[sjberman]

Does the rendered version with tables look okay? Not seeing the automatic preview in the PR...

[salonichf5]

Does the rendered version with tables look okay? Not seeing the automatic preview in the PR...

let me add some screenshots for visibility

[salonichf5]

Screenshots to view rendered diagrams and tables @sjberman

[ADubhlaoich]

As a point of record, there's no automatic preview because the branch for the PR is from a fork.

F5 employees can just branch directly from the repo without forking, which will generate a preview.