W3C home > Mailing lists > Public > public-design-tokens-log@w3.org > March 2020

Re: [community-group] [RFC] Format specification (#1)

From: Kevin Powell via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Mar 2020 22:34:18 +0000
To: public-design-tokens-log@w3.org
Message-ID: <issue_comment.created-593658796-1583188457-sysbot+gh@w3.org>
Zooming out a bit to the file format itself and an earlier recommendation to "pave the cowpaths." 

I'd be keen to poll potential consumers of this new spec (Sketch, Figma, Adobe XD, Scss, CSS Variables, iOS, Android, etc.) and see an aggregate list of what their current token structures look like. Are they all mostly JSON? XML? YAML? is there a "most common" file type already?

I would imagine Theo and/or Style Dictionary source code would be good locations to find that information.  

Could an MVP be a static file of key/value pairs (no functions, transformations, compilations) that the majority of those consumers could read?

It seems like some of the more advanced features could be added later, but could an initial goal be centered around accelerating adoption among consumers?

GitHub Notification of comment by kevinmpowell
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-593658796 using your GitHub account
Received on Monday, 2 March 2020 22:34:19 UTC

This archive was generated by hypermail 2.4.0 : Monday, 2 March 2020 22:34:20 UTC