dhh-rails-style

To enforce DHH Rails conventions, author code using RESTful noun resources, state-as-records, and Current attributes while keeping controllers thin and logic in fat models. Avoid heavy service layers and extraneous gems in favor of native Rails patterns.

The 37signals Rails frontend approach uses Turbo and Stimulus Hotwire patterns instead of heavy JavaScript frameworks. It champions native CSS and avoids extraneous dependencies to maintain simplicity and application speed.

Structure RESTful controllers in Ruby on Rails by mapping actions to standard CRUD operations using noun-based resources. Keep controllers thin by pushing business logic into fat models and using concerns for horizontal behavior sharing.

Avoid service objects and heavy gems in Rails applications to prevent architectural drift from 37signals conventions. DHH style favors state-as-records, Current attributes, and native framework features over unfamiliar dependencies and complex service layers.

Yes, you can use Minitest fixtures following DHH's Rails testing style. The 37signals convention requires minimal Minitest fixtures rather than expansive testing setups or external testing frameworks to validate application behavior.

Use Current attributes in Rails models as a default pattern for managing request-scoped context like the current user. This DHH convention replaces passing parameters explicitly through service layers or controller methods.