docs: reorganize supported languages and tools by scan type

[claudiacodacy]

Summary

• Replaces the single 10-column, ~50-row table on Supported languages and tools with an Overview table (Language | File extensions | Supported scans, each scan name linking to its section) followed by one section per scan type, so a language lookup and a category lookup both work from this page.
• Section order: Overview, Static analysis, Secret detection, Dependency vulnerability scanning, Malicious packages detection, License scanning, Suggested fixes, Duplication, Complexity, Docker images of supported tools.
• Switched the page's footnotes from hand-rolled <sup><a>...</a></sup> HTML (unstyled anywhere in the theme, and its bottom-of-page list read oddly) to the footnotes markdown extension ([^id] / [^id]: text), which Material renders as proper numbered, back-linkable footnotes. Enabled footnotes in mkdocs.yml — confirmed via repo-wide grep that no page currently uses [^...] syntax, so this is additive, not a behavior change elsewhere.
• Converted the "Docker images of supported tools" table from raw HTML to a markdown table — required for its footnote references to render as real footnotes (raw HTML blocks aren't reprocessed for markdown inline syntax).
• Removed forced <br> line breaks in the Dependency vulnerability scanning and Malicious packages detection tables — leftover from when these were columns in a 10-column table and needed to wrap narrowly; they read as broken mid-sentence wraps in the new, wider 2-column layout.
• Left a <!-- TODO --> marker on Complexity: the table currently lists a per-language tool (Lizard, detekt), but Codacy also calculates a separate file-level complexity metric, and there's no documented per-language breakdown of that metric to model the distinction — flagging rather than guessing.
• Fixed relative links to the "which metrics does Codacy calculate" page (were copied from a raw-HTML href with a directory-style path that doesn't apply to a markdown link).
• Suggested fixes, Duplication, and Complexity are now top-level ## sections (no "Others" wrapper) so they show up directly in the page's on-page TOC.
• Stacked multi-value file extensions in the Overview table with <br> (e.g. C++'s five extensions each on their own line) instead of one long comma-separated string, so the column reads narrower.
• Fixed a broken Prospector link in "Docker images of supported tools": it pointed to landscapeio/prospector2, an unrelated repo, instead of landscapeio/prospector (already used correctly twice elsewhere on the page).

Theme fixes (theme/stylesheets/content.css)

• Enlarged the tap target on footnote-marker links, which inherit sup's browser-default font-size: smaller and had no styling anywhere in the theme (~5×15px clickable area). Rule covers both the footnotes extension's <sup><a> markup and the hand-rolled <a><sup> pattern still used on a couple of other pages.
• Fixed a real rendering bug surfaced by switching to real footnotes: a footnote referenced from many rows (e.g. the "opengrep" footnote, used by ~20 languages) gets one back-reference link per usage, and Material renders those one per line instead of flowing inline — turning a heavily-referenced footnote into a list item ~1150px tall. Now only the first back-link renders; confirmed footnote list items are back to normal single/few-line heights.

Test plan

• mkdocs build --strict passes (anchor validation is warn→error under --strict, confirming every footnote and Overview jump-link resolves)
• vale docs/getting-started/supported-languages-and-tools.md — 0 errors/warnings/suggestions
• Confirmed the H1 anchor and #docker-images-of-supported-tools — both referenced by inbound links/redirects elsewhere in the repo — are unchanged and present in the built HTML
• TOC now reads: Overview, Static analysis, Secret detection, Dependency vulnerability scanning, Malicious packages detection, License scanning, Suggested fixes, Duplication, Complexity, Docker images of supported tools, See also
• Footnote list confirmed rendering as a real <ol> with back-references; item height back to ~17px (was ~1150px) after the backref fix, verified across all 10 footnotes
• Footnote-marker tap target confirmed on the new <sup><a> markup (~15×22px) and spot-checked on the pre-existing <a><sup> pattern on managing-security-and-risk.md and organization-overview.md
• Spot-checked several category tables against the original table data for transcription accuracy
• Verified landscapeio/prospector2 resolves to a real but unrelated repo, and landscapeio/prospector is the correct, already-used-elsewhere link

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[github-actions]

Overall readability score: 53.74 (🔴 -0.16)

File	Readability
supported-languages-and-tools.md	7.84 (🔴 -41.3)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
supported-languages-and-tools.md	7.84	0	19	22	19	8.56
	🔴 -41.3	🔴 -31.17	🔴 -8.19	🔴 -8.9	🔴 -4.8	🔴 -0.75

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	53.74	42.79	10.97	12.4	12.31	8.03
	🔴 -0.16	🔴 -0.12	🔴 -0.03	🔴 -0.03	🔴 -0.02	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[codacy-production]

Pull Request Overview

The PR successfully reorganizes the 'Supported languages and tools' documentation by scan type and modernizes the underlying structure using native Markdown footnotes. Codacy analysis indicates the changes are up to standards, and the CSS improvements for footnote tap targets enhance mobile accessibility.

There is a notable implementation gap: the PR description mentions an 'Others' section containing 'Suggested fixes', 'Duplication', and 'Complexity', but the current implementation uses individual H2 headers for these categories without a parent 'Others' header. Additionally, a high-severity issue was identified regarding a broken link for the Prospector tool that must be corrected before merging.

About this PR

• The PR implementation uses individual H2 headers for 'Suggested fixes', 'Duplication', and 'Complexity'. This contradicts the PR description and test plan which specified these should be grouped under an 'Others' section. Please align the header hierarchy with the intended TOC structure.

Test suggestions

• Found recommended test scenario: Verify that Overview table links correctly anchor to their respective scan-type headers.
• Found recommended test scenario: Verify that the 'footnotes' extension is enabled and rendering proper back-links in the build.
• Found recommended test scenario: Verify that footnote markers have an enlarged tap target (padding) as specified in CSS.
• Found recommended test scenario: Verify that footnotes with multiple references only display a single back-reference link to prevent layout bloat.
• Found recommended test scenario: Verify that relative links to ../faq/code-analysis/which-metrics-does-codacy-calculate.md are valid and resolve correctly.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}