@nik_hazell Thanks a lot! Hope you'll give it a try, I think you'll enjoy it!

@nik_hazell Thanks, Nik! Feel free to share with your design team this Figma file example. It would help get started with Specify. Keep us posted :)

@charlene187 Thank you Charlene 🙏! Glad to hear that and yes we do have the px-to-rem 🔥

@charlene187 Thanks a lot! We do have a parser for px-to-rem right here. You can browse all the parsers. They're all available on the output pipeline so you can transform the data to your needs 😃

Thanks @patricia_bsc_kairn 🙌

@patricia_bsc_kairn Thank you so much Patricia! Your support means a lot to us 🙏 Keep us posted how the trial goes, we're happy to help! cc @chuckn0risk P.S. Also, I'd love your thoughts on the onboarding flow!

@patricia_bsc_kairn Oh yeah, thanks a lot Patricia!

@yassersultan Thank you so much Yasser! Yep, it was fully made by my little hands (2D, 3D, Sound Design) and of course I was helped a lot by the marketing crew 💪 Next week, Im gonna post a long and detailed breakdown of the whole process on my Behance page!

@thibaut_crepelle You sir and your little hands have some mad skills! :) Loved the part where the voice over says "designers connect your fav design tools like Figma..." and the pipe animates to connect with that "device". Will be great if you can comment the Behance link here, would love to read it.

@yassersultan Ahahah this little part definitely makes viewers happy apparently! Well I'll reply to your comment with the link as soon as it is online ! Cheers

@clemnt WOW, Clément! Thank you so much for your support 🙏

@clemnt Thanks a lot @clemnt 💜 Your support means a lot to us!

@clemnt Couldn't agree more Clément! Design systems are now the way to go but they clearly fall into the "easier said than done" side of things. Specify helps teams feed and consume their organization's branding through their design system. This offers the flexibility organizations deserve to maintain their brand at scale across all their target platforms 👍

Hey @haenschenhans, thanks a lot for your kind words! 1. Currently, you can either import tokens from Local Styles or by Frame (on the “Set up your connection” configuration step). By selecting frames over local styles you must be able to get more granular results. You can find examples of frame-based definitions on https://www.figma.com/community/file/1078015059752018461. Moreover, on the development side, you’ll be able to filter, format, and assemble almost any style or asset file. We are actively working on improving this experience, mainly filtering and data enhancing. Stay tuned ⚡️ About the nesting and grouping of the tokens, it is not currently available, anyway, we have it on the roadmap 😃 2. Aliases are a pretty hot topic within the community. The least we can say, we did not come to a consensus yet: the limit between aliasing and inheritance, the management of the aliases tree, or even how to drive users to define the right level of layers for each kind of variant... That’s why conversations are actively going within the Design Tokens Community Group to build a future specification on that side. Specify is tool agnostic, our goal is to come up with the right abstraction. Since it’s not possible yet, we’ve been internally researching for solutions to build our very own aliasing system. Here are the guidelines we encourage our users to follow to use Figma aliases along with Specify: https://www.figma.com/file/jTzVNLbtK5eFjUrP3EAm6z/Global-and-Alias-styles-in-Figma

@moreaux_antoine ah, you're right - i could import just frames with the styles I need. stupid me :D and thx for your opinion on the nesting - will check out your guideline!

@haenschenhans Keep us posted, Johannes! We're here to help :) cc @moreaux_antoine @chuckn0risk

@christophepas Thanks Chris! looking forward to it :)

@christophepas Thanks a lot!

@dley_de Thank you, Daniel!

@dley_de WOW Thanks Daniel! Keep us posted! HUGE S/O @thibaut_crepelle for the video

@michaelmangial1 WOW Thank you so much for your ever-lasting help and support, Michael 🙏 Indeed, there has been a lot of hard work, and there's more to come. Our CEO @valentinchrt shared our vision and what's next in this Thread. It's just the beginning 🙂

@michaelmangial1 Thanks for your support Mike 🙏

Thanks for your kind words @joyboustani We aim to simplify product teams life and we won't stop there 💪

@joyboustani Thanks Joy! Mentionning Segment is indeed a perfect analogy. Orgs have been managing their analytics data by collecting, storing and distributing them. In our view, it makes perfect sense doing the same for design data 👍

@shivi_jalota Thank you, Shivi! We're a small team and worked hard on this launch. S/O @thibaut_crepelle for the intro :)

@shivi_jalota Thanks a lot! 🙏

Hey @galaxyx7 😊 Thanks for your message! We’re a Design API that helps you distribute and maintain your brand identity, such as your styles and assets, on all your digital products. Basically, all you have to do is to connect your Figma files and your codebases to Specify. Then developers can automatically receive design tokens via GitHub pull requests or using our CLI. The main thing is, you can tailor shape your design data to make it compatible with your technical stack. In short: in early 2017, we were working in different teams as product designer, developer & product manager in different companies. After seeing how product teams were struggling to properly collaborate together on building and maintaining their digital products, we decided to build something that helps them solve all their problems ⚡ In 2018, we built the first version of Specify which was a desktop app that provided: - A design components and styles library extracted from Sketch - A documentation tool - A component inspect tool - A delivery pipeline distributing design tokens to GitHub and GitLab. That was an "all-in-one tool“ for Design Systems. In late 2019, following how the market evolved, the fast growth of Figma and the evolution of the product teams habits and workflow, we decided to revamp Specify to a more flexible version 😊 That's how the first Design Data Platform came to life 💜

Thanks a lot Yanis ! 🔥

@madorakkusu Wow Yanis, thank you so much for your comment! Please go ahead and give Specify a spin. To start, you can share this Figma file that may help you index your design tokens and assets. Also, read our API docs to learn more how to pull them into fully configurable files. Hope it helps you get started! Keep us posted :)

@piotr_pawlowski Thanks a lot! 🙏 We're working hard to bring the best possible product. Hope you'll enjoy it!

@gilles_bertaux Thank you Gilles, your words mean a lot!

@gilles_bertaux Thanks Gilles 🙏

@gilles_bertaux Thanks a lot!

@gilles_bertaux In case you missed it, we detailed all the visual assets we designed for the launch in this Thread. Which one is your favorite?

@ziad_ghalleb1 Hey Ziad, thanks for your kind words! Keep us posted, we'd be happy to support you setting it up :) Ping @chuckn0risk

@aksakal Hi Serhat, thank you for your support! That's it :) Basically, you connect your Figma files and your GitHub repositories, and boom they're in sync. To quote @romaindillet from TechCrunch: "Specify automagically collects, stores, and distributes your design tokens and assets."

@colorjunkie Wow thanks Antoine 🙏 Our design team puts so much care into the details. We're glad you like it. We detailed all the visual assets we designed for the launch in this Thread. What's your favorite one? S/O @yannglt @louis_charadon @thibaut_crepelle

@colorjunkie Thanks a lot, Antoine! 💜

@kyranschmidt That's so kind, Kyran. Thanks!

@kyranschmidt Thanks, Kyran! Keep us posted as you try out Specify, we're here to help :) cc @chuckn0risk