Framework Structure
The first thing that needs to get addressed is thinking about a suitable file structure so that everything has its place. Most websites and applications have:
- Commonly used functions and classes
- Business logic
- A layout and design
Files related to each of those three categories should be grouped together in their own section. So far, I created the following (simple) file structure to address this:
- System Folder
- Application Folder
- Public Folder
Core classes and objects such as database access, authentication, request handling and email sending are going to be stored in the System folder.
Next, we need a place to store the business logic which are the files that are going to make use of the framework. A.K.A the website or application itself. All those things like controllers, models, views or specific configurations are going to be stored in the Application folder.
Last, the public content like CSS files, index file and images are going to be stored in the public folder. Added benefit is that we can point the document root to this folder to make sure that the application files are not accessible for the outside world. It adds some security.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Bart Willemsen
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Bart Willemsen
- Completed by
- Bart Willemsen