跟读练习: Tokens vs Variables in Tokens Studio for Figma | Variables Series - 通过视频学习英语口语

Hi designers and tokens peeps!

Sam A.M here on behalf of the Token Studio team to talk about variables.

In this video, you'll learn about the differences between Figma's variables and design tokens, as well as the features in the Token Studio plugin for Figma

that allow you to create variables that are synced to design tokens.

This is the first video in a series where I'll walk you through all things variables

in Token Studio step by step using a community file I've created for you so you can follow along.

But before we get into the hands-on stuff, I want to take a step back

and think about what is a design token and how is that different from a variable?

Well, it depends on who you ask.

So if I give you a second to think about it, what do you think a design token is?

Me personally, I define a design token as a design decision.

That's a pretty simple response.

If you want to go deeper, I could say it has a human readable name and it follows a specific format and we use it in code.

But I was really curious, what does the community think?

So I sent out a little survey and I asked them, what is a design token?

If someone new on your team asked you, what would you say?

Well most of us agree that a design decision is a part of what a design token is.

A lot of people also mentioned this concept of design to code, or collaboration between development and design, which is pretty awesome.

And a small percentage of people mentioned variable, which is not exactly right.

But we're going to go over that in a sec.

It looks like we're all kind of on the same page about what a design token means, and that it has something to do with a design decision, but the rest of it is a little bit fuzzy.

And I think that's understandable given how new of a concept design tokens are.

You may be thinking, how new is it?

The term design tokens originated at Salesforce.

If you head to the Token Studio website under Getting Started, we've got more details on the design tokens origin story that you can check out.

In 2019, a group of people got together to form the Design Tokens Community Group.

They've created a draft of what they propose the web standards for Design Tokens should be.

They host these specifications on the W3C Community and Business Groups pages.

So, when you hear us token nerds talking about the spec, or W3C, or WC3 because we mix it up all the time,

we're talking about this document.

I'll drop the links to the most recent draft of the spec

and their Twitter page in the description below below in case you want to check that out.

But if reading a long technical document isn't your thing, don't worry, I got you.

So how does the W3C spec define a design token?

Design tokens are a methodology for expressing design decisions in a platform agnostic way so they can be shared across different disciplines, tools, and technologies.

They help establish a common vocabulary across organizations.

So I wasn't totally wrong when I said a design token is a design decision.

There's just some other things to consider as well.

And it turns out the community has a pretty solid understanding of what a design token is, which is awesome.

And now that we know what a design token is, we can look at variables from Figma.

So like I mentioned before, a variable variable is not a design token.

And actually, if you look at the Figma documentation for variables, they say a variable is a representation of a design token.

And here it says a variable is a way to create design tokens.

Over here it says a variable is a way to implement design tokens.

So to simplify this, I'm going to group these things together and say a variable is not a design token.

A variable is a representation of a design token.

Just like a style or even a design property can be a representation or an expression of a design token in Figma.

Alright, before we get our hands dirty and start working with tokens, I want to talk about the different names for the same things between variables in Figma and Token Studio.

Because the difference between collections and modes and themes and theme groups and theme switching and mode switching is all very confusing.

I don't know about you, but I must have called a variable a variant at least a million times.

We already know that a design token can be represented in Figma as a variable.

What you might not know is a design token is identified by its name.

So it makes sense that the name of a design token will match the name of its variable.

Now, there are some specifics about how you name your tokens so that they are grouped properly, which helps in organizing your tokens or variables.

And there are some specs on what can and cannot be included in a token's name, as well as a whole debatable conversation about how to name your tokens.

So I'll cover naming tokens and variables in a future video.

In Figma, variables live in collections, whereas in Token Studio, design tokens live in token sets which are grouped into themes.

So a theme group is actually the same thing as a collection.

And this is because, if you'll recall, that tokens are supposed to be platform agnostic and use a common language.

It means under the hood, design tokens live in JSON files.

The Token Studio plugin is essentially a no-code way to write a JSON file full of design tokens tokens

that can be transformed into any programming language using code.

In fact, you can edit your tokens via the JSON editor from within the Token Studio plugin

if you're faster at editing code.

I am not.

You can also sync your JSON files with code using one of our integrated sync providers.

We have design tokens living in token sets, which are grouped into themes.

And those theme groups will create collections of variables.

Now, what about modes for say, different brands?

In this example, I'm managing four different brands.

They all have a different brand color, but that's about the only thing that's different.

It's a pretty simple example.

So in Token Studio, I would create a token set for each brand.

They would have the same tokens with the same names, like brand color, primary default,

different values to reflect each brand's unique color.

When we create a theme group for brand colors, and we create different themes within that group, I'm going to create brand A as a theme, brand B as a theme,

brand C as a theme, and so on.

They will all live in the brand colors theme group.

We'll use the Token Studio plugin to create variable collections, and it will automatically use Figma's modes feature to allow for the variables with the same names,

which match the design tokens with the same name, to live in a collection with the same name as the brand colors theme group.

These are organized into modes.

The name of each mode matches the name of the theme.

So, token names match variable names.

Theme group names match collection names and the names of themes match modes in Figma.

It's important to remember that variables in Figma are still in beta.

They don't have variables to match every token type that exists.

In fact, there are many, many more types of tokens than there are variables.

I'll go through each variable type and their matching token types in their own videos.

So to recap, We learned that a design token expresses a design decision in a common language that is platform agnostic.

And a variable is not a design token.

A variable is a representation of a design token in Figma.

Design tokens follow the W3C spec

and you can use the Token Studio plugin to create variables that are synced to design tokens.

In Token Studio, design tokens live in token sets, which are a no-code version of a JSON file.

Tokens living in token sets are grouped into themes, and those theme groups can be used to create variable collections in Figma,

with modes that match the themes in Token Studio.

So, while a variable is not a design token, they do have a lot of similarities.

If you want to learn more about creating and syncing design tokens to variables, to variables, be sure to check out the other videos in the variables series.

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

跟读练习: Tokens vs Variables in Tokens Studio for Figma | Variables Series - 通过视频学习英语口语

为什么通过这个视频练习口语？

语法与表达在上下文中

常见发音陷阱

什么是跟读法？