<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Encodings on Visualization Snacks</title>
		<link>http://pages.graphics.cs.wisc.edu/VisSnacks/tags/encodings/</link>
		<description>Recent content in Encodings on Visualization Snacks</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 17 Jul 2026 15:30:00 -0500</lastBuildDate>
		
			<atom:link href="http://pages.graphics.cs.wisc.edu/VisSnacks/tags/encodings/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Encodings: Building Blocks for Visualizations</title>
				<link>http://pages.graphics.cs.wisc.edu/VisSnacks/tutorials/encodings/</link>
				<pubDate>Fri, 17 Jul 2026 15:00:00 -0500</pubDate>
				<guid>http://pages.graphics.cs.wisc.edu/VisSnacks/tutorials/encodings/</guid>
				<description>&lt;p&gt;Visualizations are built by &lt;strong&gt;encoding&lt;/strong&gt; data into visual properties: position, size, color, shape, and so on. Thinking in terms of these building blocks - rather than in terms of chart types - lets you decompose designs, compare choices, and invent new things. And one building block towers over the others: position. Spend it wisely.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Charts Are Just Encodings in Disguise</title>
				<link>http://pages.graphics.cs.wisc.edu/VisSnacks/snacks/charts-are-encodings/</link>
				<pubDate>Fri, 17 Jul 2026 15:30:00 -0500</pubDate>
				<guid>http://pages.graphics.cs.wisc.edu/VisSnacks/snacks/charts-are-encodings/</guid>
				<description>&lt;p&gt;A chart type is a bundle of encoding choices that someone found useful enough to name. Decomposing charts into their encodings explains why &amp;ldquo;line vs. bar&amp;rdquo; questions have answers, and shows you design choices (like ordering) that the chart names hide.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
