the attention of the user 3.Are target of designers’ minimalism 4.Are not mobile-friendly def create @member = Member.new(member_params) respond_to do |format| if @member.save format.html { redirect_to @member, notice: 'Member was successfully created.' } format.json { render :show, status: :created} […]
the attention of the user 3.Are target of designers’ minimalism 4.Are not mobile-friendly def create @member = Member.new(member_params) respond_to do |format| if @member.save format.html { redirect_to @member, notice: 'Member was successfully created.' } format.json { render :show, status: :created} […]
the attention of the user 3.Are target of designers’ minimalism 4.Are not mobile-friendly 5.Require hacks to work with Javascript 6.Require I18N in the controller 7.Are not cache-friendly def create @member = Member.new(member_params) respond_to do |format| if @member.save format.html { redirect_to @member, notice: 'Member was successfully created.' } format.json { render :show, status: :created} […]
value of the information, so we choose a middle- ground of “showing it only once”. By doing this, we go against the REST paradigms of individual resources and nullipotence of the GET method.
ActiveRecord::Migration def change add_column :members, :status, :integer, default: 0, null: false end end # app/models/member.rb class Member < ActiveRecord::Base enum status: %i(active inactive) end
ApplicationController def destroy @member.destroy end def index @members = Member.all end def show end end @member.inactive! Member.active render @member.status
but reasoning about them can lead to a better user experience. The real minimalism is not to hide flash messages, but to remove the reasons why we need them.