Design Systems, Code-side - Collaborative devtool to build and ship great Design Systems - by @divRIOTS Chat with us 👉 https://xitter.cf/t.co/zqpe4WgrwY

Joined April 2020
Backlight.dev retweeted
Y'all don't need to fall for this trick. Add html to design plugin to your resources and you can edit any web design of your choice.
Steal my collection of fully editable Website Design Inspiration in Figma ✨ You can get them for FREE just for 24 hours, then I'll delete it 🕐 Like & Comment "Send" to receive the link. Must be following so I can DM you 💬
2
1
1
6
1,611
Backlight.dev retweeted
My jaw dropped after coming across @backlight_dev. As a #designsystem principles advocate, this tool seems crazy remarkable and complete.
1
5
While some are enjoying the ☀️ we gathered some of the best #designsystem tools out there for you to catch up on when you are back at your keyboard 🤗 Including: • Developers tools • Designers tools • #DesignTokens • Documentation • Content Design backlight.dev/mastery/best-d…
1
2
4
Can you have a #designsystem with multiple technologies? Most certainly! Our lead designer @th4is_ds summarized it👇
1
3
6
Icons 👉 How can something so tiny mess up a #designsystem so quickly, if not managed properly from the start? 🤯 backlight.dev/blog/how-to-ma…
3
1
11
Build your #designsystem from Scratch, the painless way, with @th4is_ds & @m4d_z 🤗 If you missed your spot at #SunnyTech, you can still grab places for their workshop in the coming @ReactFinland 👇 react-finland.fi/workshops/#…
3
5
New feature in Backlight: Export your #designsystem doc into static pages 🤯 👉 Single command line 👉 High-performance pages 👉 Host it anywhere See how 👇 backlight.dev/docs/export-do…
2
6
5 things to avoid when building a #designsystem #designsystems, if built poorly, can be costly for product teams, and hard to recover from. @soniasinglas gathered 5 things to avoid in order to help you build a successful design system 👇 backlight.dev/blog/5-things-…
2
6
How to best name #designsystem elements 🤓 If naming is an art, naming conventions for #designsystems mostly come down to logic and clarity. Here is why you should care, and how to do it properly 👇 backlight.dev/blog/naming-co…
4
8
Tuesday trick 🤯 @figma design tokens edit, pushed to the code, automatically 😎 - Change token in @Figma - Push changes - Let @Github do its magic - Code diff review in @Github - Visual review in backlight.dev - Enjoy 🤗 See how 👇 backlight.dev/docs/figma-tok…
5
1
14
This week in ‹Coding #DesignSystems› 🔥 Learn about Modern #CSS new features, and components crafting with #nunjucks and @eleven_ty in a static Web content #designsystem with @5t3ph and our very own @m4d_z,🤗 The replay is already available👇 youtube.com/watch?v=V9tI519-…
4
15
The 3 pillars of a successful #designsystem ✔️ In 2021 60% of #designsystems failed 🪦 according to their users. Out of sync documentation, poor adoption, non-existent contribution, the list of reasons goes on. How to be part of the successful 40% 👇 backlight.dev/blog/the-3-pil…
3
7
3 reasons why your #designsystem needs content design 🧵👇 Think about it, #designsystems actually have a lot of content: - In the onboarding content - In the docs - In the UI itself Yet, many design system teams don’t include a #content designer or #UX writer 🤔
1
7
11
New in Backlight 🔥 Prop component in documentation kit - Automatically generate Props documentation from your component code documentation See how 👉 backlight.dev/docs/md-vue#co…
1
5