9:51 a.m.
On Wed, Aug 9, 2023 at 9:07 AM Jeff Mesnil <jmesnil(a)redhat.com> wrote:
> On 9 Aug 2023, at 15:43, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
>
>
>
> On Wed, Aug 9, 2023 at 6:20 AM Jeff Mesnil <jmesnil(a)redhat.com> wrote:
> On 9 Aug 2023, at 12:41, Eduardo Martins <emartins(a)redhat.com> wrote:
> >
> > Oh I didn’t meant we should only have one solution, was just trying to
clarify what you are targeting now.
>
>
> 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.
>
> Sure, iteration is good.
>
> How will this fit into the wildfly.org landing page? That's something
to have a clear idea of from the start, as the true 'getting started' point
is the landing page.
When I go to wildfly.org, ideally, I’d like to get a « Get Started » link
in the menu at the top.
I’d get rid of the « Home » link as it duplicates the WildFly icon (and
it’s a well-known idiomatic pattern to have the icon at the top-left of the
page being a link to the home page).
+1
So the top of home page of wildfly.org would look like
| "icon » |News| |About| |Contribute| |Get Started| |Docs| |CVE
Reporting| |Fork|
Limiting links to this to the header might be ok for the very first
iteration, but I think ultimately this would alter the main body of the
page. Right now we kind of emphasize downloads, and next we link to
github, docs and the forum.
Also, I noticed that in the header the Fork link is always emphasized with
a box. I think Get Started is a better choice.
I’d also remove the |Downloads| page as it is a visible button on the home
page.
I don't want to get too into the weeds but I want to point out this is a
common header on all pages, and changing it per page starts to open a can
of worms.
This « get started » page would be a starting point but it might not
be
sufficient for more complex use cases (eg using domain mode). However once
the user has follow the instructions to get WildFly up and running, we
could have a section with Next steps. One of these could be « there are
other way to install WildFly (zip, galleon, bootable jar », please
consulter our installation guide at
https://docs.wildfly.org/latest/Installation_Guide.html to learn more
about them ».
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His