@neokoenig I like what you've got started in the move-wheels branch. I will see if I can achieve what I want with just repackaging the current structure. I'm thinking of creating a wheels-core package that is just the wheels folder and a wheels-template-advanced that is all the other folders with a dependency on wheels-core that pulls in the wheels folder. This would allow sharing of wheels apps without including the wheels folder. Then I plan on creating a bunch of templates like wheels-template-helloworld, wheels-template-hellodynamic, and wheels-template-hellodatabase. Then the last step of the CLI wheels new would become specifying the template to use instead of hard coding the Bootstrap 3 templating into the Wheels CLI. It's not the full separation of concerns that V3 would bring but it starts that process.

Be warned, you'll find the main annoyance is that /config is essentially hardcoded to be on the same level as /wheels/ - most of the other paths are configurable... but yeah it's a PITA.

Yes, exactly. I have that in mind with all the manual steps that the user has to do removed. My ultimate goal is to make it super easy for an absolute beginner to experience the framework after installing CommandBox.

@Peter Amiri thank you for attempting to pull this off!

I've got something for you guys to test. I still have to write some readme files and probably test some more but you can go into a fresh directory and type

box install cfwheels-template-base

and it will pull down the base template which has a dependency on cfwheels-core which will get pulled down into the /wheels directory. It all works as you'd expect and you have a base CFWheels install. Then go into another fresh directory and type

box install cfwheels-template-helloworld

and that will pull down a Hello World app. The premise being that we can now check in packages into Forgbox that don;t include the core wheels directory.