I know there are a lot of CMS out there. I work with many people that aren't very technical but know how to setup, configure and run Wordpress sites. Problem is wordpress gets very bloated very easily and can take up a lot of system resources.

I am looking for an Open Source project I could start and have people join in. Mainly to make me a better programmer. It would be nice to have feedback from other developers and work as a team (as I work alone now).

My thought was to build a Wordpress style CMS from the Ground up on Laravel 5 and Bootstrap 3+.

I use the term "wordpress style cms" kind of loosely.

I have looked at OctoberCMS which looks beautiful, but it's really designed for people that want to type on PHP code directly. Lavalite looks to be developing very slowly with only 1 or 2 updates every 6 months. I struggle to get the demo working and all the demos I found don't work either.

My idea was to rethink the CMS for the masses. Wordpress was a blog that developed into a full fledged website. It's confusing for first time users between "pages" and "posts" and "widgets" etc...

I was thinking about starting from scratch and kind of redesigning the paradigm of what a CMS should look like. I'm familiar with ExpressionEngine and Joomla (yuck). Still overly complicated. I like the simplicity of Webflow, but it's more for static websites. I want something in the middle. Something that has a great UI and even allows page building like Webflow, but has the extensibility of Wordpress. Flat file meets database. Wordpress is so DB heavy it gets overloaded easily. By having pages be created as flat files/blade templates and by leveraging memcache, redis, and by allowing scheduiding and queus natively in the CMS, and then of course by making it easy for a developer to write custom plugins for, while making it easy for a designer to design themes and pages and making it easy for the end user to add content and update content I think there is a huge market. I know Cartalyst has "platform", but I also feel like platform is aimed mainly at Dev's and not so much designers or end users.

By having extensions be Packages that could be pulled in via composer that subscribe to some basic rules I think we could build a great CMS for the next 10 years.

Is that a bad idea? Or does that sound like something people would be interested in (a) helping out with (b) see's a need for and (c) would develop and release (and/or sell) plugins for.