Yep - separating into "for developers" and "for users" is I think a good idea. I Imagine right now someone who just comes with troubleshooting is - I am sure - a bit confused where to look for help.
Not sure how to nicely design it but I think we should think about "UX experience" here and different personas we care about (I am now tapping into some past experiences where I interacted a lot with UX experts). I can think of those personas who are important: a) new user who just wants to get help b) a seasoned user who already knows Airflow but wants to step-up and contribute c) an aspiring contributor who wants to become first-time contributor d) someone who is an experienced developer and wants to contribute to Airflow knowing that it is "important" project in the space Unfortunately - we only have one website - probably we are not going to have a perfect solution for all of those personas (but maybe), but I think we can address 2 or 3 of those well - we just need to decide who is most important to address well. I think that should be the most important thing to decide. I am not sure if there are UX-experts in our dev@ community (Michael maybe you feel UX-strong enough D:), but it would be great to think about those personas when designing the "Community" experience. J. On Wed, Dec 20, 2023 at 9:04 PM Kaxil Naik <kaxiln...@gmail.com> wrote: > Separating it into 2 columns: 1) Dev 2) Users -- makes sense to me > > On Thu, 21 Dec 2023 at 01:30, Michael Robinson > <michael.robin...@astronomer.io.invalid> wrote: > > > Hello dev list, > > > > The excellent website landing pages have been instrumental in the wide > > adoption of Airflow. The fact that they’ve helped so many users get > started > > with Airflow while going without significant upgrades for years speaks to > > how well-designed they are. At the same time, it’s a massive > understatement > > to say that the community has changed since the landing pages were > > launched, and some of them could use updating to represent the community > as > > it is today and meet users’ and contributors’ current needs. > > > > For example, since the website was launched 3 years ago, Slack has become > > the community’s platform of choice. There are over 35k users and > > contributors there. > > > > As Jarek has noted <https://github.com/apache/airflow-site/pull/911>, > > Slack is ephemeral and user-first (but it seems safe to assume that most > > project contributors are on there, too). Also, as is appropriate for an > ASF > > project, the dev list continues to play a crucial role in hosting > > discussions and relaying announcements, etc. It’s still the primary > > vehicle/forum for asynchronous communication among contributors. > > > > But it seems safe to say that Slack is the primary forum for new users of > > Airflow. Currently, the Community page < > > https://airflow.apache.org/community/> prioritizes the dev list and > hides > > the Slack link down the page in the “Ask a Question” section by default. > > But it seems reasonable to assume that what most (not to say all) first > > visitors to the site are looking for on that page is a link to Slack. > > > > IMO, in light of the important communications and discussions on the dev > > list, we shouldn’t minimize it, but we should also make onboarding as > > frictionless as possible for users and devs alike. So what to do? > > > > I’ve opened a PR <https://github.com/apache/airflow-site/pull/911> to > > reorganize the page, and I’m hoping to start a discussion here about how > to > > proceed. Thanks, Jarek, for your comment and for suggesting we move the > > discussion to the list. > > > > Some ideas (see the PR for more details): > > > > Put Slack at the top of the page with the dev list just below it > > Use columns to devote half the page to contributor-centric resources and > > half to user-centric resources > > > > What do you think? > > > > Thank you, > > Michael > > > > >
