Developing the Behavioral Layer for a Content Management System with Prototype
Developing the Behavioral Layer for a Content Management System with Prototype (Page 1 of 4 )
Welcome to the second installment of the series that began with "Building a Content Management System with Prototype." As the article's title claims, this series teaches you how to create a useful CMS application in a step-by-step format, which allows you to easily insert, edit and delete contents from a simple MySQL database.
As you'll probably recall, in the preceding tutorial of the series I explained in a friendly fashion how to create a simple graphical interface for providing users with the capacity to add new contents to the content management system, aside from being able to edit the contents, or eventually delete them.
In this case, I demonstrated the use of this application by using some data related to publishable articles, including information about authors, article titles, and so forth, but since the structure of the system is actually very flexible, it can be easily modified to work with contents of a different nature.
All in all, at this point I believe that the simple front-end that was built in the previous article of the series shouldn't be hard for you to grasp at all, therefore it's time to take the next step involved in the development of this Prototype-based content management system.
All right, having introduced clearly the topics that will be treated over the course of this article, let's move on together and see how to build the behavioral layer that corresponds to this Prototype-driven CMS. Let's get started now!