Design Systems at Scale. LIVE TOMORROW!!! 🔗 **Source:** [Design Systems at Scale. LIVE TOMORROW!!!](https://www.youtube.com/watch?v=Wq_E577JV6c) > [!note]+ Document Notes > tags: [design-systems, design-tokens, figma] > author: [MISSING] > source: YouTube > reference: https://www.youtube.com/watch?v=Wq_E577JV6c > date created: 2024-12-19 11:37 > > # 🏷️ Title: Design Systems at Scale. LIVE TOMORROW!!! > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Register for live session — design systems scaling #design-tokens - [H2] Prepare questions about token structure — live Q&A opportunity #learning - [H3] Review current design system complexity — token audit preparation #audit ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Token Studio](https://tokens.studio/) - [Figma Design Systems](https://www.figma.com/design-systems/) ## 📝 Summary - Live educational session on scaling design systems with fewer design tokens - Focus on reducing complexity while maintaining functionality in Figma/Token Studio - Expert-led hands-on session covering advanced token architecture - Interactive Q&A format with Token Studio expert Marco - Addresses common overwhelm with token proliferation in design systems ## 📖 Main Content This promotional video announces a live educational session focused on solving design system complexity through strategic token reduction. The session promises to address the common problem of design systems becoming unwieldy due to token proliferation. Expert Marco from Token Studio will lead hands-on demonstrations covering fluid typography, multi-brand systems, and mathematical token relationships. The format emphasizes practical implementation with live Q&A for immediate problem-solving. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/Wq_E577JV6c?t=0) — [H1] Problem identification: Token overwhelm - Key idea: Design system complexity creates maintenance burden - Evidence: "Are you overwhelmed by the number of tokens in your design system? I am." #### ⏱️ [00:05](https://youtu.be/Wq_E577JV6c?t=5) — [H2] Solution promise: Fewer tokens, less work - Key idea: Strategic token reduction maintains functionality while reducing complexity - Evidence: "build complex design systems in Pampot with fewer design tokens, which means less work" #### ⏱️ [00:12](https://youtu.be/Wq_E577JV6c?t=12) — [H3] Coverage area: Fluid typography systems - Key idea: Typography scaling can be systematized with mathematical relationships - Evidence: "We're going to cover fluid topography" #### ⏱️ [00:15](https://youtu.be/Wq_E577JV6c?t=15) — [H2] Coverage area: Multi-brand architecture - Key idea: Single system can support multiple brand expressions - Evidence: "multibranding" #### ⏱️ [00:17](https://youtu.be/Wq_E577JV6c?t=17) — [H1] Structural guidance: Scalable token organization - Key idea: Token architecture requires strategic hierarchy planning - Evidence: "how to set up your tok structure that it's scalable and maintainable" #### ⏱️ [00:22](https://youtu.be/Wq_E577JV6c?t=22) — [H2] Architecture principle: Core vs semantic separation - Key idea: Design system layers require clear boundaries and purposes - Evidence: "what should be in your systems core, and what should be in your spantics" #### ⏱️ [00:27](https://youtu.be/Wq_E577JV6c?t=27) — [H3] Advanced technique: Mathematical token relationships - Key idea: Computational approaches can generate consistent design variations - Evidence: "how to use math in your tokens and extrapolate things" #### ⏱️ [00:32](https://youtu.be/Wq_E577JV6c?t=32) — [H2] Expert involvement: Token Studio specialist - Key idea: Industry expert provides authoritative guidance - Evidence: "proper expert, Marco from Token Studio" #### ⏱️ [00:36](https://youtu.be/Wq_E577JV6c?t=36) — [H3] Format benefit: Live interaction and community - Key idea: Real-time problem solving creates immediate value - Evidence: "Join us live to nerd out together" ## 📚 References - [Token Studio](https://tokens.studio/) - [Design Systems Handbook](https://www.designbetter.co/design-systems-handbook) - [Figma Design Systems](https://www.figma.com/design-systems/) ## 🗣️ Paraphrase - Many designers struggle with design systems that have grown too complex due to excessive token proliferation - Strategic token architecture can maintain system flexibility while dramatically reducing maintenance overhead - Expert-led education with hands-on examples provides practical solutions for real-world design system challenges ## 📰 Newsletter 🎨 **Scale Your Design System Without the Complexity** Feeling overwhelmed by design token management? You're not alone. Join Token Studio expert Marco for a live session on building complex design systems with fewer tokens and less maintenance overhead. **What You'll Learn:** - Fluid typography systems that scale mathematically - Multi-brand architecture strategies - Core vs semantic token organization - Mathematical relationships in design tokens This hands-on session promises practical solutions to common design system pain points, with live Q&A for immediate problem-solving. **Resources:** [Token Studio](https://tokens.studio/), [Figma Design Systems](https://www.figma.com/design-systems/), [Design Systems Handbook](https://www.designbetter.co/design-systems-handbook) ## ✅ Action Items #### Design - Token audits: inventory current system complexity, identify redundancies - Architecture planning: core/semantic separation strategies - Mathematical systems: fluid typography implementation - Multi-brand support: scalable brand token architecture - Documentation: token usage guidelines, maintenance procedures ## 🧪 Hypotheses - Strategic token reduction improves design system maintainability without sacrificing functionality - Mathematical relationships in tokens create more consistent and scalable design systems - Core/semantic token separation reduces cognitive load for design system users - Live expert guidance accelerates design system optimization learning ### 📊 Methodology - Comparative analysis: before/after token architecture complexity - User research: designer experience with simplified vs complex token systems - Performance measurement: maintenance time reduction with strategic token organization ### ❓ Questions - What specific mathematical relationships work best for fluid typography systems? - How do you determine optimal boundaries between core and semantic tokens? - What metrics indicate when a design system has too many tokens? ### 🔮 Future Research - Automated token optimization tools and AI-assisted design system architecture - Cross-platform token synchronization in multi-tool design workflows - Design system governance frameworks for large organizations ### 💡 Implications - Practice: Design teams can reduce maintenance overhead through strategic token architecture - Education: Live expert sessions provide immediate value for design system practitioners - Tooling: Token Studio and similar tools enable more sophisticated design system management - Community: Collaborative learning accelerates design system maturation across the industry ### 🧠 Learning Styles Assessment Reading level estimate: 8th Grade #### 👀 Visual learners - Present: Video format with likely screen sharing demonstrations - Improve: Downloadable token architecture diagrams, before/after complexity comparisons #### 🔊 Aural learners - Present: Live presentation with expert narration - Improve: Recorded session for replay, podcast-style summary #### 🗣️ Verbal learners - Present: Expert explanations, technical terminology definitions - Improve: Glossary of design system terms, analogies for complex concepts #### 🧩 Kinesthetic learners - Present: Hands-on demonstrations in design tools - Improve: Step-by-step exercises, downloadable starter files #### 🧠 Logical learners - Present: Structured progression from problem to solution - Improve: Decision trees for token architecture choices, comparison matrices #### 🧑‍🤝‍🧑 Social learners - Present: Live Q&A, community interaction opportunity - Improve: Breakout discussions, peer token system reviews #### 🧘‍♀️ Solitary learners - Present: Individual learning opportunity - Improve: Self-assessment checklist, private practice exercises #### 🌿 Naturalistic learners - Present: Systems thinking approach to design token organization - Improve: Ecosystem analogies, organic growth vs pruning metaphors ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video likely includes verbal explanations - Improve: Complete transcript, detailed alt text for visual demonstrations #### Keyboard navigation - Present: Standard YouTube player controls - Improve: Keyboard shortcuts documentation, accessible demo files #### Contrast and readability - Present: Standard video player interface - Improve: High-contrast design system examples, readable token naming conventions #### Text resizing and reflow - Present: Video content adapts to player size - Improve: Supplementary text materials that resize properly #### Media and captions - Present: Video format - Improve: Auto-generated captions, downloadable transcript #### Forms and interactions - Present: Basic video player interactions - Improve: Accessible registration forms, inclusive Q&A submission ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language presentation - Improve: Multiple language options, global design system examples #### Inclusive language - Present: Technical but accessible language use - Improve: Defined jargon, plain-language alternatives #### Neurodiversity support - Present: Structured presentation format - Improve: Content outline, predictable session flow #### Representation - Present: Expert knowledge sharing - Improve: Diverse speaker lineup, varied company examples #### Psychological safety - Present: "Nerd out together" creates welcoming tone - Improve: Clear participation guidelines, multiple question formats ### ✅ Logical Validity #### Strong reasoning - Problem identification: Clear acknowledgment of widespread design system complexity issues - Solution framing: Logical connection between strategic token reduction and maintenance benefits - Expert credibility: Appeal to authority through Token Studio specialist involvement #### Fallacies - Appeal to authority: Marco's expertise assumed without credentials detailed - Bandwagon effect: "I am [overwhelmed]" suggests universal experience #### Tone of voice - Overall tone: Enthusiastic and technical, creates community through shared challenges ("I am" admission builds relatability) ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on critics or alternatives - Reverse victim/offender: No victim/offender dynamics - Emotional cues and rhetoric: Positive enthusiasm, shared struggle acknowledgment ## 🎯 Conclusion This live session addresses a critical pain point in design system management through expert-led education and hands-on demonstration. The focus on strategic token reduction rather than elimination suggests a mature approach to design system architecture. For practitioners struggling with design system complexity, this represents valuable learning opportunity with immediate practical application. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Strategic token reduction improves design system maintainability > [!quote] Design Systems at Scale. LIVE TOMORROW!!! by [MISSING] via YouTube. Published [MISSING]. Accessed 2024-12-19. > "build complex design systems in Pampot with fewer design tokens, which means less work" Core principle for design system architecture optimization. [view highlight](https://youtu.be/Wq_E577JV6c?t=5#H1) #xref #design-systems ID:rw_20241219_001 ### [H2] Mathematical relationships enable scalable design token systems > [!quote] Design Systems at Scale. LIVE TOMORROW!!! > "how to use math in your tokens and extrapolate things" Advanced technique for systematic design variation generation. [view highlight](https://youtu.be/Wq_E577JV6c?t=27#H2) #xref #design-tokens ID:rw_20241219_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Design token proliferation creates maintenance burden - Applies to complex design systems reaching scale - Referenced at video opening - Links: [[Design-System-Complexity]] [[Token-Architecture]] #### [Z2] Core-semantic token separation improves system organization - Foundation principle for scalable design system architecture - Mentioned in curriculum overview - Links: [[Design-System-Layers]] [[Token-Hierarchy]] --- ### ✏️ Fleeting Queue - [F1] Register for Token Studio live session — https://youtu.be/Wq_E577JV6c #fleeting #learning - [F2] Research Marco from Token Studio background — expert credibility #fleeting #research - [F3] Audit current design system token complexity — preparation for optimization #fleeting #audit --- ## Full Transcript [00:00] Are you overwhelmed by the number of<br>[00:01] tokens in your design system? I am.<br>[00:04] >> In this hands-on live session, we'll<br>[00:06] show you how to build complex design<br>[00:08] systems in Pampot with fewer design<br>[00:11] tokens, which means less work.<br>[00:12] >> We're going to cover fluid topography,<br>[00:14] multibranding, and also how to set up<br>[00:16] your tok structure that it's scalable<br>[00:17] and maintainable, what should be in your<br>[00:19] systems core, and what should be in your<br>[00:20] spantics. And we're going to show you<br>[00:22] how to use math in your tokens and<br>[00:24] extrapolate things. We'll answer your<br>[00:26] nerdy tokens questions live with a<br>[00:29] proper expert, Marco from Token Studio.<br>[00:34] Join us live to nerd out together. <!-- deep-read:sections end --> ## 📺 Video  --- # 📝 Full Notes (Deep-Read Analysis) # 🏷️ Title: Design Systems at Scale. LIVE TOMORROW!!! ## 🧰 Action Inbox - [H1] Register for live session — design systems scaling #design-tokens - [H2] Prepare questions about token structure — live Q&A opportunity #learning - [H3] Review current design system complexity — token audit preparation #audit ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Token Studio](https://tokens.studio/) - [Figma Design Systems](https://www.figma.com/design-systems/) ## 📝 Summary - Live educational session on scaling design systems with fewer design tokens - Focus on reducing complexity while maintaining functionality in Figma/Token Studio - Expert-led hands-on session covering advanced token architecture - Interactive Q&A format with Token Studio expert Marco - Addresses common overwhelm with token proliferation in design systems ## 📖 Main Content This promotional video announces a live educational session focused on solving design system complexity through strategic token reduction. The session promises to address the common problem of design systems becoming unwieldy due to token proliferation. Expert Marco from Token Studio will lead hands-on demonstrations covering fluid typography, multi-brand systems, and mathematical token relationships. The format emphasizes practical implementation with live Q&A for immediate problem-solving. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/Wq_E577JV6c?t=0) — [H1] Problem identification: Token overwhelm - Key idea: Design system complexity creates maintenance burden - Evidence: "Are you overwhelmed by the number of tokens in your design system? I am." #### ⏱️ [00:05](https://youtu.be/Wq_E577JV6c?t=5) — [H2] Solution promise: Fewer tokens, less work - Key idea: Strategic token reduction maintains functionality while reducing complexity - Evidence: "build complex design systems in Pampot with fewer design tokens, which means less work" #### ⏱️ [00:12](https://youtu.be/Wq_E577JV6c?t=12) — [H3] Coverage area: Fluid typography systems - Key idea: Typography scaling can be systematized with mathematical relationships - Evidence: "We're going to cover fluid topography" #### ⏱️ [00:15](https://youtu.be/Wq_E577JV6c?t=15) — [H2] Coverage area: Multi-brand architecture - Key idea: Single system can support multiple brand expressions - Evidence: "multibranding" #### ⏱️ [00:17](https://youtu.be/Wq_E577JV6c?t=17) — [H1] Structural guidance: Scalable token organization - Key idea: Token architecture requires strategic hierarchy planning - Evidence: "how to set up your tok structure that it's scalable and maintainable" #### ⏱️ [00:22](https://youtu.be/Wq_E577JV6c?t=22) — [H2] Architecture principle: Core vs semantic separation - Key idea: Design system layers require clear boundaries and purposes - Evidence: "what should be in your systems core, and what should be in your spantics" #### ⏱️ [00:27](https://youtu.be/Wq_E577JV6c?t=27) — [H3] Advanced technique: Mathematical token relationships - Key idea: Computational approaches can generate consistent design variations - Evidence: "how to use math in your tokens and extrapolate things" #### ⏱️ [00:32](https://youtu.be/Wq_E577JV6c?t=32) — [H2] Expert involvement: Token Studio specialist - Key idea: Industry expert provides authoritative guidance - Evidence: "proper expert, Marco from Token Studio" #### ⏱️ [00:36](https://youtu.be/Wq_E577JV6c?t=36) — [H3] Format benefit: Live interaction and community - Key idea: Real-time problem solving creates immediate value - Evidence: "Join us live to nerd out together" ## 📚 References - [Token Studio](https://tokens.studio/) - [Design Systems Handbook](https://www.designbetter.co/design-systems-handbook) - [Figma Design Systems](https://www.figma.com/design-systems/) ## 🗣️ Paraphrase - Many designers struggle with design systems that have grown too complex due to excessive token proliferation - Strategic token architecture can maintain system flexibility while dramatically reducing maintenance overhead - Expert-led education with hands-on examples provides practical solutions for real-world design system challenges ## 📰 Newsletter 🎨 **Scale Your Design System Without the Complexity** Feeling overwhelmed by design token management? You're not alone. Join Token Studio expert Marco for a live session on building complex design systems with fewer tokens and less maintenance overhead. **What You'll Learn:** - Fluid typography systems that scale mathematically - Multi-brand architecture strategies - Core vs semantic token organization - Mathematical relationships in design tokens This hands-on session promises practical solutions to common design system pain points, with live Q&A for immediate problem-solving. **Resources:** [Token Studio](https://tokens.studio/), [Figma Design Systems](https://www.figma.com/design-systems/), [Design Systems Handbook](https://www.designbetter.co/design-systems-handbook) ## ✅ Action Items #### Design - Token audits: inventory current system complexity, identify redundancies - Architecture planning: core/semantic separation strategies - Mathematical systems: fluid typography implementation - Multi-brand support: scalable brand token architecture - Documentation: token usage guidelines, maintenance procedures ## 🧪 Hypotheses - Strategic token reduction improves design system maintainability without sacrificing functionality - Mathematical relationships in tokens create more consistent and scalable design systems - Core/semantic token separation reduces cognitive load for design system users - Live expert guidance accelerates design system optimization learning ### 📊 Methodology - Comparative analysis: before/after token architecture complexity - User research: designer experience with simplified vs complex token systems - Performance measurement: maintenance time reduction with strategic token organization ### ❓ Questions - What specific mathematical relationships work best for fluid typography systems? - How do you determine optimal boundaries between core and semantic tokens? - What metrics indicate when a design system has too many tokens? ### 🔮 Future Research - Automated token optimization tools and AI-assisted design system architecture - Cross-platform token synchronization in multi-tool design workflows - Design system governance frameworks for large organizations ### 💡 Implications - Practice: Design teams can reduce maintenance overhead through strategic token architecture - Education: Live expert sessions provide immediate value for design system practitioners - Tooling: Token Studio and similar tools enable more sophisticated design system management - Community: Collaborative learning accelerates design system maturation across the industry ### 🧠 Learning Styles Assessment Reading level estimate: 8th Grade #### 👀 Visual learners - Present: Video format with likely screen sharing demonstrations - Improve: Downloadable token architecture diagrams, before/after complexity comparisons #### 🔊 Aural learners - Present: Live presentation with expert narration - Improve: Recorded session for replay, podcast-style summary #### 🗣️ Verbal learners - Present: Expert explanations, technical terminology definitions - Improve: Glossary of design system terms, analogies for complex concepts #### 🧩 Kinesthetic learners - Present: Hands-on demonstrations in design tools - Improve: Step-by-step exercises, downloadable starter files #### 🧠 Logical learners - Present: Structured progression from problem to solution - Improve: Decision trees for token architecture choices, comparison matrices #### 🧑‍🤝‍🧑 Social learners - Present: Live Q&A, community interaction opportunity - Improve: Breakout discussions, peer token system reviews #### 🧘‍♀️ Solitary learners - Present: Individual learning opportunity - Improve: Self-assessment checklist, private practice exercises #### 🌿 Naturalistic learners - Present: Systems thinking approach to design token organization - Improve: Ecosystem analogies, organic growth vs pruning metaphors ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video likely includes verbal explanations - Improve: Complete transcript, detailed alt text for visual demonstrations #### Keyboard navigation - Present: Standard YouTube player controls - Improve: Keyboard shortcuts documentation, accessible demo files #### Contrast and readability - Present: Standard video player interface - Improve: High-contrast design system examples, readable token naming conventions #### Text resizing and reflow - Present: Video content adapts to player size - Improve: Supplementary text materials that resize properly #### Media and captions - Present: Video format - Improve: Auto-generated captions, downloadable transcript #### Forms and interactions - Present: Basic video player interactions - Improve: Accessible registration forms, inclusive Q&A submission ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language presentation - Improve: Multiple language options, global design system examples #### Inclusive language - Present: Technical but accessible language use - Improve: Defined jargon, plain-language alternatives #### Neurodiversity support - Present: Structured presentation format - Improve: Content outline, predictable session flow #### Representation - Present: Expert knowledge sharing - Improve: Diverse speaker lineup, varied company examples #### Psychological safety - Present: "Nerd out together" creates welcoming tone - Improve: Clear participation guidelines, multiple question formats ### ✅ Logical Validity #### Strong reasoning - Problem identification: Clear acknowledgment of widespread design system complexity issues - Solution framing: Logical connection between strategic token reduction and maintenance benefits - Expert credibility: Appeal to authority through Token Studio specialist involvement #### Fallacies - Appeal to authority: Marco's expertise assumed without credentials detailed - Bandwagon effect: "I am [overwhelmed]" suggests universal experience #### Tone of voice - Overall tone: Enthusiastic and technical, creates community through shared challenges ("I am" admission builds relatability) ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on critics or alternatives - Reverse victim/offender: No victim/offender dynamics - Emotional cues and rhetoric: Positive enthusiasm, shared struggle acknowledgment ## 🎯 Conclusion This live session addresses a critical pain point in design system management through expert-led education and hands-on demonstration. The focus on strategic token reduction rather than elimination suggests a mature approach to design system architecture. For practitioners struggling with design system complexity, this represents valuable learning opportunity with immediate practical application. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Strategic token reduction improves design system maintainability > [!quote] Design Systems at Scale. LIVE TOMORROW!!! by [MISSING] via YouTube. Published [MISSING]. Accessed 2024-12-19. > "build complex design systems in Pampot with fewer design tokens, which means less work" Core principle for design system architecture optimization. [view highlight](https://youtu.be/Wq_E577JV6c?t=5#H1) #xref #design-systems ID:rw_20241219_001 ### [H2] Mathematical relationships enable scalable design token systems > [!quote] Design Systems at Scale. LIVE TOMORROW!!! > "how to use math in your tokens and extrapolate things" Advanced technique for systematic design variation generation. [view highlight](https://youtu.be/Wq_E577JV6c?t=27#H2) #xref #design-tokens ID:rw_20241219_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Design token proliferation creates maintenance burden - Applies to complex design systems reaching scale - Referenced at video opening - Links: [[Design-System-Complexity]] [[Token-Architecture]] #### [Z2] Core-semantic token separation improves system organization - Foundation principle for scalable design system architecture - Mentioned in curriculum overview - Links: [[Design-System-Layers]] [[Token-Hierarchy]] --- ### ✏️ Fleeting Queue - [F1] Register for Token Studio live session — https://youtu.be/Wq_E577JV6c #fleeting #learning - [F2] Research Marco from Token Studio background — expert credibility #fleeting #research - [F3] Audit current design system token complexity — preparation for optimization #fleeting #audit --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=Wq_E577JV6c)* **[00:00]** Are you overwhelmed by the number of tokens in your design system? I am. >> In this hands-on live session, we'll show you how to build complex design systems in Pampot with fewer design tokens, which means less work. >> We're going to cover fluid topography, multibranding, and also how to set up your tok structure that it's scalable and maintainable, what should be in your systems core, and what should be in your spantics. And we're going to show you how to use math in your tokens and extrapolate things. We'll answer your nerdy tokens questions live with a proper expert, Marco from Token Studio. **[00:34]** Join us live to nerd out together.