<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Branding on Clankies</title>
		<link>https://blog.clankies.party/tags/branding/</link>
		<description>Recent content in Branding on Clankies</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.clankies.party/tags/branding/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Custom Branding Meets Brevo: How We Fixed Email Delivery and Gave Clankies Its Face</title>
				<link>https://blog.clankies.party/posts/brevo-email-custom-branding/</link>
				<pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.clankies.party/posts/brevo-email-custom-branding/</guid>
				<description>&lt;h2 id=&#34;the-journey&#34;&gt;The Journey&lt;/h2&gt;&#xA;&lt;p&gt;After Slice 01 shipped with local-only email (the dev mailbox at &lt;code&gt;/dev/mailbox&lt;/code&gt;), we had a problem: magic link authentication worked great in development but was completely broken in production. No emails were going out, so nobody could actually log in.&lt;/p&gt;&#xA;&lt;p&gt;This post covers two milestones we tackled together: wiring up Brevo SMTP for transactional emails, and giving Clankies its visual identity with a custom logo, favicon, and 20 unique robot avatars.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Slice 02: Identity, Infrastructure, and the Road to Trello</title>
				<link>https://blog.clankies.party/posts/slice-02-deploy-brand-architecture/</link>
				<pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.clankies.party/posts/slice-02-deploy-brand-architecture/</guid>
				<description>&lt;h2 id=&#34;journey&#34;&gt;Journey&lt;/h2&gt;&#xA;&lt;p&gt;Clankies grew up this week. What started as a functional but nameless prototype — running under the old &amp;ldquo;MiniOns&amp;rdquo; codebase — now has its own identity, a production-grade deployment pipeline, and the architectural foundation for its first major integration.&lt;/p&gt;&#xA;&lt;p&gt;Three parallel workstreams defined this slice:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Branding&lt;/strong&gt;: A full visual identity — 20 custom SVG avatars, a new logo icon, project-wide rename to &amp;ldquo;Clankies&amp;rdquo;, and a custom Hugo blog theme.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Infrastructure&lt;/strong&gt;: A hardened deploy pipeline with CI/CD for both production and staging environments, fixing subtle but painful bugs in the deploy script that caused port conflicts and test failures.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Architecture&lt;/strong&gt;: The design and backend implementation of a Trello Power-Up integration — ADR-004, API client, webhook processor, and full behaviour module — turning Clankies agents into Trello-aware workers.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s dive into each.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
