[wildfly-dev] Re: Create a "get started" page on WildFly.org

On 9 Aug 2023, at 12:41, Eduardo Martins <emartins(a)redhat.com&gt; wrote: You’re right. That’s a good thing to clarify. My goal with that thread is to make WildFly more accessible and improve its user experience. Part of that is the tooling (code generator, maven archetype, whatever) but if we do not let users find out and help them get started, all the tooling improvements we are doing are lost to them. In that sense, I don’t see why we could not create a getting started page *now* with what we have. I’m not sure what you mean here. WildFly already has 3 archetypes that are released every time. Unfortunately none of them are a good starting point: * wildfly-subsystem-archetype generates a WildFly subsystem -> it’s out of scope and targets WildFLy developers, not WildFly users * wildfly-jakartaee-ear-archetype generate a EAR project -> Users should get started with a WAR and move to an EAR when their application is sufficiently complex to require them. * wildfly-jakartaee-webapp-archetype -> This one could be a starting point but I agree with Darran that it’s not simple enough to get started. It uses also JSF and JPA (with H2 as the default database?). The goal of getting started is that the user can build on top of it. If we use that one, we have to ask the users to remove things and that’s a poor UX. I don’t know. However the output of their code generator is a Maven project. It would be the same for WildFly. We can start with a Maven archetype now (Darran’s draft PR is quite close to be ready imho) and update it with a code generator when we have one. You mention you wanted to start this in Q4 and I don’t know the amount of work to create such generator but I don’t want to wait until Q1 2024 or later to improve the user experience of WildFly (and wildly.org). Best regards, Jeff -- Jeff Mesnil Engineer @ Red Hat JBoss EAP http://jmesnil.net/