dhh-rails-style

DHH Rails style enforces fat models and thin controllers by moving domain logic into model objects and keeping controllers strictly RESTful. Refactoring involves simplifying controller actions, using resource-oriented routes, and ensuring business rules live in the model layer.

Current attributes in Rails provide a thread-safe way to access global request context like the current user. DHH style implements them as singleton objects to avoid passing context explicitly through every method, keeping domain logic clean and readable.

You need Turbo patterns in Rails when building modern, single-page-like interactions without heavy JavaScript. DHH style integrates Turbo to handle partial page updates and form submissions, ensuring fast navigation and maintaining RESTful, server-driven application architecture.

DHH Rails style prioritizes REST purity and resource-oriented design but does not strictly forbid custom routes. It encourages keeping controllers slim by favoring standard RESTful actions, moving complex logic into fat models rather than adding non-RESTful controller endpoints.

Conduct a Rails code review using 37signals conventions by checking for REST purity, slim controllers, and rich models. Verify that Current attributes and Turbo patterns are applied correctly, ensuring the domain logic remains readable and structurally aligned with Basecamp and HEY standards.

The best way to structure domain logic in Rails models following DHH style is creating fat models with readable, explicit business rules. Move complex operations out of controllers into model methods, ensuring the code aligns with 37signals conventions and remains maintainable.