dhh-rails-style

To enforce DHH Rails coding conventions, align your codebase with RESTful controller structures, heavy-domain models, and state-as-record patterns. This keeps Ruby and Rails code readable, maintainable, and aligned with 37signals design principles.

The best way to structure Rails controllers using RESTful patterns is to use dedicated resources like closures, archives, and comments. This keeps controllers slim and models expressive while adhering to DHH Rails style conventions.

Handle cross-cutting concerns and domain logic in Rails by applying state-as-record patterns and horizontal concerns. This approach enables reusable, composable domain logic without bloating controllers or models.

Yes, the DHH Rails style guide works with Minitest and fixtures, providing clear testing guidance to support end-to-end workflows. It also includes front-end patterns using Turbo and Stimulus for integrated testing.

Yes, you can use DHH Rails style for refactoring existing Rails applications. It guides you to identify key domain models, extract cross-cutting concerns, and replace ad-hoc actions with resource-based controllers.

You should not use DHH Rails style if your Ruby application does not follow Rails conventions or if you prefer alternative testing frameworks over Minitest, as this style heavily relies on Rails-native RESTful patterns and specific testing guidance.