<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Graphic Meat Field Notes</title><link>https://graphicmeat.com/blog</link><description>Ideas on product design, private software and building useful independent apps.</description><language>en</language><atom:link href="https://graphicmeat.com/feed.xml" rel="self" type="application/rss+xml"/><item><title>The web solved automatic masonry. Why haven’t photobooks?</title><link>https://graphicmeat.com/blog/automatic-masonry-layouts-photobooks</link><guid isPermaLink="true">https://graphicmeat.com/blog/automatic-masonry-layouts-photobooks</guid><pubDate>Sun, 12 Jul 2026 09:00:00 +0300</pubDate><description>Why automatic photobook design needs crop awareness, hierarchy, rhythm and scoring—not only space filling.</description></item></channel></rss>
