You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Mohan, Deepthi" <md...@amazon.com.INVALID> on 2023/02/21 00:13:02 UTC
Proposal to improve the Apache Flink website
Hi,
I am a product manager for Kinesis Data Analytics, AWS’s managed service for Apache Flink. I’m creating this thread to gauge community interest in redesigning the Flink website: https://flink.apache.org/.
A few of our customers have provided feedback that the Apache Flink website looks dated. One customer claimed that the website looks “unwelcoming” and lacks useful graphics and colors. Another said it looks “like a wiki page thrown together by developers.” Customers also point out other related Apache project websites: https://spark.apache.org/ and https://kafka.apache.org/ as having “modern” user design. Many were surprised to hear that Flink has been a top-5 Apache project for several years now.
As https://flink.apache.org/ is likely the first page someone new to Flink encounters, it will be helpful to modernize the look and feel of the website. Given the growing interest in Flink, we have an opportunity to make content and features visible and easily accessible to customers. I’d like to learn if this is an idea we should pursue. I can create a FLIP if there is interest.
Thanks,
Deepthi Mohan
Re: Proposal to improve the Apache Flink website
Posted by Shammon FY <zj...@gmail.com>.
Hi
+1 too for this proposal
Compared with the beginning, Flink has good applications in many directions
now. The new website can give users better guidance for
streaming/batch/olap/ML and so on. Looking forward to the new website :)
Best,
Shammon
On Tue, Feb 21, 2023 at 2:24 PM Gyula Fóra <gy...@gmail.com> wrote:
> Hey!
>
> +1
>
> The Flink website could indeed use some love both design and content-wise.
> Thank you for starting this effort!
>
> I think a combination of approaches I) and II) could work well. Given that
> this is a highly subjective area we could have a small kickoff /
> brainstorming session with a few interested people. Then you could prepare
> a small POC of the new design as a FLIP.
>
> Cheers
> Gyula
>
> On Tue, 21 Feb 2023 at 03:30, Mohan, Deepthi <md...@amazon.com.invalid>
> wrote:
>
> > Hi Jing,
> >
> > I am proposing a redesign of the Apache Flink website (NOT a simpler way
> > to use Flink with Zeppelin or other technical solution). In general, the
> > feedback we're received from customers is that the content on the Flink
> > website is useful but is just not presented in an approachable way. For
> > example, website redesign could involve existing content structured in a
> > simpler way for new Flink users to understand and/or adding new content
> > that tells technical decision makers how using Flink would solve their
> use
> > cases.
> >
> > I agree that we would need UX/UI designers to help with content
> > restructuring, and potentially run usability studies with customers
> before
> > we implement a redesign. There are multiple ways we could approach this
> > FLIP:
> > (i) We could gather a small working committee who can discuss and set the
> > direction for a website redesign. If there are folks in the community who
> > have UX experience, they would be excellent candidates for this
> committee.
> > Interested engineers with website development experience could help
> > implement these changes.
> > (ii) I could take a stab at an initial redesign with the help of Amazon
> UX
> > designers who are interested to contribute and willing to help and bring
> it
> > up to the community for feedback and discussion.
> > (iii) We could outsource to a third party to design and implement these
> > changes (least favored)
> > And I'm sure there are other alternative approaches as well.
> >
> > However, before we jump to solutioning, I'd love to get feedback on if
> > this is something the community thinks is important to pursue.
> >
> > Thanks,
> > Deepthi
> >
> > On 2/20/23, 6:07 PM, "yuxia" <lu...@alumni.sjtu.edu.cn> wrote:
> >
> > CAUTION: This email originated from outside of the organization. Do
> > not click links or open attachments unless you can confirm the sender and
> > know the content is safe.
> >
> >
> >
> > Hi, Deepthi.
> > Thanks for bring it up. I'm looking forward to seeing what a “modern”
> > user design will look like for Flink.
> >
> > Best regards,
> > Yuxia
> >
> > ----- 原始邮件 -----
> > 发件人: "Jing Ge" <ji...@ververica.com.INVALID>
> > 收件人: "dev" <de...@flink.apache.org>
> > 发送时间: 星期二, 2023年 2 月 21日 上午 8:33:37
> > 主题: Re: Proposal to improve the Apache Flink website
> >
> > Hi Deepthi,
> >
> > Welcome to the Flink community. Thanks for the proposal. Commonly
> > speaking,
> > anything that could make Flink more attractive is welcome. I was
> > wondering
> > what your FLIP will look like. Are you going to propose a modern
> UX/UI
> > design via e.g. Zeplin which could be turned into a technical
> solution
> > that
> > front end developers can work with? This will be typically done by
> > UX/UI
> > designers, afaik. You mentioned your role as a product manager. Or,
> > will
> > you propose a restructure of the Flink websites' content and then
> find
> > the UX/UI designer to work on the new design? I am a little bit
> > confused.
> >
> > Best regards,
> > Jing
> >
> > On Tue, Feb 21, 2023 at 1:13 AM Mohan, Deepthi
> > <md...@amazon.com.invalid>
> > wrote:
> >
> > > Hi,
> > >
> > > I am a product manager for Kinesis Data Analytics, AWS’s managed
> > service
> > > for Apache Flink. I’m creating this thread to gauge community
> > interest in
> > > redesigning the Flink website: https://flink.apache.org/.
> > > A few of our customers have provided feedback that the Apache Flink
> > > website looks dated. One customer claimed that the website looks
> > > “unwelcoming” and lacks useful graphics and colors. Another said it
> > looks
> > > “like a wiki page thrown together by developers.” Customers also
> > point out
> > > other related Apache project websites: https://spark.apache.org/
> and
> > > https://kafka.apache.org/ as having “modern” user design. Many
> were
> > > surprised to hear that Flink has been a top-5 Apache project for
> > several
> > > years now.
> > > As https://flink.apache.org/ is likely the first page someone new
> to
> > > Flink encounters, it will be helpful to modernize the look and feel
> > of the
> > > website. Given the growing interest in Flink, we have an
> opportunity
> > to
> > > make content and features visible and easily accessible to
> > customers. I’d
> > > like to learn if this is an idea we should pursue. I can create a
> > FLIP if
> > > there is interest.
> > > Thanks,
> > > Deepthi Mohan
> > >
> >
> >
>
Re: Proposal to improve the Apache Flink website
Posted by Gyula Fóra <gy...@gmail.com>.
Hey!
+1
The Flink website could indeed use some love both design and content-wise.
Thank you for starting this effort!
I think a combination of approaches I) and II) could work well. Given that
this is a highly subjective area we could have a small kickoff /
brainstorming session with a few interested people. Then you could prepare
a small POC of the new design as a FLIP.
Cheers
Gyula
On Tue, 21 Feb 2023 at 03:30, Mohan, Deepthi <md...@amazon.com.invalid>
wrote:
> Hi Jing,
>
> I am proposing a redesign of the Apache Flink website (NOT a simpler way
> to use Flink with Zeppelin or other technical solution). In general, the
> feedback we're received from customers is that the content on the Flink
> website is useful but is just not presented in an approachable way. For
> example, website redesign could involve existing content structured in a
> simpler way for new Flink users to understand and/or adding new content
> that tells technical decision makers how using Flink would solve their use
> cases.
>
> I agree that we would need UX/UI designers to help with content
> restructuring, and potentially run usability studies with customers before
> we implement a redesign. There are multiple ways we could approach this
> FLIP:
> (i) We could gather a small working committee who can discuss and set the
> direction for a website redesign. If there are folks in the community who
> have UX experience, they would be excellent candidates for this committee.
> Interested engineers with website development experience could help
> implement these changes.
> (ii) I could take a stab at an initial redesign with the help of Amazon UX
> designers who are interested to contribute and willing to help and bring it
> up to the community for feedback and discussion.
> (iii) We could outsource to a third party to design and implement these
> changes (least favored)
> And I'm sure there are other alternative approaches as well.
>
> However, before we jump to solutioning, I'd love to get feedback on if
> this is something the community thinks is important to pursue.
>
> Thanks,
> Deepthi
>
> On 2/20/23, 6:07 PM, "yuxia" <lu...@alumni.sjtu.edu.cn> wrote:
>
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you can confirm the sender and
> know the content is safe.
>
>
>
> Hi, Deepthi.
> Thanks for bring it up. I'm looking forward to seeing what a “modern”
> user design will look like for Flink.
>
> Best regards,
> Yuxia
>
> ----- 原始邮件 -----
> 发件人: "Jing Ge" <ji...@ververica.com.INVALID>
> 收件人: "dev" <de...@flink.apache.org>
> 发送时间: 星期二, 2023年 2 月 21日 上午 8:33:37
> 主题: Re: Proposal to improve the Apache Flink website
>
> Hi Deepthi,
>
> Welcome to the Flink community. Thanks for the proposal. Commonly
> speaking,
> anything that could make Flink more attractive is welcome. I was
> wondering
> what your FLIP will look like. Are you going to propose a modern UX/UI
> design via e.g. Zeplin which could be turned into a technical solution
> that
> front end developers can work with? This will be typically done by
> UX/UI
> designers, afaik. You mentioned your role as a product manager. Or,
> will
> you propose a restructure of the Flink websites' content and then find
> the UX/UI designer to work on the new design? I am a little bit
> confused.
>
> Best regards,
> Jing
>
> On Tue, Feb 21, 2023 at 1:13 AM Mohan, Deepthi
> <md...@amazon.com.invalid>
> wrote:
>
> > Hi,
> >
> > I am a product manager for Kinesis Data Analytics, AWS’s managed
> service
> > for Apache Flink. I’m creating this thread to gauge community
> interest in
> > redesigning the Flink website: https://flink.apache.org/.
> > A few of our customers have provided feedback that the Apache Flink
> > website looks dated. One customer claimed that the website looks
> > “unwelcoming” and lacks useful graphics and colors. Another said it
> looks
> > “like a wiki page thrown together by developers.” Customers also
> point out
> > other related Apache project websites: https://spark.apache.org/ and
> > https://kafka.apache.org/ as having “modern” user design. Many were
> > surprised to hear that Flink has been a top-5 Apache project for
> several
> > years now.
> > As https://flink.apache.org/ is likely the first page someone new to
> > Flink encounters, it will be helpful to modernize the look and feel
> of the
> > website. Given the growing interest in Flink, we have an opportunity
> to
> > make content and features visible and easily accessible to
> customers. I’d
> > like to learn if this is an idea we should pursue. I can create a
> FLIP if
> > there is interest.
> > Thanks,
> > Deepthi Mohan
> >
>
>
Re: Proposal to improve the Apache Flink website
Posted by "Mohan, Deepthi" <md...@amazon.com.INVALID>.
Hi Jing,
I am proposing a redesign of the Apache Flink website (NOT a simpler way to use Flink with Zeppelin or other technical solution). In general, the feedback we're received from customers is that the content on the Flink website is useful but is just not presented in an approachable way. For example, website redesign could involve existing content structured in a simpler way for new Flink users to understand and/or adding new content that tells technical decision makers how using Flink would solve their use cases.
I agree that we would need UX/UI designers to help with content restructuring, and potentially run usability studies with customers before we implement a redesign. There are multiple ways we could approach this FLIP:
(i) We could gather a small working committee who can discuss and set the direction for a website redesign. If there are folks in the community who have UX experience, they would be excellent candidates for this committee. Interested engineers with website development experience could help implement these changes.
(ii) I could take a stab at an initial redesign with the help of Amazon UX designers who are interested to contribute and willing to help and bring it up to the community for feedback and discussion.
(iii) We could outsource to a third party to design and implement these changes (least favored)
And I'm sure there are other alternative approaches as well.
However, before we jump to solutioning, I'd love to get feedback on if this is something the community thinks is important to pursue.
Thanks,
Deepthi
On 2/20/23, 6:07 PM, "yuxia" <lu...@alumni.sjtu.edu.cn> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Hi, Deepthi.
Thanks for bring it up. I'm looking forward to seeing what a “modern” user design will look like for Flink.
Best regards,
Yuxia
----- 原始邮件 -----
发件人: "Jing Ge" <ji...@ververica.com.INVALID>
收件人: "dev" <de...@flink.apache.org>
发送时间: 星期二, 2023年 2 月 21日 上午 8:33:37
主题: Re: Proposal to improve the Apache Flink website
Hi Deepthi,
Welcome to the Flink community. Thanks for the proposal. Commonly speaking,
anything that could make Flink more attractive is welcome. I was wondering
what your FLIP will look like. Are you going to propose a modern UX/UI
design via e.g. Zeplin which could be turned into a technical solution that
front end developers can work with? This will be typically done by UX/UI
designers, afaik. You mentioned your role as a product manager. Or, will
you propose a restructure of the Flink websites' content and then find
the UX/UI designer to work on the new design? I am a little bit confused.
Best regards,
Jing
On Tue, Feb 21, 2023 at 1:13 AM Mohan, Deepthi <md...@amazon.com.invalid>
wrote:
> Hi,
>
> I am a product manager for Kinesis Data Analytics, AWS’s managed service
> for Apache Flink. I’m creating this thread to gauge community interest in
> redesigning the Flink website: https://flink.apache.org/.
> A few of our customers have provided feedback that the Apache Flink
> website looks dated. One customer claimed that the website looks
> “unwelcoming” and lacks useful graphics and colors. Another said it looks
> “like a wiki page thrown together by developers.” Customers also point out
> other related Apache project websites: https://spark.apache.org/ and
> https://kafka.apache.org/ as having “modern” user design. Many were
> surprised to hear that Flink has been a top-5 Apache project for several
> years now.
> As https://flink.apache.org/ is likely the first page someone new to
> Flink encounters, it will be helpful to modernize the look and feel of the
> website. Given the growing interest in Flink, we have an opportunity to
> make content and features visible and easily accessible to customers. I’d
> like to learn if this is an idea we should pursue. I can create a FLIP if
> there is interest.
> Thanks,
> Deepthi Mohan
>
Re: Proposal to improve the Apache Flink website
Posted by yuxia <lu...@alumni.sjtu.edu.cn>.
Hi, Deepthi.
Thanks for bring it up. I'm looking forward to seeing what a “modern” user design will look like for Flink.
Best regards,
Yuxia
----- 原始邮件 -----
发件人: "Jing Ge" <ji...@ververica.com.INVALID>
收件人: "dev" <de...@flink.apache.org>
发送时间: 星期二, 2023年 2 月 21日 上午 8:33:37
主题: Re: Proposal to improve the Apache Flink website
Hi Deepthi,
Welcome to the Flink community. Thanks for the proposal. Commonly speaking,
anything that could make Flink more attractive is welcome. I was wondering
what your FLIP will look like. Are you going to propose a modern UX/UI
design via e.g. Zeplin which could be turned into a technical solution that
front end developers can work with? This will be typically done by UX/UI
designers, afaik. You mentioned your role as a product manager. Or, will
you propose a restructure of the Flink websites' content and then find
the UX/UI designer to work on the new design? I am a little bit confused.
Best regards,
Jing
On Tue, Feb 21, 2023 at 1:13 AM Mohan, Deepthi <md...@amazon.com.invalid>
wrote:
> Hi,
>
> I am a product manager for Kinesis Data Analytics, AWS’s managed service
> for Apache Flink. I’m creating this thread to gauge community interest in
> redesigning the Flink website: https://flink.apache.org/.
> A few of our customers have provided feedback that the Apache Flink
> website looks dated. One customer claimed that the website looks
> “unwelcoming” and lacks useful graphics and colors. Another said it looks
> “like a wiki page thrown together by developers.” Customers also point out
> other related Apache project websites: https://spark.apache.org/ and
> https://kafka.apache.org/ as having “modern” user design. Many were
> surprised to hear that Flink has been a top-5 Apache project for several
> years now.
> As https://flink.apache.org/ is likely the first page someone new to
> Flink encounters, it will be helpful to modernize the look and feel of the
> website. Given the growing interest in Flink, we have an opportunity to
> make content and features visible and easily accessible to customers. I’d
> like to learn if this is an idea we should pursue. I can create a FLIP if
> there is interest.
> Thanks,
> Deepthi Mohan
>
Re: Proposal to improve the Apache Flink website
Posted by Jing Ge <ji...@ververica.com.INVALID>.
Hi Deepthi,
Welcome to the Flink community. Thanks for the proposal. Commonly speaking,
anything that could make Flink more attractive is welcome. I was wondering
what your FLIP will look like. Are you going to propose a modern UX/UI
design via e.g. Zeplin which could be turned into a technical solution that
front end developers can work with? This will be typically done by UX/UI
designers, afaik. You mentioned your role as a product manager. Or, will
you propose a restructure of the Flink websites' content and then find
the UX/UI designer to work on the new design? I am a little bit confused.
Best regards,
Jing
On Tue, Feb 21, 2023 at 1:13 AM Mohan, Deepthi <md...@amazon.com.invalid>
wrote:
> Hi,
>
> I am a product manager for Kinesis Data Analytics, AWS’s managed service
> for Apache Flink. I’m creating this thread to gauge community interest in
> redesigning the Flink website: https://flink.apache.org/.
> A few of our customers have provided feedback that the Apache Flink
> website looks dated. One customer claimed that the website looks
> “unwelcoming” and lacks useful graphics and colors. Another said it looks
> “like a wiki page thrown together by developers.” Customers also point out
> other related Apache project websites: https://spark.apache.org/ and
> https://kafka.apache.org/ as having “modern” user design. Many were
> surprised to hear that Flink has been a top-5 Apache project for several
> years now.
> As https://flink.apache.org/ is likely the first page someone new to
> Flink encounters, it will be helpful to modernize the look and feel of the
> website. Given the growing interest in Flink, we have an opportunity to
> make content and features visible and easily accessible to customers. I’d
> like to learn if this is an idea we should pursue. I can create a FLIP if
> there is interest.
> Thanks,
> Deepthi Mohan
>
Re: Proposal to improve the Apache Flink website
Posted by Martijn Visser <mv...@confluent.io.INVALID>.
Hi all,
I would +1 an overall redesign, but I would like to ask to wait until the
migration to Hugo has been completed [1]. That would make the themes and
technology between the project website and the documentation the same and
provide a foundation to continue for further improvements.
Best regards,
Martijn
[1] https://github.com/apache/flink-web/pull/597
On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
> Hey!
>
> +1 for the proposal, the first page of Flink is more like a tutorial
> document for developers compared to the other top apache projects. Looking
> forward to a more attractive Flink website.
>
> Best regards,
> Shuo
>
> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi <mdeepth@amazon.com.invalid
> >
> wrote:
>
> > Hi,
> >
> > I am a product manager for Kinesis Data Analytics, AWS’s managed service
> > for Apache Flink. I’m creating this thread to gauge community interest in
> > redesigning the Flink website: https://flink.apache.org/.
> > A few of our customers have provided feedback that the Apache Flink
> > website looks dated. One customer claimed that the website looks
> > “unwelcoming” and lacks useful graphics and colors. Another said it looks
> > “like a wiki page thrown together by developers.” Customers also point
> out
> > other related Apache project websites: https://spark.apache.org/ and
> > https://kafka.apache.org/ as having “modern” user design. Many were
> > surprised to hear that Flink has been a top-5 Apache project for several
> > years now.
> > As https://flink.apache.org/ is likely the first page someone new to
> > Flink encounters, it will be helpful to modernize the look and feel of
> the
> > website. Given the growing interest in Flink, we have an opportunity to
> > make content and features visible and easily accessible to customers. I’d
> > like to learn if this is an idea we should pursue. I can create a FLIP if
> > there is interest.
> > Thanks,
> > Deepthi Mohan
> >
>
Re: Proposal to improve the Apache Flink website
Posted by Yun Tang <my...@live.com>.
As a developer, I visited the docs website [1] much much more often than the official main page website [2], and I think current docs website still looks a bit better than spark's [3] which did not change in the past ten years if my memory serves me correctly.
Until Deepthi raised this proposal, I just realized that current Flink's main page looks a bit outdated compared to other active top Apache projects. I think Maximilian's preferring to simple and elegant design is well revealed in the doc website, which might be welcome among software engineers.
On the other hand, the main page website is the first entrance for everyone, not only developers, and I think a modern look would be better.
+1 for this proposal and look forward to the changes.
[1] https://nightlies.apache.org/flink/flink-docs-stable/
[2] https://flink.apache.org/
[3] https://spark.apache.org/docs/latest/
Best
Yun Tang
________________________________
From: Chesnay Schepler <ch...@apache.org>
Sent: Friday, February 24, 2023 2:20
To: dev@flink.apache.org <de...@flink.apache.org>; Maximilian Michels <mx...@apache.org>
Subject: Re: Proposal to improve the Apache Flink website
Maybe to expand on the comment from Max:
From a technical perspective the website and documentation are 2
entirely different things,
but from a users perspective could easily be perceived as being "the
website".
Again I feel like we lack a concrete list of issues; that would've
likely answered this question already.
On 23/02/2023 16:43, Maximilian Michels wrote:
> Is this targeting the landing page, the main website, or the entire
> website including the documentation?
>
> Compare the main page of Spark with its documentation:
> https://spark.apache.org/
> https://spark.apache.org/docs/latest/
>
> I like the consistency of the current Flink page, but it is obviously
> easier to change only the main page first and leave the documentation
> unchanged.
>
> -Max
>
> On Wed, Feb 22, 2023 at 3:07 AM Mohan, Deepthi
> <md...@amazon.com.invalid> wrote:
>> Thank you all for the feedback. Point taken about decoupling content/structure and design. As a first step, I can work with an AWS UX designer and come with a list of suggestions and wireframes. And while we aren't forming a committee yet, if anyone wants to collaborate, please reach out.
>>
>> On 2/21/23, 5:31 AM, "Chesnay Schepler" <ch...@apache.org> wrote:
>>
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>>
>>
>>
>> Max is raising some good points.
>>
>> Ultimately, you are free to propose changes; we don't categorically
>> reject changes to the website.
>>
>> On the flip-side, the proposed changes should also be as granular as
>> possible, because there's no real reason why changing the content
>> structure should be coupled to the design of the page or vice-versa.
>>
>> Please don't approach this as a "grand redesign" of the website where
>> we'll just a flip a switch eventually to go from old to new.
>>
>> Rather, break down the "problems with the website" into separate issue
>> that we can tackle one-by-one.
>> Because of that I'd also be against creating a "committee" at this time,
>> because that just makes it imo more likely that this will be handled as
>> an all-or-nothing/waterfall kind of thing.
>>
>> On 21/02/2023 11:31, Maximilian Michels wrote:
>> > -0 for a redesign. I might be the only one but I like the current
>> > simple design. I find it quite elegant. Apache projects do not tend to
>> > have fancy websites. That's ok. If you consider the AWS pages, they
>> > are far from being modern or beautiful.
>> >
>> > A redesign often is appealing but it can take a huge amount of time to
>> > get it right. This can mean the project is unable to focus on the main
>> > target of delivering great software and documentation.
>> >
>> > Some concerns:
>> > 1. Content regressions (content not being displayed properly, content
>> > and graphics not fitting anymore, code formatting breaking)
>> > 2. Higher entry barrier for committing (tooling / formatting becomes
>> > complicated)
>> > 3. Lack of focus on the content which needs work too (e.g. outdated
>> > information, lack of documentation of features)
>> >
>> > That said, I would support a redesign if we prevent regressions and
>> > build on standard tooling and best practices. I'm just not convinced
>> > (yet) that the pros outweigh the cons.
>> >
>> > -Max
>> >
>> > On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
>> >> Hi Deepthi,
>> >>
>> >> +1 for a redesign.
>> >>
>> >> I like the idea of setting up a committee/team that can produce some mock
>> >> ups and create a FLIP where the community can elect the best look and feel.
>> >> I very much look forward to seeing the results!
>> >>
>> >> Thanks,
>> >> Danny
>> >>
>> >>
>> >>
>> >> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
>> >>
>> >>> Hi Deepthi,
>> >>>
>> >>> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
>> >>> it is not Zeppelin.
>> >>>
>> >>> It is great to hear that Amazon UX/UI designers would contribute. There was
>> >>> a lack of front-end engineers in the past. Hopefully we could find enough
>> >>> front-end contributors for this big project.
>> >>>
>> >>> +1 looking forward to your proposal.
>> >>>
>> >>> Best regards,
>> >>> Jing
>> >>>
>> >>> [1] https://zeplin.io/
>> >>>
>> >>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
>> >>>
>> >>>> Hey!
>> >>>>
>> >>>> +1 for the proposal, the first page of Flink is more like a tutorial
>> >>>> document for developers compared to the other top apache projects.
>> >>> Looking
>> >>>> forward to a more attractive Flink website.
>> >>>>
>> >>>> Best regards,
>> >>>> Shuo
>> >>>>
>> >>>> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
>> >>> <mdeepth@amazon.com.invalid
>> >>>> wrote:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> I am a product manager for Kinesis Data Analytics, AWS’s managed
>> >>> service
>> >>>>> for Apache Flink. I’m creating this thread to gauge community interest
>> >>> in
>> >>>>> redesigning the Flink website: https://flink.apache.org/.
>> >>>>> A few of our customers have provided feedback that the Apache Flink
>> >>>>> website looks dated. One customer claimed that the website looks
>> >>>>> “unwelcoming” and lacks useful graphics and colors. Another said it
>> >>> looks
>> >>>>> “like a wiki page thrown together by developers.” Customers also point
>> >>>> out
>> >>>>> other related Apache project websites: https://spark.apache.org/ and
>> >>>>> https://kafka.apache.org/ as having “modern” user design. Many were
>> >>>>> surprised to hear that Flink has been a top-5 Apache project for
>> >>> several
>> >>>>> years now.
>> >>>>> As https://flink.apache.org/ is likely the first page someone new to
>> >>>>> Flink encounters, it will be helpful to modernize the look and feel of
>> >>>> the
>> >>>>> website. Given the growing interest in Flink, we have an opportunity to
>> >>>>> make content and features visible and easily accessible to customers.
>> >>> I’d
>> >>>>> like to learn if this is an idea we should pursue. I can create a FLIP
>> >>> if
>> >>>>> there is interest.
>> >>>>> Thanks,
>> >>>>> Deepthi Mohan
>> >>>>>
>>
>>
Re: Proposal to improve the Apache Flink website
Posted by Chesnay Schepler <ch...@apache.org>.
Maybe to expand on the comment from Max:
From a technical perspective the website and documentation are 2
entirely different things,
but from a users perspective could easily be perceived as being "the
website".
Again I feel like we lack a concrete list of issues; that would've
likely answered this question already.
On 23/02/2023 16:43, Maximilian Michels wrote:
> Is this targeting the landing page, the main website, or the entire
> website including the documentation?
>
> Compare the main page of Spark with its documentation:
> https://spark.apache.org/
> https://spark.apache.org/docs/latest/
>
> I like the consistency of the current Flink page, but it is obviously
> easier to change only the main page first and leave the documentation
> unchanged.
>
> -Max
>
> On Wed, Feb 22, 2023 at 3:07 AM Mohan, Deepthi
> <md...@amazon.com.invalid> wrote:
>> Thank you all for the feedback. Point taken about decoupling content/structure and design. As a first step, I can work with an AWS UX designer and come with a list of suggestions and wireframes. And while we aren't forming a committee yet, if anyone wants to collaborate, please reach out.
>>
>> On 2/21/23, 5:31 AM, "Chesnay Schepler" <ch...@apache.org> wrote:
>>
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>>
>>
>>
>> Max is raising some good points.
>>
>> Ultimately, you are free to propose changes; we don't categorically
>> reject changes to the website.
>>
>> On the flip-side, the proposed changes should also be as granular as
>> possible, because there's no real reason why changing the content
>> structure should be coupled to the design of the page or vice-versa.
>>
>> Please don't approach this as a "grand redesign" of the website where
>> we'll just a flip a switch eventually to go from old to new.
>>
>> Rather, break down the "problems with the website" into separate issue
>> that we can tackle one-by-one.
>> Because of that I'd also be against creating a "committee" at this time,
>> because that just makes it imo more likely that this will be handled as
>> an all-or-nothing/waterfall kind of thing.
>>
>> On 21/02/2023 11:31, Maximilian Michels wrote:
>> > -0 for a redesign. I might be the only one but I like the current
>> > simple design. I find it quite elegant. Apache projects do not tend to
>> > have fancy websites. That's ok. If you consider the AWS pages, they
>> > are far from being modern or beautiful.
>> >
>> > A redesign often is appealing but it can take a huge amount of time to
>> > get it right. This can mean the project is unable to focus on the main
>> > target of delivering great software and documentation.
>> >
>> > Some concerns:
>> > 1. Content regressions (content not being displayed properly, content
>> > and graphics not fitting anymore, code formatting breaking)
>> > 2. Higher entry barrier for committing (tooling / formatting becomes
>> > complicated)
>> > 3. Lack of focus on the content which needs work too (e.g. outdated
>> > information, lack of documentation of features)
>> >
>> > That said, I would support a redesign if we prevent regressions and
>> > build on standard tooling and best practices. I'm just not convinced
>> > (yet) that the pros outweigh the cons.
>> >
>> > -Max
>> >
>> > On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
>> >> Hi Deepthi,
>> >>
>> >> +1 for a redesign.
>> >>
>> >> I like the idea of setting up a committee/team that can produce some mock
>> >> ups and create a FLIP where the community can elect the best look and feel.
>> >> I very much look forward to seeing the results!
>> >>
>> >> Thanks,
>> >> Danny
>> >>
>> >>
>> >>
>> >> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
>> >>
>> >>> Hi Deepthi,
>> >>>
>> >>> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
>> >>> it is not Zeppelin.
>> >>>
>> >>> It is great to hear that Amazon UX/UI designers would contribute. There was
>> >>> a lack of front-end engineers in the past. Hopefully we could find enough
>> >>> front-end contributors for this big project.
>> >>>
>> >>> +1 looking forward to your proposal.
>> >>>
>> >>> Best regards,
>> >>> Jing
>> >>>
>> >>> [1] https://zeplin.io/
>> >>>
>> >>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
>> >>>
>> >>>> Hey!
>> >>>>
>> >>>> +1 for the proposal, the first page of Flink is more like a tutorial
>> >>>> document for developers compared to the other top apache projects.
>> >>> Looking
>> >>>> forward to a more attractive Flink website.
>> >>>>
>> >>>> Best regards,
>> >>>> Shuo
>> >>>>
>> >>>> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
>> >>> <mdeepth@amazon.com.invalid
>> >>>> wrote:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> I am a product manager for Kinesis Data Analytics, AWS’s managed
>> >>> service
>> >>>>> for Apache Flink. I’m creating this thread to gauge community interest
>> >>> in
>> >>>>> redesigning the Flink website: https://flink.apache.org/.
>> >>>>> A few of our customers have provided feedback that the Apache Flink
>> >>>>> website looks dated. One customer claimed that the website looks
>> >>>>> “unwelcoming” and lacks useful graphics and colors. Another said it
>> >>> looks
>> >>>>> “like a wiki page thrown together by developers.” Customers also point
>> >>>> out
>> >>>>> other related Apache project websites: https://spark.apache.org/ and
>> >>>>> https://kafka.apache.org/ as having “modern” user design. Many were
>> >>>>> surprised to hear that Flink has been a top-5 Apache project for
>> >>> several
>> >>>>> years now.
>> >>>>> As https://flink.apache.org/ is likely the first page someone new to
>> >>>>> Flink encounters, it will be helpful to modernize the look and feel of
>> >>>> the
>> >>>>> website. Given the growing interest in Flink, we have an opportunity to
>> >>>>> make content and features visible and easily accessible to customers.
>> >>> I’d
>> >>>>> like to learn if this is an idea we should pursue. I can create a FLIP
>> >>> if
>> >>>>> there is interest.
>> >>>>> Thanks,
>> >>>>> Deepthi Mohan
>> >>>>>
>>
>>
Re: Proposal to improve the Apache Flink website
Posted by Maximilian Michels <mx...@apache.org>.
Is this targeting the landing page, the main website, or the entire
website including the documentation?
Compare the main page of Spark with its documentation:
https://spark.apache.org/
https://spark.apache.org/docs/latest/
I like the consistency of the current Flink page, but it is obviously
easier to change only the main page first and leave the documentation
unchanged.
-Max
On Wed, Feb 22, 2023 at 3:07 AM Mohan, Deepthi
<md...@amazon.com.invalid> wrote:
>
> Thank you all for the feedback. Point taken about decoupling content/structure and design. As a first step, I can work with an AWS UX designer and come with a list of suggestions and wireframes. And while we aren't forming a committee yet, if anyone wants to collaborate, please reach out.
>
> On 2/21/23, 5:31 AM, "Chesnay Schepler" <ch...@apache.org> wrote:
>
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> Max is raising some good points.
>
> Ultimately, you are free to propose changes; we don't categorically
> reject changes to the website.
>
> On the flip-side, the proposed changes should also be as granular as
> possible, because there's no real reason why changing the content
> structure should be coupled to the design of the page or vice-versa.
>
> Please don't approach this as a "grand redesign" of the website where
> we'll just a flip a switch eventually to go from old to new.
>
> Rather, break down the "problems with the website" into separate issue
> that we can tackle one-by-one.
> Because of that I'd also be against creating a "committee" at this time,
> because that just makes it imo more likely that this will be handled as
> an all-or-nothing/waterfall kind of thing.
>
> On 21/02/2023 11:31, Maximilian Michels wrote:
> > -0 for a redesign. I might be the only one but I like the current
> > simple design. I find it quite elegant. Apache projects do not tend to
> > have fancy websites. That's ok. If you consider the AWS pages, they
> > are far from being modern or beautiful.
> >
> > A redesign often is appealing but it can take a huge amount of time to
> > get it right. This can mean the project is unable to focus on the main
> > target of delivering great software and documentation.
> >
> > Some concerns:
> > 1. Content regressions (content not being displayed properly, content
> > and graphics not fitting anymore, code formatting breaking)
> > 2. Higher entry barrier for committing (tooling / formatting becomes
> > complicated)
> > 3. Lack of focus on the content which needs work too (e.g. outdated
> > information, lack of documentation of features)
> >
> > That said, I would support a redesign if we prevent regressions and
> > build on standard tooling and best practices. I'm just not convinced
> > (yet) that the pros outweigh the cons.
> >
> > -Max
> >
> > On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
> >> Hi Deepthi,
> >>
> >> +1 for a redesign.
> >>
> >> I like the idea of setting up a committee/team that can produce some mock
> >> ups and create a FLIP where the community can elect the best look and feel.
> >> I very much look forward to seeing the results!
> >>
> >> Thanks,
> >> Danny
> >>
> >>
> >>
> >> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
> >>
> >>> Hi Deepthi,
> >>>
> >>> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
> >>> it is not Zeppelin.
> >>>
> >>> It is great to hear that Amazon UX/UI designers would contribute. There was
> >>> a lack of front-end engineers in the past. Hopefully we could find enough
> >>> front-end contributors for this big project.
> >>>
> >>> +1 looking forward to your proposal.
> >>>
> >>> Best regards,
> >>> Jing
> >>>
> >>> [1] https://zeplin.io/
> >>>
> >>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
> >>>
> >>>> Hey!
> >>>>
> >>>> +1 for the proposal, the first page of Flink is more like a tutorial
> >>>> document for developers compared to the other top apache projects.
> >>> Looking
> >>>> forward to a more attractive Flink website.
> >>>>
> >>>> Best regards,
> >>>> Shuo
> >>>>
> >>>> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
> >>> <mdeepth@amazon.com.invalid
> >>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I am a product manager for Kinesis Data Analytics, AWS’s managed
> >>> service
> >>>>> for Apache Flink. I’m creating this thread to gauge community interest
> >>> in
> >>>>> redesigning the Flink website: https://flink.apache.org/.
> >>>>> A few of our customers have provided feedback that the Apache Flink
> >>>>> website looks dated. One customer claimed that the website looks
> >>>>> “unwelcoming” and lacks useful graphics and colors. Another said it
> >>> looks
> >>>>> “like a wiki page thrown together by developers.” Customers also point
> >>>> out
> >>>>> other related Apache project websites: https://spark.apache.org/ and
> >>>>> https://kafka.apache.org/ as having “modern” user design. Many were
> >>>>> surprised to hear that Flink has been a top-5 Apache project for
> >>> several
> >>>>> years now.
> >>>>> As https://flink.apache.org/ is likely the first page someone new to
> >>>>> Flink encounters, it will be helpful to modernize the look and feel of
> >>>> the
> >>>>> website. Given the growing interest in Flink, we have an opportunity to
> >>>>> make content and features visible and easily accessible to customers.
> >>> I’d
> >>>>> like to learn if this is an idea we should pursue. I can create a FLIP
> >>> if
> >>>>> there is interest.
> >>>>> Thanks,
> >>>>> Deepthi Mohan
> >>>>>
>
>
Re: Proposal to improve the Apache Flink website
Posted by "Mohan, Deepthi" <md...@amazon.com.INVALID>.
Thank you all for the feedback. Point taken about decoupling content/structure and design. As a first step, I can work with an AWS UX designer and come with a list of suggestions and wireframes. And while we aren't forming a committee yet, if anyone wants to collaborate, please reach out.
On 2/21/23, 5:31 AM, "Chesnay Schepler" <ch...@apache.org> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Max is raising some good points.
Ultimately, you are free to propose changes; we don't categorically
reject changes to the website.
On the flip-side, the proposed changes should also be as granular as
possible, because there's no real reason why changing the content
structure should be coupled to the design of the page or vice-versa.
Please don't approach this as a "grand redesign" of the website where
we'll just a flip a switch eventually to go from old to new.
Rather, break down the "problems with the website" into separate issue
that we can tackle one-by-one.
Because of that I'd also be against creating a "committee" at this time,
because that just makes it imo more likely that this will be handled as
an all-or-nothing/waterfall kind of thing.
On 21/02/2023 11:31, Maximilian Michels wrote:
> -0 for a redesign. I might be the only one but I like the current
> simple design. I find it quite elegant. Apache projects do not tend to
> have fancy websites. That's ok. If you consider the AWS pages, they
> are far from being modern or beautiful.
>
> A redesign often is appealing but it can take a huge amount of time to
> get it right. This can mean the project is unable to focus on the main
> target of delivering great software and documentation.
>
> Some concerns:
> 1. Content regressions (content not being displayed properly, content
> and graphics not fitting anymore, code formatting breaking)
> 2. Higher entry barrier for committing (tooling / formatting becomes
> complicated)
> 3. Lack of focus on the content which needs work too (e.g. outdated
> information, lack of documentation of features)
>
> That said, I would support a redesign if we prevent regressions and
> build on standard tooling and best practices. I'm just not convinced
> (yet) that the pros outweigh the cons.
>
> -Max
>
> On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
>> Hi Deepthi,
>>
>> +1 for a redesign.
>>
>> I like the idea of setting up a committee/team that can produce some mock
>> ups and create a FLIP where the community can elect the best look and feel.
>> I very much look forward to seeing the results!
>>
>> Thanks,
>> Danny
>>
>>
>>
>> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
>>
>>> Hi Deepthi,
>>>
>>> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
>>> it is not Zeppelin.
>>>
>>> It is great to hear that Amazon UX/UI designers would contribute. There was
>>> a lack of front-end engineers in the past. Hopefully we could find enough
>>> front-end contributors for this big project.
>>>
>>> +1 looking forward to your proposal.
>>>
>>> Best regards,
>>> Jing
>>>
>>> [1] https://zeplin.io/
>>>
>>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
>>>
>>>> Hey!
>>>>
>>>> +1 for the proposal, the first page of Flink is more like a tutorial
>>>> document for developers compared to the other top apache projects.
>>> Looking
>>>> forward to a more attractive Flink website.
>>>>
>>>> Best regards,
>>>> Shuo
>>>>
>>>> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
>>> <mdeepth@amazon.com.invalid
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am a product manager for Kinesis Data Analytics, AWS’s managed
>>> service
>>>>> for Apache Flink. I’m creating this thread to gauge community interest
>>> in
>>>>> redesigning the Flink website: https://flink.apache.org/.
>>>>> A few of our customers have provided feedback that the Apache Flink
>>>>> website looks dated. One customer claimed that the website looks
>>>>> “unwelcoming” and lacks useful graphics and colors. Another said it
>>> looks
>>>>> “like a wiki page thrown together by developers.” Customers also point
>>>> out
>>>>> other related Apache project websites: https://spark.apache.org/ and
>>>>> https://kafka.apache.org/ as having “modern” user design. Many were
>>>>> surprised to hear that Flink has been a top-5 Apache project for
>>> several
>>>>> years now.
>>>>> As https://flink.apache.org/ is likely the first page someone new to
>>>>> Flink encounters, it will be helpful to modernize the look and feel of
>>>> the
>>>>> website. Given the growing interest in Flink, we have an opportunity to
>>>>> make content and features visible and easily accessible to customers.
>>> I’d
>>>>> like to learn if this is an idea we should pursue. I can create a FLIP
>>> if
>>>>> there is interest.
>>>>> Thanks,
>>>>> Deepthi Mohan
>>>>>
Re: Proposal to improve the Apache Flink website
Posted by Chesnay Schepler <ch...@apache.org>.
Max is raising some good points.
Ultimately, you are free to propose changes; we don't categorically
reject changes to the website.
On the flip-side, the proposed changes should also be as granular as
possible, because there's no real reason why changing the content
structure should be coupled to the design of the page or vice-versa.
Please don't approach this as a "grand redesign" of the website where
we'll just a flip a switch eventually to go from old to new.
Rather, break down the "problems with the website" into separate issue
that we can tackle one-by-one.
Because of that I'd also be against creating a "committee" at this time,
because that just makes it imo more likely that this will be handled as
an all-or-nothing/waterfall kind of thing.
On 21/02/2023 11:31, Maximilian Michels wrote:
> -0 for a redesign. I might be the only one but I like the current
> simple design. I find it quite elegant. Apache projects do not tend to
> have fancy websites. That's ok. If you consider the AWS pages, they
> are far from being modern or beautiful.
>
> A redesign often is appealing but it can take a huge amount of time to
> get it right. This can mean the project is unable to focus on the main
> target of delivering great software and documentation.
>
> Some concerns:
> 1. Content regressions (content not being displayed properly, content
> and graphics not fitting anymore, code formatting breaking)
> 2. Higher entry barrier for committing (tooling / formatting becomes
> complicated)
> 3. Lack of focus on the content which needs work too (e.g. outdated
> information, lack of documentation of features)
>
> That said, I would support a redesign if we prevent regressions and
> build on standard tooling and best practices. I'm just not convinced
> (yet) that the pros outweigh the cons.
>
> -Max
>
> On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
>> Hi Deepthi,
>>
>> +1 for a redesign.
>>
>> I like the idea of setting up a committee/team that can produce some mock
>> ups and create a FLIP where the community can elect the best look and feel.
>> I very much look forward to seeing the results!
>>
>> Thanks,
>> Danny
>>
>>
>>
>> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
>>
>>> Hi Deepthi,
>>>
>>> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
>>> it is not Zeppelin.
>>>
>>> It is great to hear that Amazon UX/UI designers would contribute. There was
>>> a lack of front-end engineers in the past. Hopefully we could find enough
>>> front-end contributors for this big project.
>>>
>>> +1 looking forward to your proposal.
>>>
>>> Best regards,
>>> Jing
>>>
>>> [1] https://zeplin.io/
>>>
>>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
>>>
>>>> Hey!
>>>>
>>>> +1 for the proposal, the first page of Flink is more like a tutorial
>>>> document for developers compared to the other top apache projects.
>>> Looking
>>>> forward to a more attractive Flink website.
>>>>
>>>> Best regards,
>>>> Shuo
>>>>
>>>> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
>>> <mdeepth@amazon.com.invalid
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am a product manager for Kinesis Data Analytics, AWS’s managed
>>> service
>>>>> for Apache Flink. I’m creating this thread to gauge community interest
>>> in
>>>>> redesigning the Flink website: https://flink.apache.org/.
>>>>> A few of our customers have provided feedback that the Apache Flink
>>>>> website looks dated. One customer claimed that the website looks
>>>>> “unwelcoming” and lacks useful graphics and colors. Another said it
>>> looks
>>>>> “like a wiki page thrown together by developers.” Customers also point
>>>> out
>>>>> other related Apache project websites: https://spark.apache.org/ and
>>>>> https://kafka.apache.org/ as having “modern” user design. Many were
>>>>> surprised to hear that Flink has been a top-5 Apache project for
>>> several
>>>>> years now.
>>>>> As https://flink.apache.org/ is likely the first page someone new to
>>>>> Flink encounters, it will be helpful to modernize the look and feel of
>>>> the
>>>>> website. Given the growing interest in Flink, we have an opportunity to
>>>>> make content and features visible and easily accessible to customers.
>>> I’d
>>>>> like to learn if this is an idea we should pursue. I can create a FLIP
>>> if
>>>>> there is interest.
>>>>> Thanks,
>>>>> Deepthi Mohan
>>>>>
Re: Proposal to improve the Apache Flink website
Posted by Maximilian Michels <mx...@apache.org>.
-0 for a redesign. I might be the only one but I like the current
simple design. I find it quite elegant. Apache projects do not tend to
have fancy websites. That's ok. If you consider the AWS pages, they
are far from being modern or beautiful.
A redesign often is appealing but it can take a huge amount of time to
get it right. This can mean the project is unable to focus on the main
target of delivering great software and documentation.
Some concerns:
1. Content regressions (content not being displayed properly, content
and graphics not fitting anymore, code formatting breaking)
2. Higher entry barrier for committing (tooling / formatting becomes
complicated)
3. Lack of focus on the content which needs work too (e.g. outdated
information, lack of documentation of features)
That said, I would support a redesign if we prevent regressions and
build on standard tooling and best practices. I'm just not convinced
(yet) that the pros outweigh the cons.
-Max
On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer <da...@apache.org> wrote:
>
> Hi Deepthi,
>
> +1 for a redesign.
>
> I like the idea of setting up a committee/team that can produce some mock
> ups and create a FLIP where the community can elect the best look and feel.
> I very much look forward to seeing the results!
>
> Thanks,
> Danny
>
>
>
> On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
>
> > Hi Deepthi,
> >
> > Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
> > it is not Zeppelin.
> >
> > It is great to hear that Amazon UX/UI designers would contribute. There was
> > a lack of front-end engineers in the past. Hopefully we could find enough
> > front-end contributors for this big project.
> >
> > +1 looking forward to your proposal.
> >
> > Best regards,
> > Jing
> >
> > [1] https://zeplin.io/
> >
> > On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
> >
> > > Hey!
> > >
> > > +1 for the proposal, the first page of Flink is more like a tutorial
> > > document for developers compared to the other top apache projects.
> > Looking
> > > forward to a more attractive Flink website.
> > >
> > > Best regards,
> > > Shuo
> > >
> > > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
> > <mdeepth@amazon.com.invalid
> > > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I am a product manager for Kinesis Data Analytics, AWS’s managed
> > service
> > > > for Apache Flink. I’m creating this thread to gauge community interest
> > in
> > > > redesigning the Flink website: https://flink.apache.org/.
> > > > A few of our customers have provided feedback that the Apache Flink
> > > > website looks dated. One customer claimed that the website looks
> > > > “unwelcoming” and lacks useful graphics and colors. Another said it
> > looks
> > > > “like a wiki page thrown together by developers.” Customers also point
> > > out
> > > > other related Apache project websites: https://spark.apache.org/ and
> > > > https://kafka.apache.org/ as having “modern” user design. Many were
> > > > surprised to hear that Flink has been a top-5 Apache project for
> > several
> > > > years now.
> > > > As https://flink.apache.org/ is likely the first page someone new to
> > > > Flink encounters, it will be helpful to modernize the look and feel of
> > > the
> > > > website. Given the growing interest in Flink, we have an opportunity to
> > > > make content and features visible and easily accessible to customers.
> > I’d
> > > > like to learn if this is an idea we should pursue. I can create a FLIP
> > if
> > > > there is interest.
> > > > Thanks,
> > > > Deepthi Mohan
> > > >
> > >
> >
Re: Proposal to improve the Apache Flink website
Posted by Danny Cranmer <da...@apache.org>.
Hi Deepthi,
+1 for a redesign.
I like the idea of setting up a committee/team that can produce some mock
ups and create a FLIP where the community can elect the best look and feel.
I very much look forward to seeing the results!
Thanks,
Danny
On Tue, Feb 21, 2023 at 8:37 AM Jing Ge <ji...@ververica.com.invalid> wrote:
> Hi Deepthi,
>
> Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
> it is not Zeppelin.
>
> It is great to hear that Amazon UX/UI designers would contribute. There was
> a lack of front-end engineers in the past. Hopefully we could find enough
> front-end contributors for this big project.
>
> +1 looking forward to your proposal.
>
> Best regards,
> Jing
>
> [1] https://zeplin.io/
>
> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
>
> > Hey!
> >
> > +1 for the proposal, the first page of Flink is more like a tutorial
> > document for developers compared to the other top apache projects.
> Looking
> > forward to a more attractive Flink website.
> >
> > Best regards,
> > Shuo
> >
> > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi
> <mdeepth@amazon.com.invalid
> > >
> > wrote:
> >
> > > Hi,
> > >
> > > I am a product manager for Kinesis Data Analytics, AWS’s managed
> service
> > > for Apache Flink. I’m creating this thread to gauge community interest
> in
> > > redesigning the Flink website: https://flink.apache.org/.
> > > A few of our customers have provided feedback that the Apache Flink
> > > website looks dated. One customer claimed that the website looks
> > > “unwelcoming” and lacks useful graphics and colors. Another said it
> looks
> > > “like a wiki page thrown together by developers.” Customers also point
> > out
> > > other related Apache project websites: https://spark.apache.org/ and
> > > https://kafka.apache.org/ as having “modern” user design. Many were
> > > surprised to hear that Flink has been a top-5 Apache project for
> several
> > > years now.
> > > As https://flink.apache.org/ is likely the first page someone new to
> > > Flink encounters, it will be helpful to modernize the look and feel of
> > the
> > > website. Given the growing interest in Flink, we have an opportunity to
> > > make content and features visible and easily accessible to customers.
> I’d
> > > like to learn if this is an idea we should pursue. I can create a FLIP
> if
> > > there is interest.
> > > Thanks,
> > > Deepthi Mohan
> > >
> >
>
Re: Proposal to improve the Apache Flink website
Posted by Jing Ge <ji...@ververica.com.INVALID>.
Hi Deepthi,
Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
it is not Zeppelin.
It is great to hear that Amazon UX/UI designers would contribute. There was
a lack of front-end engineers in the past. Hopefully we could find enough
front-end contributors for this big project.
+1 looking forward to your proposal.
Best regards,
Jing
[1] https://zeplin.io/
On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng <nj...@gmail.com> wrote:
> Hey!
>
> +1 for the proposal, the first page of Flink is more like a tutorial
> document for developers compared to the other top apache projects. Looking
> forward to a more attractive Flink website.
>
> Best regards,
> Shuo
>
> On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi <mdeepth@amazon.com.invalid
> >
> wrote:
>
> > Hi,
> >
> > I am a product manager for Kinesis Data Analytics, AWS’s managed service
> > for Apache Flink. I’m creating this thread to gauge community interest in
> > redesigning the Flink website: https://flink.apache.org/.
> > A few of our customers have provided feedback that the Apache Flink
> > website looks dated. One customer claimed that the website looks
> > “unwelcoming” and lacks useful graphics and colors. Another said it looks
> > “like a wiki page thrown together by developers.” Customers also point
> out
> > other related Apache project websites: https://spark.apache.org/ and
> > https://kafka.apache.org/ as having “modern” user design. Many were
> > surprised to hear that Flink has been a top-5 Apache project for several
> > years now.
> > As https://flink.apache.org/ is likely the first page someone new to
> > Flink encounters, it will be helpful to modernize the look and feel of
> the
> > website. Given the growing interest in Flink, we have an opportunity to
> > make content and features visible and easily accessible to customers. I’d
> > like to learn if this is an idea we should pursue. I can create a FLIP if
> > there is interest.
> > Thanks,
> > Deepthi Mohan
> >
>
Re: Proposal to improve the Apache Flink website
Posted by Shuo Cheng <nj...@gmail.com>.
Hey!
+1 for the proposal, the first page of Flink is more like a tutorial
document for developers compared to the other top apache projects. Looking
forward to a more attractive Flink website.
Best regards,
Shuo
On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi <md...@amazon.com.invalid>
wrote:
> Hi,
>
> I am a product manager for Kinesis Data Analytics, AWS’s managed service
> for Apache Flink. I’m creating this thread to gauge community interest in
> redesigning the Flink website: https://flink.apache.org/.
> A few of our customers have provided feedback that the Apache Flink
> website looks dated. One customer claimed that the website looks
> “unwelcoming” and lacks useful graphics and colors. Another said it looks
> “like a wiki page thrown together by developers.” Customers also point out
> other related Apache project websites: https://spark.apache.org/ and
> https://kafka.apache.org/ as having “modern” user design. Many were
> surprised to hear that Flink has been a top-5 Apache project for several
> years now.
> As https://flink.apache.org/ is likely the first page someone new to
> Flink encounters, it will be helpful to modernize the look and feel of the
> website. Given the growing interest in Flink, we have an opportunity to
> make content and features visible and easily accessible to customers. I’d
> like to learn if this is an idea we should pursue. I can create a FLIP if
> there is interest.
> Thanks,
> Deepthi Mohan
>