Document new Config Explorer feature

[CodeMonkeyF5]

Proposed changes

Plan is for Config Explorer GA on June 12

Add documentation and changelog entry for Config Explorer, a new NGINX One Console feature that lets users browse and search any NGINX configuration as an interactive node graph. Config Explorer is generally available as of June 12, 2026 for Staged Configurations, Instances, and Config Sync Groups.

A new how-to page (nginx-configs/explore-configurations.md) explains how to open Config Explorer for each supported resource type, browse the configuration node graph, and search for directives. The page follows the existing howto content type, frontmatter conventions, and procedural step structure used across the nginx-one-console section. It is weighted at 450, placing it after the staged-configs, config-sync-groups, and config-templates subsections in the sidebar.

The changelog.md entry follows the existing date-heading and ### feature-heading format used by all prior entries in that file.

The documentation page intentionally omits the upstream server editing capability, which is not generally available and is enabled on a per-tenant basis outside of the standard release.

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 Technical Writing 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. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

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

---

[travisamartin]

Looks great! :)

[CodeMonkeyF5]

Realized that even if we flip feature flag on June 12, we first need to ensure the UI changes are merged before the Friday cutoff. So have set to June 15 (further out of possibilities). If the UI changes get merged by Thursday will update back to June 12.