Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Pajamas Design System
Pajamas Design System
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 276
    • Issues 276
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 15
    • Merge Requests 15
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-services
  • Pajamas Design SystemPajamas Design System
  • Issues
  • #740

Closed
Open
Opened Oct 23, 2020 by Jeremy Elder@jelderglMaintainer

Pajamas website refresh

Why?

The Pajamas website has met our needs to this point, but there are several feature lacking if we want it to be the go-to resource we want it to be.

What

Here are a few ways that the site could be improved:

Responsive

We need to consider responsive behavior and patterns more holistically. The current site has some responsive behavior, but many features and views are unreliable.

CleanShot_2020-10-23_at_09.23.10

Search

There is currently no way to search on the site. It would be helpful to have both tagged and full content search available.

Accessibility

There are several things to consider here, but one of the main ones is the navigation. A <details> element is used for some of the navigation, and could benefit from an update. Making more use of landmarks and regions could help too.

Dogfooding GitLab UI

The site uses separate styles from GitLab UI. The site instead should be a testing ground for GitLab UI styles and components. This would also help prevent the need to duplicate some styles (like colors) which can easily get out of sync. It would also be great to have GitLab UI feel more integrated and less like an embed or a reference. If the site was built on Vue, could we build out examples the same way they’re included in the product with templating instead of pulling from Storybook?

Reliability

This error happens often when viewing the public site.

CleanShot_2020-10-23_at_08.22.49_2x

More visual and contextual examples

The site is very text-heavy, and users would benefit from concepts also being represented visually. This doesn’t mean we have to use literal UI screenshots that could become out of date, but representative visuals that demonstrate concepts in a more timeless way.

Before After
CleanShot_2020-10-23_at_09.42.31_2x CleanShot_2020-10-23_at_09.43.08_2x
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-services/design.gitlab.com#740