Automattic / Automattic/jetpack

Gutenberg: De-hardcode SCSS variables in our blocks

Open
#11,844 3 comments 1 reaction 0 assignees View on GitHub
[Focus] Blocks Enhancement Task
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

In the Markdown block (~and probably in other blocks already~ and many more), we hardcode colors, fonts and other styles that could originally are defined in Gutenberg.

Let's find a good way to manage them - also see some suggestions in https://github.com/Automattic/wp-calypso/pull/27450#discussion_r220529958

Example:

https://github.com/Automattic/wp-calypso/blob/8ad80271e0e97f627d1fafb99c74dc28ef823143/client/gutenberg/extensions/markdown/editor.scss#L1-L8

Contributor guide

Open the contributing guide

Research direction

Start with the Markdown block stylesheet at client/gutenberg/extensions/markdown/editor.scss, then review the suggestions in wp-calypso PR 27450. Identify how Gutenberg defines the shared colors, fonts, and other styles before deciding how the blocks should consume them. Done means the hardcoded SCSS values are replaced consistently across the affected blocks.

Written by the indexing model from the issue text.

Assessment

Tech stack
scss
Domain
frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.