Glad to hear there is excitement about bringing this to life! Barring any significant feedback, we hope to bring this to a vote later in the week, so please chime in if you have insights to offer.
On Fri, Feb 26, 2021 at 7:21 PM Leah Cole <colel...@google.com> wrote: > Woooooo love to hear it! And +1 to the yielding a better experience for > everyone! > > On Fri, Feb 26, 2021 at 1:17 PM Ryan Hamilton <ryan.hamil...@astronomer.io> > wrote: > >> Thank you for the input Leah! I very much share your concern. >> Accessibility is a constant lens that I strive to always assess my own and >> my peers’ work through. I’ve always believed that prioritizing >> accessibility always yields a better experience for all users, not just the >> ones who need it. >> >> >> As we undertake the proposed design process and yield a new design >> system, it will certainly be an important factor. In producing these themes >> and reusable components, we hope to build these concerns in by default so >> we aren’t reliant on every individual contributor to keep the experience up >> to par. >> >> >> We hadn’t ran the demo through Lighthouse yet, but I just deployed a few >> quick edits and if you re-test, you should see that 79 is now 100! :) >> >> On Fri, Feb 26, 2021 at 2:39 PM Leah Cole <colel...@google.com> wrote: >> >>> At first glance to someone who hasn't touched front end in years, this >>> looks so thoughtful and detailed! And it looks pretty when I tried it out >>> :) >>> >>> One concern I have though is ensuring that accessibility is incorporated >>> as part of such a plan as well - I ran the lighthouse accessibility >>> report <https://developers.google.com/web/tools/lighthouse> on the demo >>> site and it got a 79/100, which is not bad, but it would be great to see >>> that check and its equivalent in other browsers be 100%. If others in the >>> community have other accessibility checkers they use as well, please send >>> them along because I'm by no means an expert! :) >>> >>> On Thu, Feb 25, 2021 at 12:20 PM Xinbin Huang <bin.huan...@gmail.com> >>> wrote: >>> >>>> I am already loving this UI! The change from the dropdown list to >>>> switching tabs makes it a lot more natural to lookup information in the UI. >>>> >>>> Thanks for the amazing work! Ryan and Brent. >>>> >>>> Best >>>> Bin >>>> >>>> On Thu, Feb 25, 2021 at 8:40 AM Vikram Koka >>>> <vik...@astronomer.io.invalid> wrote: >>>> >>>>> I love the breadth of your thinking through the problem and the >>>>> incremental approach which can be adapted based on feedback. >>>>> >>>>> Ryan and Brent, excellent work on this and really looking forward to >>>>> seeing this happen! >>>>> >>>>> Best regards, >>>>> Vikram >>>>> >>>>> >>>>> On Thu, Feb 25, 2021 at 4:31 AM Kaxil Naik <kaxiln...@gmail.com> >>>>> wrote: >>>>> >>>>>> This is awesome. I can already see Airflow users loving this UI. >>>>>> >>>>>> The Proposed Process in the AIP looks sound too. >>>>>> >>>>>> I have cross-posed this email to #sig-ui channel on Airflow Slack >>>>>> workspace too: >>>>>> https://apache-airflow.slack.com/archives/CMLE0UZEG/p1614255950000300 >>>>>> >>>>>> Well done -- Ryan and Brent. >>>>>> >>>>>> Regards, >>>>>> Kaxil >>>>>> >>>>>> On Thu, Feb 25, 2021 at 10:21 AM Sumit Maheshwari < >>>>>> sumeet.ma...@gmail.com> wrote: >>>>>> >>>>>>> Wow, the new demo UI is super slick and awesome. Great work Ryan and >>>>>>> Brent. 👏 >>>>>>> >>>>>>> On Thu, Feb 25, 2021 at 2:59 PM Jarek Potiuk <ja...@potiuk.com> >>>>>>> wrote: >>>>>>> >>>>>>>> For whatever reason there was an ".invalid" added to your address >>>>>>>> in reply, so let me just resend it :) >>>>>>>> >>>>>>>> On Thu, Feb 25, 2021 at 10:28 AM Jarek Potiuk <ja...@potiuk.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Great description. I have not had time to read it in detail - >>>>>>>>> (added to weekend reading list :) ). But it looks great and it's >>>>>>>>> clear you >>>>>>>>> put enormous effort into that. The technology stack choice, tooling, >>>>>>>>> test >>>>>>>>> support, architecture all look very sound in the proposal at the first >>>>>>>>> glance. >>>>>>>>> >>>>>>>>> Just a personal comment - It's a pity I will not have a lot of >>>>>>>>> time to contribute to it :(. React has gone a long way and matured a >>>>>>>>> lot >>>>>>>>> since we pioneered it in Polidea (we were rather deeply vested in >>>>>>>>> React >>>>>>>>> Native for mobile Apps). You can see my talk from 2015 at Mobile >>>>>>>>> Warsaw >>>>>>>>> from early days of it: https://www.youtube.com/watch?v=a3dz3OF81EE >>>>>>>>> - it was already good then, but it is a fully matured ecosystem now, >>>>>>>>> and a >>>>>>>>> great choice as a technology. >>>>>>>>> >>>>>>>>> Great piece of AIP Ryan and Brent. >>>>>>>>> >>>>>>>>> This will be a huge effort to complete, but I am 100% sure it's >>>>>>>>> worth it. >>>>>>>>> >>>>>>>>> J. >>>>>>>>> >>>>>>>>> On Wed, Feb 24, 2021 at 5:02 PM Ryan Hamilton >>>>>>>>> <ryan.hamil...@astronomer.io.invalid> wrote: >>>>>>>>> >>>>>>>>>> Team, >>>>>>>>>> >>>>>>>>>> We just created “AIP-38 Modern Web Application”' on Confluence >>>>>>>>>> and would very much appreciate feedback and suggestions from the >>>>>>>>>> community. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-38+Modern+Web+Application >>>>>>>>>> >>>>>>>>>> Building on the momentum of the release of 2.0 and the interest >>>>>>>>>> generated by the UI refresh delivered by it, we feel the time is >>>>>>>>>> right to >>>>>>>>>> begin the journey in making (and keeping) Airflow’s web application >>>>>>>>>> a truly >>>>>>>>>> modern one. We outline our motivations in detail within the AIP, but >>>>>>>>>> ultimately we strive to deliver a world-class user experience that >>>>>>>>>> strengthens Airflow’s position as the leader for data orchestration. >>>>>>>>>> >>>>>>>>>> The AIP consists of two primary sections: Technology and Information >>>>>>>>>> Architecture & Design. While the former has a fairly >>>>>>>>>> straightforward specification of technology and a proof of concept, >>>>>>>>>> the >>>>>>>>>> latter may feel a bit unorthodox as far as Airflow AIPs go. We are >>>>>>>>>> confident that the process that we’ve proposed to support it will >>>>>>>>>> fully >>>>>>>>>> utilize the best design practices that will yield an evolved and >>>>>>>>>> elevated >>>>>>>>>> experience for Airflow’s users. >>>>>>>>>> >>>>>>>>>> We’re cognizant of the significant amount of effort that this >>>>>>>>>> endeavour will require, and the ultimate impact that it will have on >>>>>>>>>> the >>>>>>>>>> future of Airflow. We believe that the proposed community-supported >>>>>>>>>> design >>>>>>>>>> process, and the introduction path with continual feedback loops will >>>>>>>>>> ensure that the end result fully delivers on the needs of Airflow’s >>>>>>>>>> diverse >>>>>>>>>> community of users. >>>>>>>>>> >>>>>>>>>> Any feedback, suggestions, and comments would be greatly >>>>>>>>>> appreciated. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Ryan Hamilton and Brent Bovenzi >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> +48 660 796 129 <+48%20660%20796%20129> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> +48 660 796 129 <+48%20660%20796%20129> >>>>>>>> >>>>>>> >>> >>> -- >>> >>> Leah Cole (she/her) | Developer Programs Engineer | colel...@google.com >>> | (925) 257-2112 >>> *I'm working weird hours during this pandemic and am sometimes a bit >>> slower to respond to PRs/CLs than normal. Please feel free to send me a >>> gentle ping for a status update if my slowness is blocking you and I'll do >>> my best to give you an ETA. * >>> >>> > > -- > > Leah Cole (she/her) | Developer Programs Engineer | colel...@google.com | > (925) > 257-2112 > *I'm working weird hours during this pandemic and am sometimes a bit > slower to respond to PRs/CLs than normal. Please feel free to send me a > gentle ping for a status update if my slowness is blocking you and I'll do > my best to give you an ETA. * > >
