{"id":24512,"date":"2026-04-06T07:58:52","date_gmt":"2026-04-06T13:28:52","guid":{"rendered":"https:\/\/lollypop.terralogic.com\/?p=24512"},"modified":"2026-04-07T03:56:29","modified_gmt":"2026-04-07T09:26:29","slug":"design-tokens-the-foundation-of-scalable-design-systems","status":"publish","type":"post","link":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/","title":{"rendered":"Design Tokens: The Foundation of Scalable Design Systems"},"content":{"rendered":"<article class=\"blog-post\" aria-labelledby=\"post-heading\">\n<section class=\"blog-intro\" aria-label=\"Introduction\">In simple terms, design tokens are just nicknames for design elements!Instead of using raw, \u201chard-coded\u201d values that are difficult to remember and even harder to change, we use semantic names.\n<ul>\n<li><strong>Instead of:<\/strong> <code>#FF5733<\/code> \u2192 <strong>You write:<\/strong> <code>color-background-primary<\/code><\/li>\n<li><strong>Instead of:<\/strong> <code>16px<\/code> \u2192 <strong>You write:<\/strong> <code>spacing-medium<\/code><\/li>\n<\/ul>\n<p>But this leads to the <strong>big questions: \u201cWhy do we need to rename these values? What actual value does this bring to a complex product design project?\u201d<\/strong><\/p>\n<p>Let\u2019s dive deep into the world of <a href=\"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/\" target=\"_blank\" rel=\"noopener noreferrer\">design tokens<\/a> through this blog!<\/p>\n<\/section>\n<section aria-labelledby=\"key-takeaways\">\n<h2 id=\"key-takeaways\"><strong>Key Takeaways<\/strong><\/h2>\n<ul>\n<li><strong>Design tokens<\/strong> replace hard-coded values like <code>#FF5733<\/code> or <code>16px<\/code> with meaningful names such as <code>color-background-primary<\/code> and <code>spacing-medium<\/code>.<\/li>\n<li>They create a single source of truth, so updates only need to be made once across all platforms.<\/li>\n<li>The 3 main layers are:\n<ul>\n<li>Global tokens = raw values<\/li>\n<li>Alias tokens = purpose-based names<\/li>\n<li>Component tokens = UI-specific styles<\/li>\n<\/ul>\n<\/li>\n<li>This structure improves consistency, speeds up updates, and gives teams more flexibility.<\/li>\n<li>Design tokens help designers and developers stay aligned and scale design systems more efficiently.<\/li>\n<\/ul>\n<\/section>\n<section aria-labelledby=\"what-are-design-tokens\">\n<h2 id=\"what-are-design-tokens\"><strong>What Are Design Tokens?<\/strong><\/h2>\n<p>Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. Instead of hard-coding values like <code>#E8DEF8<\/code> or <code>16px<\/code>, these values are stored as named variables that can be reused across the entire product ecosystem.<\/p>\n<p>Think of it like saving a contact in your phone. You do not save your mother\u2019s number as <code>123-456-7890<\/code>. You save it as Mom. If her number changes, you update it once in your contact list, and everyone who calls Mom reaches the new number automatically.<\/p>\n<p>Design tokens work exactly like that. They assign a specific name to a specific value so that when the brand evolves, you only update the \u201csource of truth\u201d in one place.<\/p>\n<\/section>\n<section aria-labelledby=\"why-design-tokens-born\">\n<h2 id=\"why-design-tokens-born\"><strong>Why Were Design Tokens Born?<\/strong><\/h2>\n<p>In the early days of digital design, teams were small and products were simple. If a designer wanted to change a button color, they just told the developer the new Hex code. It was manual, but it worked!<\/p>\n<p>But then products scaled. Companies started building websites, iOS apps, Android apps, even smartwatch interfaces \u2014 all at once. Suddenly, that one color existed in 4 different places. If the brand decided to switch from <strong>blue<\/strong> \u2192 <strong>purple<\/strong>, someone had to hunt down every instance of that blue across platforms and update it manually.<\/p>\n<p>That\u2019s where things got messy!<\/p>\n<p>Design tokens were born to solve this chaos. They turn design decisions into shared data that both designers and developers can use \u2014 so no matter where the product lives, it looks and feels the same!<\/p>\n<p>And it\u2019s not just about color. Design tokens can also be applied to:<\/p>\n<figure><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/d076e39a-artwork-1.webp\" alt=\"Categories of design tokens including color, typography, spacing, sizing, border radius, shadows, motion, and z-index values\" width=\"1440\" height=\"615\"><\/figure>\n<p><strong>Explore further: <a href=\"https:\/\/lollypop.design\/blog\/2024\/july\/what-is-design-system\/\" target=\"_blank\" rel=\"noopener noreferrer\">What is a Design System?<\/a><\/strong><\/p>\n<\/section>\n<section aria-labelledby=\"design-token-types\">\n<h2 id=\"design-token-types\"><strong>Design Token Types: The 3 Layers You Need to Know<\/strong><\/h2>\n<figure><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/9b680199-artwork-2.webp\" alt=\"Diagram showing the three layers of design tokens: Global Tokens at the base, Alias Tokens in the middle, and Component Tokens at the top\" width=\"1440\" height=\"615\"><\/figure>\n<p>Now that you understand what design tokens are and why they matter, the next question is: Are all tokens the same?<\/p>\n<p>The answer is no. Design tokens come in three main types. Think of them like layers in a cake. Each layer has a different purpose, and they work together to create the final result.<\/p>\n<p>Let\u2019s break down each type in simple terms.<\/p>\n<article aria-labelledby=\"layer-1-global\">\n<h3 id=\"layer-1-global\"><strong>Layer 1. Global Tokens<\/strong><\/h3>\n<figure><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/7375c2f6-artwork-3.webp\" alt=\"Global tokens diagram showing raw primitive values like color hex codes mapped to simple names such as blue-500 with no semantic meaning attached\" width=\"1440\" height=\"1110\"><\/figure>\n<p>Global tokens are the \u201cprimitive\u201d values of your design language. They are simply names for raw values like specific colors or pixel measurements.<\/p>\n<p><strong>For example:<\/strong> <code>#0066FF<\/code> \u2192 <code>blue-500<\/code><\/p>\n<p>At this level, there\u2019s no meaning attached. It tells you what the value is, but not how to use it. Is it for buttons? Text? Background? You don\u2019t know yet.<\/p>\n<p>That\u2019s why global tokens are usually not used directly. They act as the source for other tokens.<\/p>\n<\/article>\n<article aria-labelledby=\"layer-2-alias\">\n<h3 id=\"layer-2-alias\"><strong>Layer 2. Alias Tokens<\/strong><\/h3>\n<figure><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/481c42aa-artwork-4.webp\" alt=\"Alias tokens diagram showing how raw global token values are mapped to purpose-based names like color-background-primary and color-text-inverse\" width=\"1440\" height=\"570\"><\/figure>\n<p>Alias tokens add meaning to global tokens. They map raw values to a specific purpose in the design system.<\/p>\n<p><strong>For example:<\/strong><\/p>\n<ul>\n<li><code>color-background-primary<\/code> \u2192 <code>purple-400<\/code><\/li>\n<li><code>color-text-inverse<\/code> \u2192 <code>purple-400<\/code><\/li>\n<\/ul>\n<p>Instead of referencing a color directly, you reference its role. This helps designers and developers understand how and where a token should be used.<\/p>\n<\/article>\n<article aria-labelledby=\"layer-3-component\">\n<h3 id=\"layer-3-component\"><strong>Layer 3. Component Tokens<\/strong><\/h3>\n<figure><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/b5697406-artwork-5.webp\" alt=\"Component tokens diagram showing UI-specific token names like button-background-primary, button-background-primary-hover, and checkbox-background-checked applied to real interface elements\" width=\"1440\" height=\"455\"><\/figure>\n<p>Component tokens are the most specific layer. They apply tokens directly to UI components and define how those components look in different states.<\/p>\n<p><strong>For example:<\/strong><\/p>\n<ul>\n<li><code>button-background-primary<\/code><\/li>\n<li><code>button-background-primary-hover<\/code><\/li>\n<li><code>tab-background-selected<\/code><\/li>\n<li><code>checkbox-background-checked<\/code><\/li>\n<\/ul>\n<p>These tokens connect the design system to real interface elements. They usually reference alias tokens to stay consistent with the overall system.<\/p>\n<\/article>\n<article aria-labelledby=\"why-three-layers\">\n<h3 id=\"why-three-layers\"><strong>Why Three Layers?<\/strong><\/h3>\n<p>You might wonder, why not just use one type? Why make it complicated with 3 layers?<\/p>\n<p>The answer is flexibility. When you separate tokens into these 3 types, you gain control at different levels.<\/p>\n<ul>\n<li><strong>If you need to change a raw value<\/strong>, like updating your brand blue, you change the global token. Every alias and component that uses it updates automatically.<\/li>\n<li><strong>If you need to change how a value is used<\/strong>, like making all primary buttons green instead of blue, you change the alias token. The global token stays the same, but the meaning shifts.<\/li>\n<li><strong>If you need to change a single component<\/strong> without affecting others, you use component-specific tokens. This gives you surgical control when needed.<\/li>\n<\/ul>\n<\/article>\n<\/section>\n<section aria-labelledby=\"final-thoughts\">\n<h2 id=\"final-thoughts\"><strong>Final Thoughts<\/strong><\/h2>\n<p>Design tokens act as the <strong>single source of truth<\/strong> that connects design and development. They help teams move faster, maintain consistency across platforms, and scale products without the burden of constant manual updates.<\/p>\n<p>At <a href=\"https:\/\/lollypop.design\/ui-ux-design-agency-in-usa\/\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>Lollypop Design Studio<\/strong><\/a>, building a comprehensive UX design system is always a core part of our digital product projects. This approach ensures that every design component can be reused efficiently and applied consistently across the product.<\/p>\n<p>If you\u2019re looking for a reliable partner to design your product or build a scalable design system, we\u2019re here to help. Get in touch to <a href=\"https:\/\/lollypop.design\/project-enquiry\/\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>schedule a free consultation<\/strong><\/a>!<\/p>\n<\/section>\n<section aria-labelledby=\"faq\">\n<h2 id=\"faq\"><strong>Frequently Asked Questions (FAQs)<\/strong><\/h2>\n<article aria-labelledby=\"faq-1\">\n<h3 id=\"faq-1\"><strong>1. What are tools for managing design tokens?<\/strong><\/h3>\n<p>Popular tools for managing design tokens include design platforms like Figma Tokens (Tokens Studio), Penpot, and Specify, as well as development tools such as Style Dictionary for transforming tokens into platform-specific formats. These tools allow teams to maintain a centralized token library, export tokens for different platforms (web, iOS, Android), and ensure designers and developers are working with the same design definitions.<\/p>\n<\/article>\n<article aria-labelledby=\"faq-2\">\n<h3 id=\"faq-2\"><strong>2. How are design tokens used in CSS?<\/strong><\/h3>\n<p>In CSS, design tokens are commonly implemented as CSS custom properties (variables). Token values \u2014 such as colors, spacing, or typography \u2014 are defined once in a global stylesheet and referenced throughout the codebase. For example, a token like <code>--color-background-primary<\/code> can be defined in <code>:root<\/code>, and components can reference it using <code>var(--color-background-primary)<\/code>. This approach makes it easy to update styles across the entire interface by modifying the token value in a single place.<\/p>\n<\/article>\n<article aria-labelledby=\"faq-3\">\n<h3 id=\"faq-3\"><strong>3. What is the difference between tokens and variables?<\/strong><\/h3>\n<p>Design tokens and variables are closely related but serve different roles. A design token represents a design decision \u2014 such as a color, spacing value, or typography rule \u2014 defined in a structured system that can be shared across tools and platforms. A variable, on the other hand, is a technical implementation used in code to store and reference a value. In practice, design tokens often become variables when they are exported to development environments like CSS, JavaScript, or native mobile frameworks.<\/p>\n<\/article>\n<article aria-labelledby=\"faq-4\">\n<h3 id=\"faq-4\"><strong>4. How do design tokens improve consistency across a design system?<\/strong><\/h3>\n<p>Design tokens improve consistency by creating a centralized source of truth for visual design decisions. Instead of designers and developers manually choosing values for colors, typography, or spacing, they reference predefined tokens that represent approved styles within the design system. Because these tokens are reused across components, layouts, and platforms, they help ensure that the interface maintains a consistent visual language and make it easier to apply updates or design changes across the entire product.<\/p>\n<\/article>\n<\/section>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>In simple terms, design tokens are just nicknames for design elements!Instead of using raw, \u201chard-coded\u201d values that are difficult to remember and even harder to change, we use semantic names. Instead of: #FF5733 \u2192 You write: color-background-primary Instead of: 16px \u2192 You write: spacing-medium But this leads to the big questions: \u201cWhy do we need [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":24513,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[16,5],"tags":[],"blogs_category":[26,27,25],"class_list":["post-24512","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-april","category-blogs","blogs_category-banner-blog","blogs_category-blogs","blogs_category-top-blogs"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Design Tokens: The Foundation of Scalable Design Systems - Lollypop<\/title>\n<meta name=\"description\" content=\"Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. These values are stored as named variables that can be reused across the entire product ecosystem. Learn More!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Design Tokens: The Foundation of Scalable Design Systems - Lollypop\" \/>\n<meta property=\"og:description\" content=\"Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. These values are stored as named variables that can be reused across the entire product ecosystem. Learn More!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/\" \/>\n<meta property=\"og:site_name\" content=\"Lollypop\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-06T13:28:52+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-07T09:26:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1461\" \/>\n\t<meta property=\"og:image:height\" content=\"942\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Charishma Singh\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Charishma Singh\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Design Tokens: The Foundation of Scalable Design Systems - Lollypop","description":"Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. These values are stored as named variables that can be reused across the entire product ecosystem. Learn More!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/","og_locale":"en_US","og_type":"article","og_title":"Design Tokens: The Foundation of Scalable Design Systems - Lollypop","og_description":"Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. These values are stored as named variables that can be reused across the entire product ecosystem. Learn More!","og_url":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/","og_site_name":"Lollypop","article_published_time":"2026-04-06T13:28:52+00:00","article_modified_time":"2026-04-07T09:26:29+00:00","og_image":[{"width":1461,"height":942,"url":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp","type":"image\/webp"}],"author":"Charishma Singh","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Charishma Singh","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#article","isPartOf":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/"},"author":{"name":"Charishma Singh","@id":"https:\/\/lollypop.design\/#\/schema\/person\/1ad57f626111d7fa07a44fc397ea62c7"},"headline":"Design Tokens: The Foundation of Scalable Design Systems","datePublished":"2026-04-06T13:28:52+00:00","dateModified":"2026-04-07T09:26:29+00:00","mainEntityOfPage":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/"},"wordCount":1231,"publisher":{"@id":"https:\/\/lollypop.design\/#organization"},"image":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#primaryimage"},"thumbnailUrl":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp","articleSection":["april","blogs"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/","url":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/","name":"Design Tokens: The Foundation of Scalable Design Systems - Lollypop","isPartOf":{"@id":"https:\/\/lollypop.design\/#website"},"primaryImageOfPage":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#primaryimage"},"image":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#primaryimage"},"thumbnailUrl":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp","datePublished":"2026-04-06T13:28:52+00:00","dateModified":"2026-04-07T09:26:29+00:00","description":"Design tokens are a structured way to store design decisions such as colors, typography, spacing, and other design elements. These values are stored as named variables that can be reused across the entire product ecosystem. Learn More!","breadcrumb":{"@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#primaryimage","url":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp","contentUrl":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/00dde9e6-banner-3.webp","width":1461,"height":942},{"@type":"BreadcrumbList","@id":"https:\/\/lollypop.design\/blog\/2026\/april\/design-tokens-the-foundation-of-scalable-design-systems\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/lollypop.design\/"},{"@type":"ListItem","position":2,"name":"Design Tokens: The Foundation of Scalable Design Systems"}]},{"@type":"WebSite","@id":"https:\/\/lollypop.design\/#website","url":"https:\/\/lollypop.design\/","name":"Lollypop","description":"Designing Human-Centered Digital Experiences.","publisher":{"@id":"https:\/\/lollypop.design\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/lollypop.design\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/lollypop.design\/#organization","name":"lollypop","url":"https:\/\/lollypop.design\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/lollypop.design\/#\/schema\/logo\/image\/","url":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/2022\/01\/lollypop-new-logo-2.jpg","contentUrl":"https:\/\/storage.googleapis.com\/websiteasset\/uploads\/2022\/01\/lollypop-new-logo-2.jpg","width":350,"height":226,"caption":"lollypop"},"image":{"@id":"https:\/\/lollypop.design\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/lollypop.design\/#\/schema\/person\/1ad57f626111d7fa07a44fc397ea62c7","name":"Charishma Singh","sameAs":["https:\/\/lollypop.design\/"],"url":"https:\/\/lollypop.design\/author\/charishma\/"}]}},"_links":{"self":[{"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/posts\/24512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/comments?post=24512"}],"version-history":[{"count":0,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/posts\/24512\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/media\/24513"}],"wp:attachment":[{"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/media?parent=24512"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/categories?post=24512"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/tags?post=24512"},{"taxonomy":"blogs_category","embeddable":true,"href":"https:\/\/lollypop.design\/wp-json\/wp\/v2\/blogs_category?post=24512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}