Skip to content

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

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

ADubhlaoich
Copy link
Contributor

@ADubhlaoich ADubhlaoich commented May 13, 2025

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.

  • 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.

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.
Copy link

Deploy Preview will be available once build job completes!

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

@ADubhlaoich ADubhlaoich self-assigned this May 14, 2025
@ADubhlaoich ADubhlaoich requested a review from a team May 14, 2025 10:22
@ADubhlaoich ADubhlaoich marked this pull request as ready for review May 14, 2025 10:23
@ADubhlaoich ADubhlaoich requested a review from a team as a code owner May 14, 2025 10:23
@ADubhlaoich
Copy link
Contributor Author

ADubhlaoich commented May 14, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant