Migrate policy feature information

[ADubhlaoich]

Overview

As a F5 WAF for NGINX user, I want information about WAF features, So I can configure my policies accordingly.

Description

Underneath V4 and V5's configuration pages, there is a table of Supported Policy features.

The context of what a feature is and how to configure it are split across different locations.

I have began to migrate this content, starting with the table itself as an include file: /content/includes/waf/table-policy-features.md.

In the refactor, all context related to single a feature exists in one location, which is a page per feature in the folder /content/waf/policies.

All content from the existing table must be migrated and consolidated onto new pages in the refactor folder.

Tasks

For a given feature:

• Identify the content related to a feature
• Create a page for the feature in the folder /content/waf/policies
• Add the feature and page link to /content/includes/waf/table-policy-features.md
• Rewrite the content according to our contemporary style guide

If a page hyperlinks to content that does not exist in the refactor, add an empty anchor link and flag it in this issue for me to update when relevant.

The four existing feature pages exemplify how some content has been re-written: features rarely have uniform amounts of content available.

I am alphabetizing the table: within the Policy folder, the first three items are fixed to the top, while the feature pages afterwards (Item four onwards) should be alphabetized.

Resolving page weights across multiple PRs might be annoying, so it's low-priority as something I can easily fix in the primary branch.

Acceptance criteria

• The user can find the what features are supported easily
• The user can follow links to a destination page for each feature
• The user has all context of the feature on its page

[ADubhlaoich]

Adding entries for all of the speculated pages to the table now, then I will follow-up with the alphabetized pages themselves, creating the relative links.

@JTorreG Feel free to push directly into waf/refactor for this when you pick it up: depending on how my work goes finishing one other page, it might make sense for us to start at opposite ends and meet in the middle.