So, you want to create a new Design System? Great idea! A shared library of components and guidelines between designers and developers will improve everyone's productivity. But how do you design a Design System that won't become obsolete as soon as a new JavaScript framework comes out (tomorrow)?
I propose we explore some concrete strategies to free yourself from dependence on frameworks and libraries. Here's a hint: use web standards! We'll talk about design tokens, CSS, package architecture, and Web Components to develop a future-proof Design System. Want to switch JS frameworks? No problem. Ditch Tailwind CSS? Easy. Create a simple HTML page? Oh yeah!
This session is primarily aimed at large-scale Design Systems used by multiple teams on different frameworks, but the proposed architecture can easily be adapted to simpler projects.