<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abigaél &amp; Anouk on Medium]]></title>
        <description><![CDATA[Stories by Abigaél &amp; Anouk on Medium]]></description>
        <link>https://medium.com/@abigael-and-anouk?source=rss-fb646a49efb1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YOHP4JcSnVLfFDMYFjveJA.png</url>
            <title>Stories by Abigaél &amp;amp; Anouk on Medium</title>
            <link>https://medium.com/@abigael-and-anouk?source=rss-fb646a49efb1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:01:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abigael-and-anouk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[One System, 10+ Brands: Part 2 — How we shaped our scalable Multibrand Design System]]></title>
            <link>https://www.designsystemscollective.com/one-system-10-brands-part-2-how-we-shaped-our-scalable-multibrand-design-system-55af0d5d3e9d?source=rss-fb646a49efb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/55af0d5d3e9d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-system-tips]]></category>
            <dc:creator><![CDATA[Abigaél & Anouk]]></dc:creator>
            <pubDate>Wed, 12 Nov 2025 08:03:34 GMT</pubDate>
            <atom:updated>2025-11-12T08:56:41.153Z</atom:updated>
            <content:encoded><![CDATA[<h3>One System, 10+ Brands: Part 2 — How we shaped our scalable Multibrand Design System</h3><h3><strong>A short recap: our case</strong></h3><p>In our <a href="https://medium.com/design-systems-collective/one-system-10-brands-why-we-chose-to-build-a-multibrand-design-system-in-figma-1fe688274506"><strong>previous article</strong></a>, we explained what a design system is and why it’s such a game-changer, especially when managing multiple brands. In this article, we’re zooming in on our own setup at PXR. An online publisher with a custom-built CMS, used for the content platforms of 10+ brands, with a team behind it that is determined to do as much as possible in-house.</p><p>This combination of a proprietary CMS, multiple editorial teams, and a single design system that needs to serve them all makes our case quite niche. In this article, we’ll take you behind the scenes. We’ll explain how we work, the tools and structure we rely on, the challenges we faced, and what made our multibrand setup so complex and yet so rewarding to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGyBmOhe1fBDACEpJzTqmQ.png" /></figure><h3>1. How we work at PXR</h3><p>Our tech department at PXR contains developers, product owners, and designers who operate as a single team. Together, we maintain our different products with shared goals. We do so by working in an agile environment with sprints, retrospectives, and refinements. This aligns our priorities across disciplines and helps us to keep improving our process.</p><p>Because everything is built in-house, <strong>collaboration is key</strong>. Our editorial teams work daily in our <em>Nēxt</em> CMS to create and publish content. Whereas we, as the product team, focus on making that experience as smooth and scalable as possible, for both the editors behind the scenes and the readers on the front end.</p><p>Everything we design happens in <strong>Figma</strong>, which serves as our single source of truth. All components, variables, and brand styles are defined there. Developers export these variables directly into code. Resulting in that whenever we update a color, spacing, or typography style in Figma, it’s automatically reflected across the live platforms.</p><p>This setup keeps our <strong>design system alive</strong>: not as a static library, but as a dynamic part of our production workflow, continuously evolving alongside the products it supports.</p><h3><strong>3. Figma Modes vs. Tokens Studio</strong></h3><p>During our research, we found that many design system case studies used <strong>Tokens Studio</strong> to manage variables. At first, it seemed like a great fit for our needs. It offered easy options to create light and dark theme variables, and more importantly, it supported multiple brands that you could easily switch between. However, we quickly ran into a few practical problems.</p><p>Our main challenges were that the tool was paid, had a steep learning curve, and required time we didn’t have to set up initial design variables. It also added an extra layer between design and development, causing issues when exporting and importing code. While testing a basic multi-brand setup, we found it difficult to see which brand you were working with, unlike in Figma, where you can easily switch appearances and see this reflected in both your layers and your sidebar. Finally, since Token Studio is simply a Figma plugin, it would mean building on something external rather than keeping everything within our main design tool.</p><p>As a wise strategist once said:<br>“Bouw nooit je huis op gehuurde grond” <br>(<em>Roughly translated: Never build your property on land that you’re just renting.</em>). <br>- <a href="https://medium.com/u/2d496530b34d">Matt Tielman</a></p><p>We decided to stay close to the source and work directly with native Figma variables and modes. The standard within our existing workflow, and a structure guaranteed to stay supported and scalable. Although it required more manual setup at first, it gave us complete control and ownership over the system we were building.</p><h3>4. A Lesson on Libraries</h3><p>We started with <strong>one single Figma file</strong> containing everything: all brands, components, and modes. At first, this setup worked well since our focus was solely on <strong>web components</strong>, the parts of the platform visible to end users.</p><p>However, once we shared the setup with developers, our first challenge arose. Since both the components for the back end (CMS) and for the front end (WEB) come from the same codebase, our development suggested combining everything into one library. We understood their perspective at the time, but for us, these were completely different products with different users and different contexts. Our CMS is used by the editorial teams, while the WEB elements serve readers visiting our platforms. Two areas with very different UX and UI patterns. Combining all components and their specific variables into one system felt unsustainable: the file would become huge, very slow, would be difficult to maintain, and confusing to work with, especially if our team were to grow. We had to find another way.</p><p><strong>And so, we made the big decision to restructure our design system into three separate libraries that all build on top of one another.</strong></p><ul><li><strong>Base Library</strong> → Our <em>functional building blocks</em> without styling, based on our shared codebase.</li><li><strong>Web Library</strong> → The styled versions of our functional building blocks for all brands, along with web-specific components used only on the website.</li><li><strong>CMS Library</strong> → The styled versions of our functional building blocks for our admin environment, along with CMS-specific components used only in the admin.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJvAc2meCAIBxQ1pu8H5Pg.jpeg" /></figure><p>The Web and CMS libraries both utilize components from the Base Library. In other words, <strong>Base Components</strong> form the shared foundation across all our products. Some components are unique to Web or CMS, but most come from this common core, for instance: inputs, buttons, and larger (interactive) components that exist in both environments.</p><p>The tough part of all this is that because we started with the Web Library and came to the conclusion that we needed a Base Library, we had to go back and build that Base Library later, resulting in us having to relink dozens of existing components and reassigning variables to fit the new structure; a lot of manual work we could have avoided.</p><p>💡Key lesson learned:<br> <strong>Mapping out</strong> <strong>a well-structured foundation should be step 1.</strong></p><h3>5. Collaborating With Development</h3><p>From the start, we worked closely with a front-end developer who had prior experience building design systems. Together, we iterated on the setup, naming conventions, and file structure <em>(sometimes for hours on end)</em> to find a balance that worked for both design and development.</p><p>He built the integration that connects our Figma variables directly to the codebase. With just a few clicks, developers can now pull the latest updates from Figma, marking the true starting point for implementing our design system on the development side.</p><p>However, before that connection can fully work, the tech stack needs some maintenance and partial rebuilding. Each component has to be linked to our system one by one, just as we did when recreating and connecting them to the new variables in Figma. It’s a big task, but absolutely worth it. Once everything is reconnected, the code becomes simpler, the stack cleaner and more organized, and updates will sync automatically. This will save the development team a significant amount of time in the long run.</p><p>💡During this collaboration, we also uncovered another important insight:<strong> language matters</strong>.</p><p>Early on, we realized that designers and developers often used different terminology for the same things, which led to confusion and slowed us down. Together, we refined <em>and re-refined</em> our naming conventions to make them consistent, predictable, and easy to search. We let development take the lead on the logic behind names, because their workflow depends on reading and navigating the code efficiently. As designers, we think visually; for us, renaming or reorganizing a layer is quick, but for developers, it can make or break their workflow.</p><h3><strong>6. Consistency Across Libraries and Modes</strong></h3><p>Consistent naming matters not only between design and code but also within Figma itself. Since our system spans multiple files and variable collections, we apply the same naming conventions to shared building blocks and the variables used within each component.</p><p>Inside the Web Library, we manage multiple <strong>modes in folders/collections</strong>:</p><ol><li>Each <strong>Brand</strong> has its own folder with brand-specific tokens.</li><li>Then come <strong>Brand Modes</strong>, grouped under the name “Alias”. <br>Within Alias, we set tokens that define styles for each brand within a single component, utilizing the definitions set in the Brand folders.</li><li>Next, we have a <strong>Color Mode</strong> folder, in which we define the light and dark modes. For this, we utilize the definitions set in Alias for light mode and give them an alternative for dark mode.</li><li>And then there’s also a <strong>Viewport</strong> folder, in which we store sizing settings to be able to design responsive components. This ranges from differences in font size between small- and large displays, to grids and paddings.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qx5D8A1Nyc-fmRUeWaDM3g.jpeg" /></figure><p>All this wouldn’t work properly for development if the names of elements didn’t line up. It would result in enormous lines of code and become massively confusing. So, the variables in the folder ‘Color Mode’ are identical to the (color-related) ones in ‘Alias’, and so on.</p><p>In the components that we build, we can assign settings (modes) from each of these folders (collections). For example, when we work with a button component, we reference both a <strong>brand</strong> and a <strong>color mode</strong>. The button is styled for Brand X, and knows whether to act like it’s in light- or dark mode as defined per Color Mode/Light (or Dark). Switching this button to another brand or color mode has never been easier.</p><p>This layered approach allows us to scale effortlessly. When a new brand joins the PXR ecosystem, all we need to do is determine the brand variables and add them to the design system; the rest already knows how to behave.</p><h3>Wrapping up</h3><p>Building a multibrand design system isn’t just about structure; it’s about collaboration, communication, and iteration. Here are a few of the lessons that made the biggest difference for us, which we hope could be helpful for others.</p><ul><li><strong>Start with your shared foundation:</strong> Define what’s common before what’s unique.</li><li><strong>Involve development early:</strong> It’ll save you so much time later.</li><li><strong>Agree on naming conventions.</strong> Clarity in structure = speed in execution.</li><li><strong>Make sure you can rely on your tools.</strong> Remember Matthijs Tielman’s words: Be careful with the tools you choose when building <em>what could be</em> your life’s work.</li><li><strong>Remain open for feedback and willing to iterate.</strong> Expect to revisit and refine (very) often. And remember that together you’re making it better.</li></ul><p>Each step we took made the system better, more consistent and more scalable. And although it’s still evolving, we’ve now built a foundation that will support every future product, brand, and platform at PXR.</p><p>— — —</p><p>We hope sharing our insights and lessons learned will prove to be useful. Feel free to DM us your thoughts or questions about Design Systems. We’re happy to discuss, answer questions, and learn more.</p><p>In our next article, we’ll zoom in on naming conventions and consistency regarding a design system. As we mentioned before, this is super important, and in many cases, it takes a lot of effort to do this correctly.</p><p>👉 Follow us to get notified when we post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55af0d5d3e9d" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/one-system-10-brands-part-2-how-we-shaped-our-scalable-multibrand-design-system-55af0d5d3e9d">One System, 10+ Brands: Part 2 — How we shaped our scalable Multibrand Design System</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One System, 10+ Brands: Why We Chose to Build a Multibrand Design System in Figma]]></title>
            <link>https://www.designsystemscollective.com/one-system-10-brands-why-we-chose-to-build-a-multibrand-design-system-in-figma-1fe688274506?source=rss-fb646a49efb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fe688274506</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-system-tips]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Abigaél & Anouk]]></dc:creator>
            <pubDate>Wed, 08 Oct 2025 11:23:15 GMT</pubDate>
            <atom:updated>2025-10-16T08:02:54.685Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If you’re not exactly sure what a Design System is, don’t click away just yet. We’ll explain what it is (and why it matters) in clear, simple language.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0tI1Z0WAZXB025qKRKjbxg.png" /></figure><h3>What is a Design System, really?</h3><p>Design systems have become an omnipresent feature in UX/UI design. Various examples can be found online with different approaches and methods. Design systems are very similar to Lego. When buying a box, it’s not just a random collection of bricks. The set has been carefully put together to build something specific: a spaceship, a castle, or even an entire city.</p><p>Each piece has been carefully crafted to have its own purpose: its shape, color, how it fits with the rest. There’s a system behind it. A well-functioning design system works the same way. It’s a carefully created collection of design blocks that together form a whole. Instead of reinventing the wheel every time, you can click together existing parts in an efficient way. Mostly ideal when you’re creating digital products for a brand.</p><p>While the idea of setting up a design system can be exciting, in reality it can become very complex. Especially in our case, when the system has to feature over 10 brands. We’re building a <strong>multibrand</strong> design system for publisher PXR, housing all their online titles, the admin environment, and soon the native apps.</p><h3>Why a (Multibrand) Design System matters</h3><p>When looking at large (tech) organisations, like Uber and Google, most of them have invested in a design system. However for smaller, growing companies this is usually not the case. They either postpone or never start, due to the time and resources it demands to create one, and from experience we can tell: pulling scattered components into one central system becomes increasingly complex and even more time-consuming.</p><p>Large companies embrace design systems because they help them <strong>scale consistently across multiple products and teams</strong>. They help maintain <strong>ownership of the brand experience</strong>, while still leaving room for each sub-brand to differentiate. This balance of efficiency, governance and flexibility is what makes (multibrand) design systems so powerful, and at the same time so challenging.</p><p>Throughout our research on building a multibrand design system, we found that most (public) examples are based on a <em>shared product foundation</em>. Take Coca-Cola, Light, Zero and Cherry each have their own identity within a single design system, making this a multibrand design system as well — but they all revolve around the same product. At PXR, it’s a different story.</p><p>Our brands differ far more in content and purpose and therefore also in users and stakeholders. We have a parenting platform, sports- and lifestyle communities, gadget- and science platforms and automotive portal. This means that we couldn’t fall back on existing examples like the one given above. We had to figure out many things ourselves: how to create <strong>one system that powers completely different brands, while still leaving room for each brand’s own identity</strong>. That’s what makes our case so complex, and unique.</p><h3>A quick look at how this project came to life</h3><p>Anouk was already working as a designer at PXR when the first new brands had to be onboarded to CMS <em>Nēxt</em>. She quickly ran into a familiar problem: <strong>too much repetitive manual work</strong>.</p><p>Even though every content platform is different, you always encounter recurring components: buttons, lists, forms, navigation, and so on. Yet we had to redesign and rebuild them every single time. That took a lot of effort and therefore left little room for structural improvement.</p><p>By bringing in Abigaél, her freelance partner and now also colleague. They created the space to tackle this problem systematically. Together, they started setting up a design system. At first small, but within a few months used by our colleagues in Tech, and well received by the rest of the organization.</p><p>The true impact of the new design system became especially clear with PXR’s latest migration: moving Voetbal International onto the Nēxt CMS. This migration took a lot of time and effort, and with the next titles already lined up to be onboarded, time and capacity are of the essence. With the system in place, we can now easily onboard any new brand/platform onto our CMS. Where we used to rebuild an entire framework from scratch, we now click together existing building blocks to form the basics. By defining the brand-specific variables, the foundation is ready in no time.</p><p><strong>With results like:</strong></p><ul><li><strong>Creating space for innovation:</strong> more time for the truly fun work.</li><li><strong>Raising consistency and quality:</strong> less mistakes and ‘quick fixes’, better UX and accessibility.</li><li><strong>Accelerating processes:</strong> onboarding new brands better and faster.</li><li><strong>Focusing on details:</strong> where usability and distinction really come to life.</li><li><strong>Bridging the gap between design and tech</strong>: one source of truth for everyone.</li></ul><p>In short: less time spent on basics, more room to look ahead.</p><h3>Why this is relevant for your organization too</h3><p>Our setup at PXR may be large-scale, but the principle is universal. Whether you work at an agency, publisher, or in a product team building digital platforms, if there is no design system in place, you’ve likely run into relatable challenges.</p><p>As we’ve said before: a design system doesn’t just make your work faster and more consistent, it frees up room for real innovation and leaves less space for mistakes. Even though we are in the middle of implementing our design system, with still plenty left to learn, we can already tell how much easier and more fun our work has become.</p><p>So, do your design team a favor, carve out space to set one up.</p><p>──────────────────</p><p>This article is the start of a series in which we’ll share what we learned along the way: from the challenges of a multibrand setup, to collaboration between design and development, to the mistakes we’ve already made so you don’t have to.</p><p>👉 Follow us to read about our next steps soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fe688274506" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/one-system-10-brands-why-we-chose-to-build-a-multibrand-design-system-in-figma-1fe688274506">One System, 10+ Brands: Why We Chose to Build a Multibrand Design System in Figma</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>