Problem: No user-facing documentation for configuring TLS Passthrough
Solution: Add a how-to guide for TLS Passthrough and update Gateway API compatibility doc

Co-authored-by: Sarthak Agrawal <[email protected]>

* NFR Test Results for NGF version 1.4.0

---------

Co-authored-by: Saylor Berman <[email protected]>

Policy: As a user, I want to know how to remedy a policy restriction issue.

Solution: Add some workarounds to the troubleshooting doc.

Add longevity results for 1.4.0 (#2427)

* Release 1.4.0

* Manual updates and changelog

---------

Co-authored-by: Saylor Berman <[email protected]>

* Bump documentation theme version
* Run hugo mod tidy

…2575)

| datasource  | package               | from   | to     |
| ----------- | --------------------- | ------ | ------ |
| github-tags | nginxinc/docs-actions | v1.0.4 | v1.0.5 |

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

cherry pick docs-fix-broken-url (#2585)

Co-authored-by: nginx-aoife <[email protected]>

Problem: One of our relative links was incorrect and causing docs to fail to build.

Solution: Fix link.

Update README.md with correct make target behaviors
Add hugo-entrypoint to allow extra commands when docker starts
Update hugo theme version in go.mod
Use slimmer hugo docker image

docs: enableGitInfo config (#2637)

enableGitInfo config and docs-action bump

Fix docs docker failing without git context (#2654)

Add docker specific docs config to disable gitInfo

Add new "Get started" document (#2700)

This commit adds a new "Get started" document for NGINX Gateway Fabric.
It re-orders the top level page so that it is second after "Overview" as
a means to get a reader started as quickly as possible, and is a
combination of the existing kind guide, a Helm installation path and the
cafe-example on GitHub.

As part of this work, the original kind guide has been deleted: the only
context lost is regarding port forwarding, which this new document
mentions not requiring. The README for the cafe-example could also be
stripped down as a result: the step "skipped" regards how to use a
different hostname.

Both of these could instead be added to a general network configuration
document.

Co-authored-by: Saylor Berman <[email protected]>