Update controller organization rules (#113)

Author: AELSchauer

general/README.md

@@ -45,7 +45,7 @@ Style and best practices that apply to all languages and frameworks.
 
 ## Organization
 
-- Define methods alphabetically.
+- Define methods alphabetically. (See Rails guide for more details about an exception in controllers.)
 - Define class methods before instance methods.
 - Always define the `initialize` method of a class at the top of instance method
   definitions.

rails/.rubocop.yml

@@ -20,6 +20,10 @@ Rails/ActionFilter:
   Description: "Enforces consistent use of action filter methods."
   Enabled: false
 
+Rails/ActionOrder:
+  Description: "Enforces the order of CRUD controller methods."
+  Enabled: true
+
 Rails/Date:
   Description: >-
     Checks the correct usage of date aware methods,

rails/README.md

@@ -12,7 +12,9 @@ A guide for building great Rails apps.
   attribute name.
 - Order ActiveRecord validations alphabetically by attribute name.
 - Order ActiveRecord associations above ActiveRecord validations.
-- Order controller contents: filters, public methods, private methods.
+- Order controller contents: standard actions, custom actions, filter methods, private methods.
+  - Standard methods should be organized using the official Rails order (see `Rails/ActionOrder` cop)
+  - All other methods should be organized in their respective sections alphabetically
 - Order i18n translations alphabetically by key name.
 - Order model contents: constants, macros, public methods, private methods.
 - Use link_to for GET requests, and button_to for other HTTP verbs.