1:"$Sreact.fragment"
2:I[85437,["/_next/static/chunks/3ook47v9b5o5y.js","/_next/static/chunks/14mrh2-p_w84d.js"],"Image"]
3:I[22016,["/_next/static/chunks/3ook47v9b5o5y.js","/_next/static/chunks/14mrh2-p_w84d.js"],""]
4:I[97367,["/_next/static/chunks/3ook47v9b5o5y.js","/_next/static/chunks/14mrh2-p_w84d.js"],"OutletBoundary"]
5:"$Sreact.suspense"
0:{"rsc":["$","$1","c",{"children":[["$","div",null,{"className":"min-h-screen bg-gray-50","children":[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"Article\",\"headline\":\"Design Systems That Don't Crumble\",\"description\":\"How to build a design system that scales across platforms without turning every change into a boss fight.\",\"image\":\"https://images.unsplash.com/photo-1522071820081-009f0129c71c?auto=format&fit=crop&w=1200&q=60\",\"datePublished\":\"2025-08-17\",\"author\":{\"@type\":\"Person\",\"name\":\"Team Sprocket\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Sprocket Solutions\"},\"keywords\":\"Design, Systems, UI/UX\"}"}}],["$","div",null,{"className":"relative h-96 overflow-hidden","children":[["$","$L2",null,{"src":"https://images.unsplash.com/photo-1522071820081-009f0129c71c?auto=format&fit=crop&w=1200&q=60","alt":"Design Systems That Don't Crumble","fill":true,"className":"object-cover","priority":true}],["$","div",null,{"className":"absolute inset-0 bg-black/50"}]]}],["$","section",null,{"className":"max-w-4xl mx-auto px-6 py-12 -mt-24 relative z-10","children":[["$","$L3",null,{"href":"/blogs","className":"inline-flex items-center text-purple-600 hover:text-purple-800 transition mb-6 font-medium","children":[["$","svg",null,{"xmlns":"http://www.w3.org/2000/svg","width":24,"height":24,"viewBox":"0 0 24 24","fill":"none","stroke":"currentColor","strokeWidth":2,"strokeLinecap":"round","strokeLinejoin":"round","className":"lucide lucide-arrow-left w-5 h-5 mr-1","aria-hidden":"true","children":[["$","path","1l729n",{"d":"m12 19-7-7 7-7"}],["$","path","x3x0zl",{"d":"M19 12H5"}],"$undefined"]}],"Back to all Blogs"]}],["$","article",null,{"className":"bg-white rounded-3xl shadow-2xl p-8 md:p-12","children":[["$","div",null,{"className":"flex flex-wrap gap-3 mb-4 text-sm text-gray-500","children":[["$","span",null,{"className":"font-medium text-purple-600","children":"Team Sprocket"}],["$","span",null,{"children":"•"}],["$","time",null,{"dateTime":"2025-08-17","children":"August 17, 2025"}],["$","span",null,{"children":"•"}],["$","span",null,{"className":"flex items-center","children":[["$","svg",null,{"xmlns":"http://www.w3.org/2000/svg","width":24,"height":24,"viewBox":"0 0 24 24","fill":"none","stroke":"currentColor","strokeWidth":2,"strokeLinecap":"round","strokeLinejoin":"round","className":"lucide lucide-clock w-4 h-4 mr-1","aria-hidden":"true","children":[["$","path","mmk7yg",{"d":"M12 6v6l4 2"}],["$","circle","1mglay",{"cx":"12","cy":"12","r":"10"}],"$undefined"]}],8," min read"]}]]}],["$","h1",null,{"className":"text-4xl md:text-5xl font-extrabold text-gray-900 mb-6 leading-tight","children":"Design Systems That Don't Crumble"}],["$","div",null,{"className":"flex flex-wrap gap-2 mb-8","children":[["$","span","Design",{"className":"text-xs px-3 py-1 rounded-full bg-blue-100 text-blue-700 font-medium","children":"Design"}],["$","span","Systems",{"className":"text-xs px-3 py-1 rounded-full bg-blue-100 text-blue-700 font-medium","children":"Systems"}],["$","span","UI/UX",{"className":"text-xs px-3 py-1 rounded-full bg-blue-100 text-blue-700 font-medium","children":"UI/UX"}]]}],["$","div",null,{"className":"blog-content text-gray-800","dangerouslySetInnerHTML":{"__html":"<p>Building a design system is easy; maintaining one is the real challenge. The moment your team grows or your product expands to a new platform, the beautifully structured system often starts showing cracks.</p><h2>1. The Component Library is Not Enough</h2><p>A common mistake is treating the design system purely as a component library. A true design system is a living, breathing set of principles, guidelines, and code.</p><h3>Conclusion</h3><p>A non-crumbling design system is a product in itself. Treat it with the same rigor, planning, and continuous iteration as your main application.</p>"}}]]}]]}]]}],null,["$","$L4",null,{"children":["$","$5",null,{"name":"Next.MetadataOutlet","children":"$@6"}]}]]}],"isPartial":false,"staleTime":300,"varyParams":null,"buildId":"Vo073p63oA0iU5rRtp-n3"}
6:null