aws-amplify / aws-amplify/amplify-studio

Figma font family is not synced to Amplify

Open
#529 12 comments 0 reactions 0 assignees View on GitHub
feature-request general studio-ui
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

https://eu-central-1.console.aws.amazon.com/amplify/home?region=eu-central-1#/d3n0l36napjji5

### Region

eu-central-1

### Environment name

staging

### Amplify CLI Version

_No response_

### If applicable, what version of Node.js are you using?

_No response_

### What operating system are you using?

Windows

### Browser type?

Edge

### Describe the bug

The font type in Figma does not sync to Amplify. I tried both Abel and Barlow in my Figma file, and either way the text looks kind of like Times New Roman in Amplify. This issue was not there before Easter, and I have not opened or changed my Figma file or Amplify app in the meantime.

### Expected behavior

Font type in components is transferred from Figma to Amplify.

### Reproduction steps

Create component in Figma and sync to Amplify. Notice the font type.

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at the Figma-to-Amplify component sync flow by creating a component that uses Abel or Barlow, then reproduce the issue in the eu-central-1 staging app on Windows with Edge. Compare the synced component's font with its Figma source; done means the selected font family is transferred and rendered instead of falling back to a Times New Roman-like font.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, figma
Domain
design, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.