Hey everyone, Thanks for the feedback.
I think we are in a state to merge this and continue with incremental changes. We should rather continuously improve the website instead of doing these stop-the-world all-or-nothing changes. ;-) The updated preview is still here: http://uce.github.io/flink-web # Adressed: - Stick with current features overview (raised by Felix, Stephan, Volker) * Felix: I like the current design better, since you get a really quick overview with many fancy pictures * Stephan: Add some pictures for features * Volker: I wonder where would people who do not know about Flink already find what it is about quickly in a concise way? I believe that the landing page should give information about features in a "declarative way" (what, not how ;-) ) before going into details. - Tag Line (raised by Robert, Alexander, Stephan) * Fabian: I am always suspicious if someone says "real-time"; The frontpage / first sentence does not make clear that Flink is also for Batch (<- Same point Robert raised) * Robert: The front page doesn't contain the word "batch" at all. People might be confused * Alexander: I think the top row text to be slightly revised. Flink offers a unified runtime and APIs for both batch + streaming, but at the moment the tagline suggests it is streaming only. * Stephan: Having a more prominent tag line => changed tag line to have batch and streaming in it (no real time) - Stack figure: 1. Don't stack high-level APIs and Libraries on top of each other (raised by Fabian, Alexander, Vasia) * Fabian: Don't stack libraries. It suggests that they depend on each other. Can we put them vertical like on our slides? * Alexander: Is there a particular reason why the APIs are stacked above each other in the picture (ML on top of Gelly on top of the Table API)? I was actually picturing the three next to each other... * Vasia: It might look like Gelly is built on top of Table API and ML on top of Gelly. Also, I get why Table is both on top of DataSet and DataStream, but I would add each component once and have a note "batch & streaming" instead of copying. First time I saw this on some slides, I thought it was a mistake :/ 3. Improve image quality (raised by Vasia) * Vasia: The stack image is a bit blurry. 4. Remove term language-integrated query (raised by Stephan) * Stephan: remove the term "Language Integrated Queries", I think that is trademarked by Microsoft - Align frontpage cells Frontpage cell alignment (raised by Alexander, Felix, Timo, Stephan) * Alexander: I suggest to change the layout of the bottom half in the following way [...] * Felix: Can you align the structure that there aren't as many overlaps? * Timo: I think the diagram could be a little bit larger and the blog post smaller, so that the lines meet in the middle ;) * Stephan: align the content as per Felix' suggestion - Disqus comments for blog (raised by Robert) * Robert: The disqus comments are missing in the blog => readded it to single posts - Twitter on front page (raised by Robert, Ted) * Robert: The link to our twitter account could be more prominent. Maybe on the front page? * Ted: If there is an active twitter entity for Flink, I recommend framing that on the home page - Broken links (raised by Robert, Fabian): * Robert: The frontpage link to the setup is broken => this is missing text in the docs, the link is OK * Fabian: Links in the right-side menu of the main blog pages are broken - Top navbar: 1. Add Community tab to navbar (raised by Vasia) * Vasia: +1 for Community in the front page, but why not also keep the link in the menu? 2. Fix logo dimensions in Chrome (raised by Vasia) * Vasia: The logo in the menu is quite disproportional in Chrome and looks quite bad. - Too wide for text (raised by Fabian): * Fabian: I find the text area a bit too wide for comfortable reading, especially for long texts such as blog posts or the how to contribute guide. - Streamed data inside the system (raised by Fabian): * Fabian: Data is not always "streamed all the way" in batch programs. There are also dams. # Won't address - Table API on front page (raised by Robert) * why is the "Table API" so prominent on the front page? Other staging projects like python or the hadoop compat don't get a mention at all. - Features: API text (raised by Fabian) * You can use native Java and Scala data types without packing them into key-value pairs, logical field addressing, and a wealth of operators." -> Sentence can be misunderstood ("without packaging [...], logical field addressing, and a wealth of operators") => this is our current text on the front page. - Scala vs. Java code snippets (raised by Fabian) * Fabian: The usual question: Java or Scala code snippets => I'll keep the Java snippets for now. We can change this incrementally. - Too few FAQ entries (raised by Fabian) * Fabian: I agree that some of the FAQs are outdated, but I guess more than two are still relevant. We might think about adding more common questions that we see on SO or the mailing lists. => The previous FAQ had irrelevant questions for the general project. This change separates docs FAQ and project FAQ. We need to add more questions though! I saw that Spark has a very nice project faq (https://spark.apache.org/faq.html) and we certainly have heard some of those questions as well. # To be addressed - Declutter (raised by Stephan, Kostas) * Stephan: tendency to pack too much content into a small space. * Kostas: I think starting with Ufuk's draft, de-cluttering it is a good start. - Codetabs.js (raised by Robert) * Robert: The codetabs.js file contains (and actually logs) "HERE" to the javascript console of my browser. Looks like some leftover debugging code. codetabs.js also gets a "Uncaught ReferenceError: $ is not defined" on the downloads page. => Not our code and I didn't have time to look into it - Increase font difference between headings (raised by Timo) * Timo: I would increase the font difference between headings and subheadings - Quickstarts (raised by Timo, Fabian) * Timo: Quickstart is missing * Fabian: Getting started does not link to the Quickstarts / Maven archetypes & only shows Maven dependencies for Java API - Too large pictures in blog posts (raised by Fabian) * Fabian: Pictures in some blog posts are too large, IMO (Streaming, Hadoop, Join post) - Broken links (raised by Robert, Fabian) * Robert: basically all links to the documentation in the blog are broken * Fabian: Links in latest blog posts not working - Add beta badge to components in flink-staging (raised by Robert) * Robert: Do you think adding a very little "Beta" badge on the system stack at the front page to the beta components would be a good idea? I think we should manage the expectations there. ML, gelly and the table API are all not part of any official stable release. On 13 May 2015, at 17:40, Stephan Ewen <se...@apache.org> wrote: > That is a good thing to have, agreed. > > On Wed, May 13, 2015 at 5:13 PM, Henry Saputra <henry.sapu...@gmail.com> > wrote: > >> For me personally, would like to still keep the architecture image [1] >> to show how it interacts with other systems. >> >> This usually help people to see how Flink could fit into their >> existing infrastructure pieces. >> >> - Henry >> >> >> [1] http://flink.apache.org/img/WhatIsFlink.png >> >> On Tue, May 12, 2015 at 1:55 AM, Stephan Ewen <se...@apache.org> wrote: >>> I think starting with Ufuk's draft, de-cluttering it is a good start. >>> >>> - Having a more prominent tag line >>> - Add some pictures for features back >>> - align the content as per Felix' suggestion >>> >>> That should give us a faster quick overview, but keep some serious >> content >>> in the starting page. >>> >>> I especially like that we have the stack figure and the recent blog posts >>> on the new website - that we should keep no matter what. >>> >>> >>> >>> On Tue, May 12, 2015 at 10:33 AM, Kostas Tzoumas <ktzou...@apache.org> >>> wrote: >>> >>>> Good points raised by Stephan, Felix, and Volker. >>>> >>>> Do you think we can achieve this by iterating on the new design? One >> thing >>>> we can indeed do is de-clutter a bit. Apart from that, what high level >>>> points would you like to see in the frontpage? >>>> >>>> On Tue, May 12, 2015 at 6:16 AM, Markl, Volker, Prof. Dr. < >>>> volker.ma...@tu-berlin.de> wrote: >>>> >>>>> -1 >>>>> >>>>> Dear all, >>>>> >>>>> first and foremost, thanks to Ufuk, for the new design. >>>>> >>>>> However, I agree with Felix that the current page is more of a >>>>> documentation than a front page. >>>>> >>>>> I wonder where would people who do not know about Flink already find >> what >>>>> it is about quickly in a concise way? >>>>> I believe that the landing page should give information about >> features >>>> in >>>>> a "declarative way" (what, not how ;-) ) >>>>> before going into details. >>>>> >>>>> I also believe that the current page does a better job on this than >> the >>>>> new design. To me the new design looks like >>>>> a perfect architecture page and intro to the documentation, but not >> like >>>>> the starting page of the project. >>>>> >>>>> Best, >>>>> Volker >>>>> >>>>> -----Ursprüngliche Nachricht----- >>>>> Von: ewenstep...@gmail.com [mailto:ewenstep...@gmail.com] Im Auftrag >> von >>>>> Stephan Ewen >>>>> Gesendet: Montag, 11. Mai 2015 22:01 >>>>> An: dev@flink.apache.org >>>>> Betreff: Re: New project website >>>>> >>>>> I agree that we should have a "more serious content, less happy >> hipster" >>>>> website. >>>>> >>>>> The current one is very nice, but I also think it has a tendency to >> pack >>>>> too much content into a small space. >>>>> For me (and probably other old people with less-than-sharp eyes), it >> may >>>>> help to space things out a bit... >>>>> >>>>> On Mon, May 11, 2015 at 2:58 PM, Timo Walther <twal...@apache.org> >>>> wrote: >>>>> >>>>>> I completely agree with Robert. Less marketing, more technical >>>>>> information targeted to the user group. >>>>>> >>>>>> I think the diagram could be a little bit larger and the blog post >>>>>> smaller, so that the lines meet in the middle ;) >>>>>> >>>>>> >>>>>> On 11.05.2015 14:39, Robert Metzger wrote: >>>>>> >>>>>>> I think its fine when the front page looks a little bit more like a >>>>>>> documentation. >>>>>>> Flink is no fancy hipster app, our users are either sysops running >> it >>>>>>> on a cluster or developers programming against APIs. >>>>>>> I think the new website will convince this target audience. >>>>>>> >>>>>>> I agree with you that aligning the vertical separators might help >>>>>>> visual structure of the page. I think we "only" need to center the >>>>>>> vertical separator between the getting started and the >> blog/community >>>>> section. >>>>>>> The positioning of the first line is fine, in my opinion.... >>>>>>> >>>>>>> >>>>>>> On Mon, May 11, 2015 at 2:27 PM, Felix Neutatz >>>>>>> <neut...@googlemail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Hi Ufuk, >>>>>>>> >>>>>>>> I really like the idea of redesigning the start page. But in my >>>>>>>> opinion your page design looks more like a documentation webpage >>>>>>>> than a starting page. >>>>>>>> >>>>>>>> In my personal opinion I like the current design better, since you >>>>>>>> get a really quick overview with many fancy pictures. (So if you >>>>>>>> wanna dive in deep, you can check out things in the documentation >>>>> or/and wiki). >>>>>>>> >>>>>>>> Moreover I have some design issue. Can you align the structure >> that >>>>>>>> there aren't as many overlaps. Here you can see what I mean: >>>>>>>> http://postimg.org/image/paogu6f3h/ >>>>>>>> >>>>>>>> This is only my personal opinion, maybe I have a wrong idea about >>>>>>>> starting pages. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Felix >>>>>>>> >>>>>>>> >>>>>>>> 2015-05-11 14:06 GMT+02:00 Hermann Gábor <reckone...@gmail.com>: >>>>>>>> >>>>>>>> Great! >>>>>>>>> It looks way better than the current site :) >>>>>>>>> >>>>>>>>> On Mon, May 11, 2015 at 1:28 PM Stephan Ewen <se...@apache.org> >>>>> wrote: >>>>>>>>> >>>>>>>>> I think we may have to remove the term "Language Integrated >>>>>>>>> Queries", I >>>>>>>>>> think that is trademarked by Microsoft. >>>>>>>>>> >>>>>>>>>> Otherwise, +1 >>>>>>>>>> >>>>>>>>>> On Mon, May 11, 2015 at 1:19 PM, Maximilian Michels >>>>>>>>>> <m...@apache.org> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> +1 very nice comprehensive overhaul of the website. I'd suggest >>>>>>>>>> to >>>>>>>>>>> >>>>>>>>>> merge >>>>>>>>> >>>>>>>>>> this as soon as possible. We can incrementally fix the remaining >>>>>>>>>>> >>>>>>>>>> issues >>>>>>>> >>>>>>>>> and >>>>>>>>>> >>>>>>>>>>> add a twitter feed to the front page. >>>>>>>>>>> >>>>>>>>>>> On Mon, May 11, 2015 at 12:09 PM, Ted Dunning >>>>>>>>>>> <ted.dunn...@gmail.com >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> If there is an active twitter entity for Flink, I recommend >>>>>>>>>>> framing >>>>>>>>>>>> >>>>>>>>>>> that >>>>>>>>>> >>>>>>>>>>> on >>>>>>>>>>> >>>>>>>>>>>> the home page. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, May 11, 2015 at 8:51 AM, Ufuk Celebi <u...@apache.org> >>>>>>>>>>>> >>>>>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hey all, >>>>>>>>>>>>> >>>>>>>>>>>>> I reworked the project website the last couple of days and >>>>>>>>>>>>> would >>>>>>>>>>>>> >>>>>>>>>>>> like >>>>>>>>> >>>>>>>>>> to >>>>>>>>>>> >>>>>>>>>>>> share the preview: >>>>>>>>>>>>> >>>>>>>>>>>>> http://uce.github.io/flink-web/ >>>>>>>>>>>>> >>>>>>>>>>>>> I would like to get this in asap. We can push incremental >>>>>>>>>>>>> updates >>>>>>>>>>>>> >>>>>>>>>>>> at >>>>>>>>> >>>>>>>>>> any >>>>>>>>>>> >>>>>>>>>>>> time, but I think this version is a big improvement over the >>>>>>>>>>>>> >>>>>>>>>>>> current >>>>>>>>> >>>>>>>>>> status >>>>>>>>>>>> >>>>>>>>>>>>> quo. If I get some +1s I'll go ahead and update the website >>>>>>>>>>>>> >>>>>>>>>>>> today. >>>>>>>> >>>>>>>>> – Ufuk >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>> >>>>> >>>> >>
