The Model-View-Controller (MVC) design pattern is heavily used (and misused) in the PHP world. Many PHP frameworks help us – expect us – to organize our web application around this pattern. We’ll examine the intended separation of concerns. We’ll see the middleware, the request-response loop. We’ll configure GET and POST routing. We’ll look at the pattern itself. The model represents the data in our application. The view is the visual component that presents the interface for users to interact with that data, such as clickable links, form fields, and buttons. The controller coordinates it all.

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