<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on marwa.gorvan.com</title><link>https://marwa.gorvan.com/categories/ai/</link><description>Recent content in AI on marwa.gorvan.com</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Mon, 21 Sep 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://marwa.gorvan.com/categories/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Design System Documentation in the Age of AI</title><link>https://marwa.gorvan.com/writing/design-system-documentation-in-the-age-of-ai/</link><pubDate>Mon, 21 Sep 2026 12:00:00 +0000</pubDate><guid>https://marwa.gorvan.com/writing/design-system-documentation-in-the-age-of-ai/</guid><description>&lt;p>&lt;img src="https://marwa.gorvan.com/images/robot-jetsons.gif" alt="Rosey the Robot from the Jetsons" />&lt;/p>
&lt;p>As AI develops at a rapid pace, design system documentation is struggling to keep up. Documentation now serves two very different audiences: humans and machines.&lt;/p>
&lt;p>Since the rise of design systems, teams have relied on documentation to explain how components, tokens, and patterns should be used. Traditionally, this documentation was written by humans, for humans. It told designers and engineers which tokens to use, how much spacing was required, and which button variant belonged in a particular context.&lt;/p></description></item></channel></rss>