In my opinion, both the diagram seem to show the same thing, but not with the same appearance.
What is important when starting with the MVC architectural pattern is to really separate all of the parts :
- Controller : It is often the entry point for the request. There are more and implementation where there is a routing middleware not included inside the controller. But as all the guide and books will tell you, the controller is where you'll spend most of your time
- Model : The model is sometimes mixed with the ORM. The purpose of the model is only to be the center of the data of your application. In almost all implementation, the model is closely tied to the ORM, and sometimes we have one model for each table / document type.
- View : The view can be as simple as you want it. The important part is to remember that you should never put logic inside your View. Logic = Controller. The only thing you should put in your views are datas, markup and the minimal amount of code to make it work. A lot of implementation of views use template engine to allow a small amount of logic to be used in the view without using a full fledged programming language.
All in one, when teaching web dev, my students found quite interesting to create (with help of course), a small MVC framework to try and see how it works.
There is no definitive guide that I know of, but using, for example, a small framework like Tiny MVC as a boilerplate has yielded good results.