Thanks for the good catch, @jobara. All addressed except this one. 

Triggering simply events in the callback functions of show/hide would result in the event firing depending on the finish of show/hide functions. If anyhow the finish callback is not fired perhaps in the failure of show/hide, our simplify events won't be fired as well. And, I think the show/hide of the footer, header etc is just one step of the simplifying process. It doesn't make a lot of sense to use them to control other steps.

I noticed my current way to name those events with "after" prefix may not really be "after" once the adding/removing of the css class are declared via simplify events. I've renamed them with "on" prefix.

Let's chat about this when you come back tomorrow.