<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: The DesignWhine Guide to Design Systems	</title>
	<atom:link href="https://www.designwhine.com/design-system/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.designwhine.com/design-system/</link>
	<description>Tech Through A Design Lens</description>
	<lastBuildDate>Fri, 11 Sep 2026 13:55:45 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		By: Design System Governance: Ownership, Contribution And Maintenance		</title>
		<link>https://www.designwhine.com/design-system/#comment-284</link>

		<dc:creator><![CDATA[Design System Governance: Ownership, Contribution And Maintenance]]></dc:creator>
		<pubDate>Fri, 11 Sep 2026 13:55:45 +0000</pubDate>
		<guid isPermaLink="false">https://www.designwhine.com/?p=17140#comment-284</guid>

					<description><![CDATA[[&#8230;] DesignWhine Guide to Design Systems argues that a design system is product infrastructure and institutional memory, not merely a [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] DesignWhine Guide to Design Systems argues that a design system is product infrastructure and institutional memory, not merely a [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: DesignWhine Editorial Team		</title>
		<link>https://www.designwhine.com/design-system/#comment-275</link>

		<dc:creator><![CDATA[DesignWhine Editorial Team]]></dc:creator>
		<pubDate>Fri, 11 Sep 2026 09:02:12 +0000</pubDate>
		<guid isPermaLink="false">https://www.designwhine.com/?p=17140#comment-275</guid>

					<description><![CDATA[What is the hardest part of a design system in practice for your team: building components, getting adoption, keeping design and code aligned, governance, or making the system usable by AI?]]></description>
			<content:encoded><![CDATA[<p>What is the hardest part of a design system in practice for your team: building components, getting adoption, keeping design and code aligned, governance, or making the system usable by AI?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
