dhh-rails-style

DHH Rails style enforces RESTful, readable conventions across models, controllers, and views using patterns like Current attributes, concerns, and Turbo Streams. Start by integrating these conventions into new code, then gradually refactor existing components to use domain-oriented concerns and lean controllers instead of service objects.

DHH style prioritizes fat models with domain logic, RESTful controllers, and Turbo-driven updates over service objects and complex layering. This approach reduces cognitive load by keeping related concerns cohesive and emphasizing conventional Rails patterns used at 37signals and Basecamp.

Yes. DHH Rails style explicitly codifies patterns for Turbo Streams and Stimulus integration, guiding how to structure controllers and views for real-time updates while maintaining RESTful principles and readable code organization.

Current attributes store request-scoped data like the authenticated user without passing context through every method. DHH style encourages using Current for clean, maintainable access to shared state in models and controllers aligned with 37signals conventions.

Concerns group related model behaviors and responsibilities into reusable modules, keeping models focused and maintainable. DHH style uses domain-oriented concerns to extract common patterns across models while preserving readability and conventional structure.

DHH Rails style guides reviews toward RESTful controller design, lean actions, fat models with cohesive logic, and Turbo-driven interactions. It helps align discussions on whether code follows conventional Rails patterns and reduces unnecessary abstraction layers.