Proposal: Rename design.gitlab.com and reposition Pajamas as the product design system

Problem There's a fundamental confusion about what "Pajamas" refers to:

• The site: design.gitlab.com is branded as "Pajamas" and describes itself as "Resources, components, and design guidelines behind GitLab"
• The design system: We're also defining Pajamas as primarily focused on the GitLab product (GitLab.com, self-managed, dedicated)

This creates tension when we try to include content like:

• Brand guidelines (not product-specific but under "Pajamas")
• Potential future sections for tools like Switchboard
• Or resources that support design at GitLab more broadly (Figma libraries)

The result is confusion about scope, ownership, and exactly what content "belongs" in Pajamas.

Proposal

Rename and restructure design.gitlab.com to clearly separate the site from the product design system.

1. Rename design.gitlab.com to "Design @ GitLab" (or similar) to position it as a hub for all design resources at GitLab.
2. Position Pajamas as a subset under Design @ GitLab, specifically the product design system for GitLab.com, self-managed, and dedicated instances.
3. Create a design and IA that can accommodate the different design systems, guidelines, and resources across GitLab:
   1. Pajamas (product design system for GitLab.com, self-managed, dedicated)
   2. Brand guidelines
   3. Space for other platforms and tools (Marketing, Switchboard, Docs, etc.) to document their own systems or patterns as needed

Not all platforms may need dedicated space immediately, but the IA should be structured to support them as requirements emerge without requiring fundamental restructuring.

Benefits

• Eliminates scope confusion: Pajamas clearly means "GitLab product design system"
• Enables growth: Design @ GitLab can include resources beyond the product without diluting Pajamas' focus
• Positions brand as foundational: Brand guidelines serve as an umbrella relevant across all design at GitLab

Open Questions

• What should we name the broader design hub?
• Should we maintain design.gitlab.com as the URL, or consider something new?
• Who maintains the design hub long-term? If design.gitlab.com becomes a broader hub beyond just Pajamas, who owns the overall structure, navigation, and governance of the site?