[P2] Audit: Content clusters are incomplete and not deeply interlinked

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: the site has workflow and cluster content, but the clusters are not yet complete enough to support a strong topical authority strategy. Existing pages need clearer pillar/supporting structure and tighter links back to tools, categories, and workflows.

Affected content areas:

• JSON ecosystem cluster
• API debugging cluster
• Network/security cluster
• CSS/design cluster
• Image processing cluster
• Encoding/hash cluster
• Future text/regex, DevOps, generator, and social metadata clusters

Reproduction steps:

1. Open cluster/tutorial pages.
2. Check whether each page links to a pillar page, sibling articles, relevant tools, and workflows.
3. Check whether each cluster has 8–15 supporting articles.
4. Inspect if content is deep enough or only a short checklist.

Expected behavior: each cluster should have a pillar page, supporting articles, internal links, tool CTAs, and schema.

Actual behavior: several clusters exist but are not fully built out or consistently interlinked.

Impact: weaker topical authority, lower content-driven conversions, and fragmented user journeys.

Proposed fix:

• Build 8 core clusters: JSON, API, JWT/Auth/Crypto, Logs/DevOps, Text/Regex/Unicode, Images/SVG/CSS, Generators/IDs, Social/Metadata.
• Add pillar pages and 8–15 supporting articles per cluster.
• Add internal links from articles to tools and workflows.
• Add article/FAQ/how-to schema where appropriate.

Acceptance criteria:

• Each cluster has a pillar page and at least 8 support pages.
• Every article links to at least one tool and one related article.
• Tool pages link back to relevant content.
• Cluster pages have consistent metadata and schema.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.