There a reason why you should build your own framework?
First of all, how big is your project? How many projects do you work on? How much functionally are you looking for?
Second of all, do you have enough time and knowledge to build your own framework?
The first step is listing a few features that you need:
- A global template(or multiple templates) that can changed from page to page or stay static throughout the whole site.
- Simple content placement, pages(determined by the URI)-would be loaded into the template.
- Quick database access.
- Data Sensitization.
…and go from there.
I like using OOP(Object Orientated Programming) for my framework because it makes things so much easier.
It’s only as complicated as you make it. Just integrate the features that you need, keep it secure and keep tweaking it until it meets up to your personal standards.
The things that you should look for in any framework before it’s used in public:
- Freedom and flexibility
- Quality and performance
The ultimate goal for your framework should be to save time as well as to give yourself a little extra freedom. All you need to do is write up a plan and start coding:)
Oh, and you might find this site helpful from time to time: http://php.net