Decision Documentation for Communication

    For long term projects, without customer level 'release', (Eg While Implimenting a design SystemImplimenting a design System
    Design System is a collection of reusable Components, build using Atomicity and Sub-atomic Design Tokens particles that follow the guideline, behave consistently, and together work as t...
    ) it is good to have a time based change log. FigmaFigma
    Figma is a vector graphics editor and prototyping tool and is primarily web-based.


    Figma Resources



    Source

    Figma Website

    version control is not that efficient It doesn't provide Version per frame, comparison or search inside push note. Hence we use Google Doc.

    • Changelog as a consistent communication toolChangelog as a consistent communication tool
      Changelogs are a great way of effective communication. It provides a clear idea on what is done, and why it's done. Also, it communicates to the user about the value the new feature adds / problem ...

    Version Numbering

    • Two number version system
      • XX.YY
    • YY is any changes made in Single Source of Truth
      • Any designer can add it
      • Consider it more as Ship / Show of Ship-Show-AskShip-Show-Ask
        Ship/Show/Ask is a branching strategy that combines the features of Pull Requests with the option to continue shipping changes. There are three categories of changes in this method. They are Ship ...
    • XX is bi-weekly design meeting count
      • Objective is to do the Ask part of Ship-Show-AskShip-Show-Ask
        Ship/Show/Ask is a branching strategy that combines the features of Pull Requests with the option to continue shipping changes. There are three categories of changes in this method. They are Ship ...
      • Decisions are made, SST is updated

    Source

    • #Design