Replies: 1 comment
-
I think we do struggle a lot overloading the term |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem statement
In this repository,
adobe/spectrum-tokens
, we are adding more than just token data.Specifically, we are currently adding JSON schema for component options and have plans to add support for capturing component anatomy data in the future.
History
Historically, the token data and management tools were part of a repository named
spectrum-dna
. It has been spectrum-tokens for a few years. We have since restructured the repository as a monorepo to manage several integrated packages, including token data manipulation tools. We are currently building a token diff report generating tool and moving the component options schema into their own package published on NPM.Proposal
Change the name from
adobe/spectrum-tokens
toadobe/spectrum-design-data
.Alternatives considered
I considered changing it back to
spectrum-dna
because I liked the name and historical context, but spectrum-design-data is the most descriptive of the purpose of the packages and data in this project.Consequences or Required Actions
Because I am not proposing changing the name of the @adobe/spectrum-tokens NPM package, most projects will not be impacted by this change.
It will impact the website for the token visualizer, but we could create a way to redirect to the new URL.
It will also impact the GitHub actions that keep the adobe/spectrum-tokens-studio-data repository in sync with this repository.
Beta Was this translation helpful? Give feedback.
All reactions