Thread — #design-systems · Quill

# design-systems

Patterns, components, and tokens. Decisions in main pane; WIP in threads.

Iben Faro 3:58 PM

Migration script ready when you are. Touches 218 files; nothing structural.

Renske Goh 10:24 AM Thread open

Filed the proposed token names. The one to argue about, I think, is color.surface.2: should we keep the numeric ladder or move to semantic names like raised / sunken?

IF OB LH 4 replies · last from Iben, 2 min

Oren Bahir 10:28 AM

Pushing the patch now — call me if the runner doesn't pick it up by noon.

Message #design-systems…

Thread

# design-systems · 4 replies

Following

Renske Goh 10:24 AM

Filed the proposed token names. The one to argue about, I think, is color.surface.2: should we keep the numeric ladder or move to semantic names like raised / sunken?

👍 3 🎯 1

4 replies

Iben Faro 10:31 AM

Semantic. The numeric ladder is fine right now but it locks us into a linear scale we don't actually have — surface 3 doesn't exist and we keep almost-naming it.

Oren Bahir 10:33 AM

Agreed on principle. The cost is the migration — but Iben's script handles it. raised / sunken works for me; would also accept elevated / inset.

💯 2

Lior Harkavy 10:46 AM

Push for raised / sunken — it matches what we already say in design crits. elevated is technically a shadow concept and we'll re-conflate them in six months.

Iben Faro 10:48 AM

Strong +1. I'll rename in the spec and re-run the migration tonight on staging. Decision in the channel by EOD?

🙌 3 ⏱ 1

Also send to #design-systems

Decided: raised / sunken. I'll write up the rationale in the main channel and lock the spec at v0.6.1 tonight.

Only people in this thread will be notified · ⌘↩ to send