Settings such as database information are currently stored as defined constants. This taks will implement associative arrays (at minimum) or more preferably a registry. Content types will be defined here most likely. At this early stage there is a controller for each content type. Later on, it is likely that there will be a singular "content" or "entity" controller that fetches particular types of data based on the url parameter for type. This will allow controller names to be moved from configuration and into the database, which is the best way to handle aliases and mapping.
Settings such as database information are currently stored as defined constants. This taks will implement associative arrays (at minimum) or more preferably a registry. Content types will be defined here most likely. At this early stage there is a controller for each content type. Later on, it is likely that there will be a singular "content" or "entity" controller that fetches particular types of data based on the url parameter for type. This will allow controller names to be moved from configuration and into the database, which is the best way to handle aliases and mapping.