ce-dhh-rails-style

Map every action to CRUD on a resource by converting verbs into noun resources, such as POST /cards/:id/closure instead of a custom close action. Use controller concerns like CardScoped for shared behavior and respond with Turbo Streams for partial updates.

State is tracked as separate records, such as a Card::Closure model, instead of boolean columns. Predicates like card.closed? check for the presence of the related record, and queries use joins or where.missing to filter open versus closed cards.

This style uses Minitest with fixtures because it ships with Rails, has less DSL magic, and boots faster. Fixtures provide deterministic preloaded data, and tests ship in the same commit as the feature rather than following strict TDD.

No, it replaces Devise with a custom magic link authentication of roughly 150 lines using Session and MagicLink models. This avoids password storage liability and gives full control over the authentication flow.

They avoid devise, pundit, sidekiq, redis, view_component, GraphQL, factory_bot, RSpec, and Tailwind. Instead they use Solid Queue, Solid Cache, fixtures, Minitest, standard partials, and native CSS with layers and OKLCH colors.

In DHH style, business logic stays in fat models with verb methods like card.close rather than service objects like CardCloser.call(card). Plain Ruby objects are only used for namespaced presentation or bundling logic under parent models.