Skip to content

feat: Customer-friendly NGINX One Console home page #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 30, 2025

Conversation

mjang
Copy link
Contributor

@mjang mjang commented May 29, 2025

Proposed changes

We want a clear and consistent message on NGINX One, from the first intro to our customers to our docs. To that end, we're setting up a new home page for the NGINX One Console docs. Once merged, you'll see it at docs.nginx.com/nginx-one.

I've included two screenshots:

before

Screenshot 2025-05-29 at 12 11 38 PM

after

Screenshot 2025-05-29 at 12 12 09 PM

I have comments / approvals in PR #595 . I also have internal approvals from appropriate parties.

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 changes1, 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.

@mjang mjang self-assigned this May 29, 2025
@mjang mjang requested review from a team as code owners May 29, 2025 19:13
@github-actions github-actions bot added documentation Improvements or additions to documentation product/nginx-one NGINX One Console tooling Back end, repository, Hugo, and all things not related to content labels May 29, 2025
Copy link

Deploy Preview will be available once build job completes!

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

@mjang
Copy link
Contributor Author

mjang commented May 29, 2025

Note: approvals given in:

@mjang
Copy link
Contributor Author

mjang commented May 30, 2025

Merging based on approvals in #595 and managerial approvals in internal Slack

@mjang mjang merged commit 212cf5b into main May 30, 2025
10 checks passed
@mjang mjang deleted the nginx-one-new-homepage-v2 branch May 30, 2025 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation product/nginx-one NGINX One Console tooling Back end, repository, Hugo, and all things not related to content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants