Figma release cadence

[Kritvi-bhatia17]

Problem

Our current approach to managing Figma releases lacks structure, resulting in challenges in effectively communicating new Figma releases.

Description

• There is a need to establish a more structured approach to managing Figma releases.
• This involves implementing clear processes for announcing new features, deprecating properties within components, and managing other aspects of Figma releases.
• A structured approach will improve communication, organization, and coordination throughout the release process.

Notes:

Initial Goal: At the moment, we're focused on figuring out how to organize the pushing of our kits and documenting the process. We're also considering putting designers on a rotation to share this responsibility, similar to how developers do.

Later Goal: As we move forward, we may explore leveraging the same Slack bot currently used for dev-related announcements to organize tasks into "dev" and "design" categories.

---

Reference/related:

• [Figma] Written tutorials for using new AI features #722

General updates

Beta Give feedback

1. [Figma] Tutorial to use theme
2. [Figma] Tutorial or information about Non-variable vs Variable tokens
3. [Figma] Feature flag
4. [Slack] Make monthly announcement for Figma feature updates
5. [Figma] Slot and Slot groups
6. [Figma] Resizing

Announcements

Beta Give feedback

1. Create a task list for which all figma cadence will be required
2. Idea: Use threads if we have too many issue to call out
3. Idea: Maybe make a monthly update on slack of what we have done in the past month
4. Idea: How can this be automated, slackbot?

[thyhmdo]

@Kritvi-bhatia17 Our team discussed this with Juan. I wrote down tasks but we definitely can update these tasks if we need to refine them more. We'll need to have write-out guidance for each feature on the "Read Me" page and make a monthly announcement on Slack.

[Kritvi-bhatia17]

Got it @thyhmdo, thanks for the update. Sounds good!