Skip to content

Research possibility of Figma for better "publish" handling #5375

@mj-hof

Description

@mj-hof

Description

  • Check if branching is a problem
  • Check if its possible to clean cache in Figma
  • Gather insights of software trouble shooting for Figma publish feature
  • consider different split ideas

DEV handover checklist

DEV handover done with: @ADD_DEV_NAME_HERE

Component

  • defined main component name
  • defined which support components are used and how they are named
  • component has been hidden from publishing (until its implemented)
  • the following is explained to the DEV and documented:
    • all properties
    • truncation
    • responsiveness / wrapping behavior
    • min / max width

Documentation

  • category for Figma and Storybook is defined
  • examples that should be shown in Storybook are defined and documented in Figma (documentation file)
  • component status "planned" has been added to the docs overview

Other

  • DEV has either refined an implementation ticket or at least created a blank issue with a title
  • follow-up UX tickets were created if necessary (add links below)
  • expand (figma) documentation with new results/decisions
  • make sure the results are transferred into the corresponding implementation or concept ticket

Metadata

Metadata

Assignees

Labels

uxRequires UX/UI design

Type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions