tokens-studio / figma-plugin

Official repository of the plugin 'Tokens Studio for Figma' (Figma Tokens)
https://www.figma.com/community/plugin/843461159747178978
MIT License
1.32k stars 190 forks source link

[2.0] Sync provider form updates #2871

Open SamIam4Hyma opened 2 weeks ago

SamIam4Hyma commented 2 weeks ago

Each sync provider form should be customized for the provider:

  1. Header specific to the provider

    • [ ] Sync provider logo icon
    • [ ] Label that includes the provider name in the following structure: Sync to {provider-name}
  2. A content block for additional context

    • [ ] Short description specific to the provider
    • [ ] A hyperlink to the specific provider's docs on the tokens studio website (not the providers website), which opens in the web browser

✏️ Sync specific content attached (except Tokens Studio, covered separately)

📸 Screenshot of sync provider form annotate for #1 and #2 image


When the form includes the same form fields, the label and helper text/message should be consistent.

  1. FormField for "name"

    • [ ] message to say:
      This nickname appears on the settings page to help identify this sync provider from your list.
  2. FormField for "filePath"

    • [ ] label to say:
      Token storage location (file/folder path)
    • [ ] message to say:
      To store all tokens in a single JSON file, write the file name (Ex: tokens.json). Pro features, like themes, require a multi-file sync with tokens stored in a folder by writing the folder pathway (Ex: tokens). 

      Azure DevOps Form Changes

      FormField for "name"

    • Current label says Project Name (optional)
    • [ ] Label should say:
      Project Name
    • [ ] Ensure the form field is mandatory on the back end

JSONBin Form Changes

FormField for "secret"