-
Notifications
You must be signed in to change notification settings - Fork 83
Proposal: Refactoring NGINX App Protect WAF documentation #547
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
base: main
Are you sure you want to change the base?
Conversation
This commit adds a new documentation folder to the repository, with a discrete section for proposals. I will be using this folder in the future to organise more process documentation. NGINX App Protect WAF has had a lot of fundamental design problems with how its documentation is structured due to historic changes in the direction of the product. Since those changes, the documentation has not changed to account for it.
…tation into docs/nap-refactor-proposal
…tation into docs/nap-refactor-proposal
✅ Deploy Preview will be available once build job completes!
|
It occurs to me now that I've thrown this PR up, I could have done a partial refactor as a proof of concept that could be interacted with as a Deployment preview. I'm not certain the time investment would be useful to exemplify the point, however, and the full extent of changes involved with a refactor mean it's difficult to isolate one set of changes given the amount of reference links that need to be updated. |
Proposed changes
This pull request is the living document for a proposal to refactor the NGINX App Protect WAF documentation.
For ease of review, please view the file directly, which will render the diagrams properly.
Feedback should be added parts of the proposal using GitHub's commenting feature.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
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. ↩