Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D design
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Primer
  • design
  • Merge requests
  • !174

Add Lifecyle page to design guidelines

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge maturity into master Aug 16, 2021
  • Overview 31
  • Commits 5
  • Pipelines 0
  • Changes 2

Created by: joelhawksley

This PR introduces a Lifecycle page to the design guidelines on primer.style.

Context

As part of our goals we're working on increasing the maturity of Primer, to make it more robust and consistent, and to create clarity for people working with the system. Our component libraries have diverged as we experimented and developed different parts of Primer, and we don't have all the pattern coverage we think consumers need across the system. These criteria are meant to establish baseline expectations for components in Primer as they mature over time.

Notes

We had originally titled these levels maturity statuses but I feel that the term Lifecycle better captures the intention for this to be a process that we move components through. I also used the term milestone in place of status for similar reasons.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: maturity