I have been assigned to build a Drupal 8 "CMS" system. After working for sometime with mild success there is a possibility to use another framework to build a more flexible and robust platform.
The scope of the project is not defined which is part of the problem, but I digress. (Basically, I working with people who don't have clue as to what they want) I think it's time to move away from Drupal and build a custom CMS. As the project will have a variety of non Drupal feature in the months to come. Now what I need is some facts to back this up. Wappalyzer used to provide charts of usage of certain frameworks.
I was wondering if there any site or articles out there I could use to prove to a non-technical person, why we should move away from Drupal. Website usage, security concerns, or hiring trends, etc.
Although I don't mind Wordpress, it has such a bad security reputation, the sysadmin won't consider it.
I would like to use Laravel or Codeigniter but need some evidence as to back it up.
Drupal is a fine off the shelf CMS that is very extensible. I'd argue it has framework like features, but with the goal to extend CMS capabilities.
I don't know enough about your use case to suggestion one over the other.
If you're in the position of choosing between Drupal, Laravel, etc. you are probably in the position to evaluate other solutions not based on PHP.
If you just need a CMS, there are tons of open-source CMS already built that you can use commercially for free. Why spend time/money building a new one?
At this point, Laravel is so widespread in the PHP world, you might as well just use it. They have a smaller version (Lumen, I think?) that is probably faster to learn and much lighter-weight.
The good news is time and money is not an variable in the equation. (meaning I'm not working in the real world...)
If I do understand that correctly, if I were you, I would spend some serious time learning about why they picked Drupal in the first place. If you run into brick walls, keep on knocking on doors until someone eventually lets you in.
I have been involved in many projects, but I have never seen one with very loose requirements end well.
I'm probably wrong and it's just my opinion, but Laravel feels like it's a one man show.