Repository navigation
Web development frameworks #136
Description
I would like to prepare a tutorial about modern web development framework, with a focus on MVC (or similar) architecture-based ones.
After a general introduction, I would like to describe AngularJS (https://angularjs.org/) along with the quite new and really interesting Ionic (http://ionicframework.com/) and/or Ruby on Rails (http://rubyonrails.org/), with some little hands-on exercises and such things.
Good idea? Bad idea?
Activity
despo commentedon Oct 23, 2014
@matteomeli Great idea. I've been thinking about this recently, and at this point, I think adding an introduction to an MVC framework would be really useful for the students (and would give them a better understanding.
I would rather we didnt have anything Rails specific in at the moment, but have no personal preferences about frameworks.
DanTheBlue commentedon Mar 11, 2015
Hey, I would be interested in helping if this is still considered?
I think explaining standard terms like MVC might be very important, and almost focusing a few tutorials on the abstract ideas before bringing in the concrete examples might be cool.
Shameless plug, but I wrote about the MVC framework on my blog. Feel free to have a look, and I am happy to adapt it or use it for the tutorials here if people are happy :) Of course, do let me know if its not right.
http://humbledeveloper.net/model-view-controller/
matyikriszta commentedon Mar 17, 2015
hi @DanTheBlue, this is still very much considered. I agree we need an overview of the abstract concepts before we jump into the specific. Would you be willing to put together a rough draft for this based on your blog post? Also, what other terms/concepts we should focus on as the basis?
DanTheBlue commentedon Mar 18, 2015
@matyikriszta Great :)
Sure can do, ill make a fork or something for a rough idea if you like, to see what people think of these new styled guides. I guess we need to go over the basics, and then have a very simple tutorial that gives you an example of how this is powerful (multiple uis for one backend system as such).
I think in these examples most of the leg work should be done, as its just an example of how it can be used.
I think we should consider things such as explaining classes and objects, databases and persistant storage and just good design (again, more of an overview than something too indepth)