You may have learned how to write proper Rails MVC features with skinny controllers and fat models. You may have learned how to properly compose your features in terms of RESTful resources. But, how do you write a proper easy to maintain Wizard without resulting in a fat controller, violating REST, or writing complicated Wizard step data management code? Do you use multiple controllers? Multiple actions in one controller? A state machine? An existing Wizard gem?
These are all questions that will get answered in this talk, in which I plan to share a simple Wizard approach that I stumbled upon while working on my last two Rails projects. It made it super easy to add Wizard steps by both junior and senior Rails developers on the projects.
Attendees should walk out of this talk with solid knowledge on how to build a light maintainable Rails Wizard, achieving proper separation of responsibilities between controllers and models, and maintaining a RESTful paradigm without the complexity of Wizard step management.