For years, I have used my own code base. Lean, clean, specific purpose and simple. As a matter fact, from one specific purpose system to another, or from one specific routing to another is very easy. Mass replace some fields names, add some extra fields and that is it.
But I do face the issues that the clients or employers on the market now even they like my portfolio very much but they wouldn't want to use my own code base. They want to go to WordPress, Drupal and Joomla. I have experience in most of these CMS but I didn't focus on one.
Now I think while keeping my own code base, still I need to use some popular 3rd party more frequently just in case. WordPress is based on blog not general purpose. Drupal is without good doc (last time I checked). Joomla I am not crazy about it.
But codeigniter is clean and simple and well documented. Plus EE is on codeIgniter (or codeIgniter borrows codes from EE like they claimed.)
My plan is
1) use codeIgniter as framework.
2) use EE as CMS
3) still keep my own code base but begin to transfer them to CodeIgniter Framework. (it won't be difficult. my own code base is MVC likely anyway.)
My question is should I use the resource from your link (I like it, clean and simple) to build my own framework and transfer my old code base to it or use CI as the framework to transfer my own code base to it?
1) you are not using codeIgniter for your brand web site is not because the license issue of CI, but because your feeling, right? brand web site can be built on CI and sold without license issue, right?
2) what else make you decided that use the source from the link you gave before and build your own Framework instead of use CI for the brand web site? because your own framework will be cleaner and leaner than CI so give your freedom to build your own branding code base?
Thanks!