cake bake [project-name]
cd project-name
cake bake all
 

=> controller name must match to a database table name;
=> If you decide to create controllers with names other than 
tables of the database, you should actually not create a 
controller but use a component instead.
=> The names of database tables as well as controllers are 
lowercase and in plural form.
=> example: orders table will have a controller php file name 
orders_controller.php under app/controllers folder. The 
controller class will follow OrdersController convention (CamelCased).

 

=> The view name will be the same as actions defined in 
controller. Suppose that there is an action called add (function add()), 
then there will be a view called add under 
app/views/<controller>/add.ctp.
 

If more than one controller needed to use the same actions, 
then you could create a component. The controllers could 
essentially run an include of the component and run the 
actions as if they were individually contained in the controller.
 

Component files contain actions or functions that can be used 
across all the controllers. A component typically aims to provide
tools to accomplish a main objective.

=> The file name of a component can be anything, but like 
models, views, and controllers, more than one word in the 
name must be separated by underscores and camel case when
naming the class object.

Including Components in the Controller with the $components Array
var $components = array('Session','RequestHandler');

Running a Component Function in the Controller
$user = $this->Session->read('User');

Components are not intended to work directly with the database, so 
the component does not do much more than return a variable, a 
string, or an array for the controller to use.
 

An element contains presentation output that can be pulled into 
multiple view files.

=> Elements are named like controller actions and view files and are 
stored in the app/views/elements directory.

=> Helpers and elements differ in that helpers work with view logic, 
whereas elements are more like chunks of HTML that repeat 
throughout the views.
 

=> When interacting with the database, sometimes the model will 
need to perform more complex processes than simply CRUD 
functionality. In some applications, deleting a record will require 
performing other manipulations to other tables and records,
and so on, with other database operations. Cake resolves this issue 
with behaviors, which are classes that may be called by models when
performing model functions.

=> Behaviors are stored in the app/models/behaviors directory and 
can be named anything following the same rules for naming helper 
files and components. They must have the .php extension. 
=> In the file, behavior class names are set with the following 
syntax:
class SpecialBehavior extends ModelBehavior {}

=> By using behaviors to store complex or customized model 
operations, you give the application's models more consistency.
 

Be Careful Using PHP Function Names as Action Names, such as date().