Design System Branching in Figma

  • Currently we follow Ship-Show-AskShip-Show-Ask

    Ship/Show/Ask - PR with ability to make changes
    Changes are categorized to three

    Ship (Merge to main, without review)
    Show (PR and Merge to Main)
    Ask (PR, then discuss, ...     format
    • Ship
      • Add to Design System
      • Take care of feedbacks, and act on it
      • Decision Documentation for CommunicationDecision Documentation for Communication

        For long term projects, without customer level 'release', (Eg While Implimenting a design System) it is good to have a time based change log
        Changelog as a consistent communication tool]...
      • Changelog as a consistent communication toolChangelog as a consistent communication tool

        Write changelogs Consistently. (I prefer Outline Notes format). It provides a clear idea of what the team has achieved and when.
        Also, it communicates to the user about new features, the v...
    • Show
      • Add as a variant to existing component
      • Cleanup once we are clear
    • Ask
      • Add as a new component
      • Use .$NAME-Context
      • Then Discuss on bi-weekly update

Source

  • §Design Private or Broken Links
    The page you're looking for is either not available or private!
  • §Product Private or Broken Links
    The page you're looking for is either not available or private!