You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2014/09/04 22:19:24 UTC

[jira] [Commented] (FLINK-1089) The Flink website main page is uninformative.

    [ https://issues.apache.org/jira/browse/FLINK-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121922#comment-14121922 ] 

Ufuk Celebi commented on FLINK-1089:
------------------------------------

Thanks for pointing this out. I totally agree with you. Especially the first page is very important. Our first incubator release was a lot of work and the website was rushed to the end.

If you have anything in particular you would find useful (besides the points you already mentioned) feel free to post it here.

I will assign myself to this issue to have someone responsible, but everyone should feel free to come up with suggestions.

> The Flink website main page is uninformative.
> ---------------------------------------------
>
>                 Key: FLINK-1089
>                 URL: https://issues.apache.org/jira/browse/FLINK-1089
>             Project: Flink
>          Issue Type: Improvement
>          Components: Project Website
>            Reporter: Sergey Dudoladov
>            Priority: Trivial
>              Labels: documentaion, site
>
> The webpage at http://flink.incubator.apache.org/ provides no  information on why Flink is useful.
> The problem is that after skimming the main page people cannot figure out why they should try Flink.  I gave the link above to my friend from industry, and in 5 minutes he asked me if Flink was an enterprise Java framework.
> I suggest adding 2-3 paragraphs under the "Project Overview" heading. They should explain in plain English what dataflow systems are, which tasks they solve and what differentiates Flink from its competitors.
> A link to the recent VLDB paper might help as well. 
> PS I would like to emphasize the word "plain" in the previous paragraph.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)