Rails Controllers

Structure

• Only RESTful public actions: index, show, new, create, edit, update, destroy
• If a controller needs custom public methods, extract them to a new controller scoped to that feature
• Use respond_to in create, update, and destroy — not in index unless multi-format is needed

REST Mapping (resources, not verbs)

• For non-CRUD actions, create a new resource rather than a custom verb on the existing controller
  • POST /cards/:id/close → Cards::ClosuresController#create (POST /cards/:id/closure)
  • DELETE /cards/:id/close → Cards::ClosuresController#destroy
  • POST /cards/:id/archive → Cards::ArchivalsController#create
• The new resource is often a real record (see "State as Records" in rails-models), so the controller stays plainly RESTful

Configuration Order

Always declare configuration in this order:

1. Authentication/authorization declarations
2. Rate limiting
3. Before actions