That was just a quick idea and definitely not fully thought, but an additional point 5. of that "get started" web page procedure, could be a jump to the new app development guide in the works, where the user then creates an app from scratch, and IIRC will be using the standard maven archetypes in such process, cause it targets EAP too. Anyway still just quick thoughts, IMHO what would be of most importance now would be figure out if archetypes is the right direction, cause it won’t be nice to send users now in such direction, and then ask them to abandon such idea.
I don’t think that the archetypes are the important piece here.
They are just a way to generate a clean, valid and complete Maven project to run a Jakarta EE application on WildFly.
An user would use the archetype once to bootstrap their app and then they no longer needs anything from it.
If/when we have a code launcher that does that, the output will be the same: a clean, valid and complete Maven project to run a Jakarta EE application on WildFly.
Releasing a code launcher should not (and MUST not) invalidate any Maven projects that were created by another mechanism.