Skip to content

Conversation

@mjang
Copy link
Contributor

@mjang mjang commented Jul 15, 2025

Proposed changes

Content reviewed and approved in an internal mirror of this repository. Based on the procedure described here: https://github.com/nginx/internal-docs/blob/main/documentation/closed-contributions.md

I've essentially mirrored the content here. Once our setup of these repositories is complete, this process will automatically include the approvals given in the internal mirror

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

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.

- Basic transparant v. blocking policies
- Strict policy
- Adjustments
- API info
- Changelog

Co-authored-by: yar <[email protected]>

Apply suggestions from code review

Co-authored-by: Daniel Edgar <[email protected]>

Apply suggestions from code review
@mjang mjang marked this pull request as ready for review July 15, 2025 16:42
@github-actions github-actions bot added documentation Improvements or additions to documentation product/nginx-one Issues related to NGINX One Console product/waf Issues related to F5 WAF for NGINX labels Jul 15, 2025
@mjang mjang requested review from a team as code owners July 15, 2025 16:42
@github-actions
Copy link

Deploy Preview will be available once build job completes!

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

@mjang mjang force-pushed the nap-usecase-stage1 branch from 3dbbe7d to 19669c7 Compare July 15, 2025 16:50
@mjang mjang force-pushed the nap-usecase-stage1 branch from 19669c7 to bec3100 Compare July 15, 2025 17:01
@mjang mjang merged commit 166a2a0 into main Jul 15, 2025
10 checks passed
@mjang mjang deleted the nap-usecase-stage1 branch July 15, 2025 17:08
@mjang mjang changed the title Nap usecase stage1 NAP integration into NGINX One Console (part 1) Jul 15, 2025
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 Issues related to NGINX One Console product/waf Issues related to F5 WAF for NGINX

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants