The document explains the Model-View-Controller (MVC) design pattern, where the model represents data independently of the view and controller. The view displays this data and captures user actions, while the controller manages user interactions and serves data to the view. The text also references a code example from GitHub and provides information about Alena Holligan, a PHP teacher and conference leader.

1. Organization Patterns
Model, View, Controller

2. What is the MVC Design Pattern?
The Model represents the data, and does nothing else. The model does
NOT depend on the controller or the view.
The View displays the model data, and sends user actions (e.g. button
clicks) to the controller.
The Controller provides model data to the view, and interprets user actions
such as button clicks. The controller depends on the view and the model.

3. You = Controller Blocks = Models Product = View

4. Let’s look at code
…although lego would be fun too
https://github.com/sketchings/slim-tutorial-mvc

5. Alena Holligan
• Wife, and Mother of 3 young children
• PHP Teacher at Treehouse
• Portland PHP User Group Leader
• Cascadia PHP Conference (cascadiaphp.com)
@alenaholligan alena@holligan.us https://joind.in/talk/840c3