Why Rails Blueprint Uses Slim + Bootstrap: The Token Economics of AI-Assisted Development
We measured 10 tech stacks to answer one question: which choices optimize for AI context windows? The data surprised us.
Blog
Details on how Rails Blueprint works and tips on making your work easier and faster
Read more
To Everyone Who Sorted Their TODOs by Color Instead of Shipping: We See You
The Monday I Won Gold at Not Shipping I sat down to “finally ship the MVP.” Two hours later, my README had a legend, gradient labels, and a semantic rainbow of TODOs that would make a design system blush. The deploy button? Untouched. Somewhere, a kanban board applauded; my users did not. Th...Read more
“I’ll Wire Up Auth Tonight” And Other Famous Last Words
The promise we all make at 7pm We’ve all said it: “I’ll wire up auth tonight.” The laptop opens, the tea is warm, confidence is high. Two hours later you’re diagramming password reset flows like a detective connecting yarn on a corkboard. Somewhere, a sunrise files a missing person report for...Read more
Why We Chose Slim Templates Over ERB or HAML: A Deep Dive into Rails Blueprint's View Layer
When building Rails Blueprint, one of our earliest architectural decisions was choosing the templating engine. While ERB comes built-in with Rails and HAML has a strong following, we chose SlimвАФand after thousands of lines of production code, we're confident it was the right choice.
This article explores why Slim templates power Rails Blueprint, backed by real performance data, developer productivity metrics, and practical examples from our codebase.
Breaking out of turbo-frame
When using turbo-frames all page updates by default are limited to the frame which initiated the request. On frontend you can change target frame by setting data-turbo-frame attribute on links (and use _top to update the whole page). But what if you want to make that decision on backend? U...Read more