Documentation, API reference, SDKs, GitHub, code samples, and system status are all named in the public developer navigation.
Support
Support should be easy to scan, not buried in a footer.
The public company navigation already names the important surfaces. This page organizes them so developers, operators, and buyers can find the right path quickly.
Support map
Public support surfaces already implied by the ecosystem.
The corporate site, agency surface, and AI surface should all feed into a single support model.
The public resources navigation includes updates, research, whitepapers, webinars, case studies, and a help center.
Public company navigation includes careers, culture, diversity, contact, and legal and privacy surfaces.
The current public footprint should route visitors clearly across the corporate, agency, and AI surfaces.
Key destinations
The support page should point people somewhere real.
Where a direct URL is public today, it should be linked. Where the surface is still maturing, the page should still reserve the right category.