Skip to content

Conversation

lamATnginx
Copy link
Contributor

Proposed changes

Rename it to comply with branding

Checklist

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

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.

@lamATnginx lamATnginx self-assigned this Aug 20, 2025
@lamATnginx lamATnginx requested review from a team as code owners August 20, 2025 15:14
@github-actions github-actions bot added documentation Improvements or additions to documentation product/nim Issues related to NGINX Instance Manager product/nginx-one Issues related to NGINX One Console product/nginxaas Issues related to NGINX as a Service for Azure tooling Back end, repository, Hugo, and all things not related to content product/controller Issues related to NGINX Controller (EOS product) product/nap-dos Issues related to NGINX App Protect DOS product/nap-waf Issues related to NGINX App Protect WAF product/nms Issues related to NGINX Management Suite (EOS product) product/nic Issues related to NGINX Ingress Controller labels Aug 20, 2025
Copy link

Deploy Preview will be available once build job completes!

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

Copy link
Contributor

@ADubhlaoich ADubhlaoich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cannot find a single internal resource describing the urgency of this change or how it relates to any timelines for the unification effort.

@ADubhlaoich ADubhlaoich marked this pull request as draft August 20, 2025 15:53
@ADubhlaoich
Copy link
Contributor

Changed the PR to draft. This is not due until September and will need to be reconciled closer to that date with the work I have been doing in the refactor.

@travisamartin
Copy link
Contributor

travisamartin commented Aug 21, 2025

Should we create an issue ticket for the change (documenting its background and AC) vs. keeping a draft PR around for an indeterminate amount of time?

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/controller Issues related to NGINX Controller (EOS product) product/nap-dos Issues related to NGINX App Protect DOS product/nap-waf Issues related to NGINX App Protect WAF product/nginx-one Issues related to NGINX One Console product/nginxaas Issues related to NGINX as a Service for Azure product/nic Issues related to NGINX Ingress Controller product/nim Issues related to NGINX Instance Manager product/nms Issues related to NGINX Management Suite (EOS product) 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.

3 participants