Pajamas

Origin

Pajamas is GitLab's design system, open-sourced in 2019 alongside GitLab's broader open-core philosophy. It powers the GitLab.com web app and self-hosted instances — the entire DevOps lifecycle in a single product surface.

Governance

GitLab's central UX team owns Pajamas; the entire design-system development happens in the open through public issues, merge requests, and the same monthly release cadence as the rest of GitLab. Anyone can propose changes; the team reviews against documented criteria.

Known for

• End-to-end devops coverage — the system documents patterns for issues, merge requests, pipelines, security scanning, and analytics in a coherent surface.
• Open governance taken seriously — every design decision is debated in public issues, every component proposal goes through the same MR review as code, and the team's working agreements are themselves public.
• Documentation as a product — the design.gitlab.com site is itself an example of how a documentation surface should be built.

Underrated

• The handbook-driven culture spills into design — Pajamas's principles, content guidelines, and contribution process are documented at unusual depth.
• The empty-state and onboarding patterns for technical features (set up CI, configure security scanning) are useful references for any product asking users to do complex first-time setup.

Watch out for

• Pajamas is built for GitLab's specific surface — repos, pipelines, issues. Patterns assume that kind of long-tail technical user; consumer products need translation.
• Visual identity is GitLab-orange-heavy; the brand is the surface's identity, not yours to lift.