<?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 for TSUX	</title>
	<atom:link href="https://thomas-sokolowski.com/en/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://thomas-sokolowski.com/en</link>
	<description>User Experience Design Blog</description>
	<lastBuildDate>Wed, 13 Nov 2024 13:02:18 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.2</generator>
	<item>
		<title>
		Comment on The Ideal UX Design Workflow by Kai Motta		</title>
		<link>https://thomas-sokolowski.com/en/the-ideal-ux-design-workflow/#comment-153</link>

		<dc:creator><![CDATA[Kai Motta]]></dc:creator>
		<pubDate>Tue, 16 Feb 2021 10:51:14 +0000</pubDate>
		<guid isPermaLink="false">https://thomas-sokolowski.com/?p=857#comment-153</guid>

					<description><![CDATA[Thank you for a great article. As a UX designer I am a huge advocate of Jesse James Garrett and The Elements of User Experience. I use his 5 layered model as the basis for all my work.]]></description>
			<content:encoded><![CDATA[<p>Thank you for a great article. As a UX designer I am a huge advocate of Jesse James Garrett and The Elements of User Experience. I use his 5 layered model as the basis for all my work.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Atomic Design 2.0 by Jax Engel		</title>
		<link>https://thomas-sokolowski.com/en/atomic-design-2-0/#comment-26</link>

		<dc:creator><![CDATA[Jax Engel]]></dc:creator>
		<pubDate>Mon, 26 Oct 2020 16:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://demo.krownthemes.com/koncept/?p=136#comment-26</guid>

					<description><![CDATA[As a designer with a focus on design systems, I find this perspective really interesting! 

I had the pleasure of meeting and doing a workshop with Brad Frost and Dan Mall at Artifact Conf back in 2019. One of my discussion points was about the true definition of &quot;atoms&quot; and the necessity of &quot;pages&quot;. Many people argue that styles are atoms while small components like buttons or inputs are atoms. The answer was something along the lines of &quot;do what works best for your product/team&quot;. 

I really love your introduction of the styles layer specifically, because &quot;atoms&quot; implies it cant be broken down further. A button can be broken down into styles. I also appreciate the focus here on templates over pages: when we design a system, defining the exact placement and organization of a &quot;page&quot; sort of defeats the purpose of the system itself. The system should be flexible in a way that the &quot;segments&quot; and &quot;templates&quot; can be used multiple ways, such as by different teams on different products under one brand, and still be cohesive. 

Thank you for this article! Definitely checking out Atomic Kitchen.]]></description>
			<content:encoded><![CDATA[<p>As a designer with a focus on design systems, I find this perspective really interesting! </p>
<p>I had the pleasure of meeting and doing a workshop with Brad Frost and Dan Mall at Artifact Conf back in 2019. One of my discussion points was about the true definition of &#8220;atoms&#8221; and the necessity of &#8220;pages&#8221;. Many people argue that styles are atoms while small components like buttons or inputs are atoms. The answer was something along the lines of &#8220;do what works best for your product/team&#8221;. </p>
<p>I really love your introduction of the styles layer specifically, because &#8220;atoms&#8221; implies it cant be broken down further. A button can be broken down into styles. I also appreciate the focus here on templates over pages: when we design a system, defining the exact placement and organization of a &#8220;page&#8221; sort of defeats the purpose of the system itself. The system should be flexible in a way that the &#8220;segments&#8221; and &#8220;templates&#8221; can be used multiple ways, such as by different teams on different products under one brand, and still be cohesive. </p>
<p>Thank you for this article! Definitely checking out Atomic Kitchen.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on The User Experience Wheel by Iris Chen		</title>
		<link>https://thomas-sokolowski.com/en/the-user-experience-wheel/#comment-2</link>

		<dc:creator><![CDATA[Iris Chen]]></dc:creator>
		<pubDate>Mon, 10 Dec 2018 04:31:45 +0000</pubDate>
		<guid isPermaLink="false">https://thomas-sokolowski.com/?p=884#comment-2</guid>

					<description><![CDATA[Fantastic Work! 
Could you share the source so that I can translate it into Chinese since I am from China. Thx.]]></description>
			<content:encoded><![CDATA[<p>Fantastic Work!<br />
Could you share the source so that I can translate it into Chinese since I am from China. Thx.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
