Page History

...

First, you should create an empty page for the tool of interest under the "Analyzers" section of the backmatter, in each appropriate language space. It may be the case that a page already exists for the tool, in which case you can skip this step.  Below are links to the "Analyzers" sections for each space.

The page should be titled with the name of the analysis tool.  The page will be automatically populated with the information that you provide on individual rule/rec pages. You do not need to add any content to it. The page should also have the 'analyzer' label so that it shows up on the Analyzers section.

...

Each rule/rec page has an Automated Detection (AD) section, describing which tools can detect violations of the rule/rec. This section contains a table. Each row of the table contains information for a specific version of a tool. A row in the AD table has the following format.

Each tool wiki page is updated, by request, with the aggregated data from these individual tables. This aggregation process is automatic. In order for the process to pick up your changes, you should adhere to certain guidelines when entering data into the AD tables.

1. The Tool column should contain the name of the tool, hyperlinked to the corresponding tool wiki page. 
   
   1. The easiest way to populate this field is with the Link macro in Confluence. Simply insert a Link macro and point it towards the appropriate tool page.
2. The Version column contains the version of the tool to which this information pertains.
   
   1. The easiest way to populate this field is with the "Include Page" macro in Confluence. You should include the version page associated with the tool into this cell.
3. Each checker name should be provided on a separate line in the Checker column. Or you can add multiple checkers on one line by separating them by commas.
4. Each checker description should be provided on a separate line in the Description column, adjacent to the associated checker.

...