Audit docs versus guides taxonomy

[luke-hagar-sp]

Summary

Audit the developer site information architecture to distinguish official reference documentation from opinionated guides and getting-started content.

Context

The developer site update discussion identified confusion between docs, guides, generated API/reference material, and supplemental walkthroughs. The team agreed this is valuable but larger than the first site organization pass.

Scope

• Review each top-level docs section for guide-like versus reference-like content.
• Propose a clearer taxonomy for documentation, guides, and getting-started material.
• Include transforms in the review, since transforms currently mix reference-like and guide-like content.
• Identify redirects or sidebar changes needed for a future implementation.

[luke-hagar-sp]

Started this work on PR #1126.

Implemented a low-risk taxonomy pass that keeps existing URLs stable:

• Renamed the top-level sidebar labels to “Identity Security Cloud docs” and “Solution guides.”
• Added docs landing copy that distinguishes reference documentation, getting started content, and guide/tutorial content.
• Clarified that top-level Solution guides are for cross-cutting tasks, while transform and rule tutorials live under their domain sections.
• Added Getting started nav entries for “Build a transform” and “Build a rule.”
• Added transform-specific guide/reference entry points and disambiguated sidebar labels like “Transform guides,” “Transform operations,” and “Reference transform.”

Validation: IDE diagnostics on edited files are clean and git diff --check passes. I did not run a local build per environment guidance.