<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tailwind on Nitzan's Blog</title><link>https://blog.nitzan.fyi/tags/tailwind/</link><description>Recent content in Tailwind on Nitzan's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 06 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.nitzan.fyi/tags/tailwind/index.xml" rel="self" type="application/rss+xml"/><item><title>From Zero to Launch: Takeaways from Our Frontend Journey</title><link>https://blog.nitzan.fyi/posts/from-zero-to-launch/</link><pubDate>Fri, 06 Sep 2024 00:00:00 +0000</pubDate><guid>https://blog.nitzan.fyi/posts/from-zero-to-launch/</guid><description>&lt;p&gt;Around six months ago, I made what some would say is a bold decision by &lt;a href="https://blog.nitzan.fyi/posts/choosing-a-frontend-framework-in-2024/"&gt;choosing Remix as the foundation for our company&amp;rsquo;s web application&lt;/a&gt;. Fast forward to today, and I think it&amp;rsquo;s time to take a step back and reflect on the choices we made. I&amp;rsquo;ll go over the main infrastructure decisions made and sprinkle a bit of practical usage examples on the way.&lt;/p&gt;
&lt;p&gt;So, without further ado, let&amp;rsquo;s jump straight into the highlights and lowlights of this journey — a mix of satisfaction and lessons learned.&lt;/p&gt;</description></item></channel></rss>