<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ano blog</title><description>Notes from the team building Ano. Product updates, build decisions, field notes. One post per week.</description><link>https://ano.chat/</link><language>en</language><item><title>Astro 6 + Specific.dev: the stack ano.chat ships on</title><link>https://ano.chat/blog/astro-6-specific-dev-website-magic</link><guid isPermaLink="true">https://ano.chat/blog/astro-6-specific-dev-website-magic</guid><description>Three decisions made the marketing site fast: Specific.dev for deploys, Astro 6 for the user experience, typed markdown for content. Here is what each buys us, and where the stack still bites.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate><category>engineering</category><category>astro</category><category>specific</category><category>performance</category><category>marketing-site</category><author>Ruben Flam</author></item><item><title>Why we built Ano on Zero, not on the Slack model</title><link>https://ano.chat/blog/why-we-built-ano-on-zero</link><guid isPermaLink="true">https://ano.chat/blog/why-we-built-ano-on-zero</guid><description>Slack-style chat puts the server in the middle of every interaction. We picked Zero, a local-first sync engine, and worked the architecture inwards from the user. Here is what changed, and why.</description><pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate><category>engineering</category><category>zero</category><category>sync</category><category>slack-alternative</category><author>Ruben Flam</author></item></channel></rss>