Hi,

+1 for white websites indeed :-)

Some comments from my side:


   -  The logo in the menu is quite disproportional in Chrome and looks
   quite bad. I can send you a screenshot if you can't check. It looks good in
   Safari.
   -  The stack image is a bit blurry and also quite confusing. 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 :/
   - +1 for Community in the front page, but why not also keep the link in
   the menu?


Cheers,
Vasia.

On 11 May 2015 at 10:20, Robert Metzger <rmetz...@apache.org> wrote:

> Amazing work!
> The new site looks really good.
> I like white websites more, they are easier to read.
> Also, its great that you're putting the community on the front page. I hear
> quite often that users like the good support they are getting from the
> mailing lists. I personally experienced other open source communities which
> didn't answer my questions on their list. I think that's not happening in
> our community!
> The blog posts with their dates on the front page show that the project is
> very active.
>
> Some detailed comments:
> - The front page doesn't contain the word "batch" at all. People might be
> confused
> - 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.
> - 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.
> - The disqus comments are missing in the blog
> - The frontpage link to the setup is broken:
> http://ci.apache.org/projects/flink/flink-docs-master/setup/
> - 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.
> - I don't want to put the burden of fixing this onto alone (= I can help
> you), but basically all links to the documentation in the blog are broken.
> For example for the 0.9.0-m1 annoucements, the links to gelly and the table
> api are broken. This issue is independent of this change, but still
> annoying.
> - The link to our twitter account could be more prominent. Maybe on the
> front page?
>
> .. I'll give feedback to the Feature page, once its done ;)
>
>
>
> On Mon, May 11, 2015 at 9: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
>

Reply via email to