Refactor developer site information architecture

[luke-hagar-sp]

Summary

• Reframe the homepage and global metadata around SailPoint Developers instead of the broader “Developer Community” label.
• Reorganize nav/footer entries for documentation, API specs, getting started/tools, community policies, videos, and Developer Relations support.
• Clarify tools, community, and video-library pages with better routing, labels, filter display names, and contribution CTAs.
• Address Audit docs versus guides taxonomy #1122 by clarifying docs-versus-guides taxonomy, preserving existing URLs, and making transform/rule guide and reference entry points more explicit.

Test plan

• Checked IDE diagnostics for edited files; no linter errors found.
• Ran git diff --check for the taxonomy update.
• Did not run a local Docusaurus build per environment-safety guidance.

Follow-up issues

• Confirm API sidebar duplication fix #1123
• Add analytics for homepage and navigation engagement #1124
• Clean up Discourse video tags and filter taxonomy #1125

Made with Cursor

[claude]

Large IA refactor (28 files: nav/footer restructuring, homepage redesign, two new pages, video-library refactor) — no bugs found, but it's worth a human eye to visually verify navigation, the new homepage hero, and the multi-select video filters render as intended.

Extended reasoning...

Overview

This PR refactors the developer site's information architecture across 28 files. Changes include: (1) rebranding copy from "SailPoint Developer Community" to "SailPoint Developers" across docs, metadata, OG/Twitter tags, footer, and announcement bar; (2) restructuring navbar.ts (new Documentation dropdown with IIQ links, dropdown parents now have to targets, "Tools" renamed to "Getting started", Video library promoted under Community); (3) restructuring footer.ts (added Videos, Community policies, Developer Relations team; removed Twitter link); (4) two new pages (devrel-team.tsx, community-policies.tsx) composed from existing HomepageBasics/HomepageTeam components; (5) homepage hero replaced with a 4-card resource grid and the embedded YouTube video removed; (6) VideoSidebar filter logic rewritten to genuinely support multi-select (previous logic combined product/video tag state awkwardly via lodash forEach); (7) tag display-name mapping centralized; (8) the previously commented-out api-specifications.md was uncommented and given slug: /api to serve as the API dropdown landing page.

Security risks

None apparent — this is a public docs/marketing site. No auth, crypto, or permissions code touched. The CSP in docusaurus.config.ts is unchanged. No new external resources are loaded.

Level of scrutiny

Moderate. The code is non-critical (docs site), but the surface area is broad and most regressions would be visual (navbar layout, homepage hero rendering, dropdown parent links, filter UX). I verified that the navbar's new dropdown-parent to targets resolve to real slugs: /docs/iiq/plugin-developer-guide maps to docs/plugin-developer-guide.md, and the uncommented api-specifications.md with slug: /api does not collide with the still-commented identity-security-cloud.md (which would have shared the slug).

Other factors

• No bugs were found by the bug hunting system.
• Refactors in VideoCards/VideoSidebar look reasonable (useCallback for stable references, removing the lodash forEach dependency, deriving filters from a single source of truth instead of mutating shared state).
• One minor oddity: src/pages/index.tsx wraps Layout in React.memo with a double cast (as unknown as ...). Functionally harmless but unnecessary, and the cast loses Layout's real typing — a human reviewer might want to flag or accept.
• The author noted they intentionally did not run a Docusaurus build per environment-safety guidance, so build verification is still outstanding.

[github-actions]

🌎🌎🌎 Visit the preview URL for this PR HERE
built from commit 75a293c