Draft for Project Website

[Henry Saputra]

Maybe I am doing something wrong, when I run build.sh from Flink svn
it seems like it wiped out the files inside the docs/0.6-SNAPSHOT/

Is there any steps I need to do before?

- Henry

On Sun, Jul 6, 2014 at 1:06 AM, Robert Metzger <[hidden email]> wrote:

> I pushed the md files to the svn repo:
> https://svn.apache.org/repos/asf/incubator/flink
> The md files of the documentation are in the main git repostiory. The
> build.sh script from the svn assembles the md files from the different
> locations in the correct way.
>
>
> On Sun, Jul 6, 2014 at 2:32 AM, Henry Saputra <[hidden email]>
> wrote:
>
>> Hi Robert, did you push the md source files to svn or git repo?
>>
>> On Fri, Jul 4, 2014 at 2:11 AM, Robert Metzger <[hidden email]>
>> wrote:
>> > Thanks for the feedback.
>> > I've added the link to "How it works" and the incubator status page.
>> >
>> > I want to note that Ufuk did most of the work for the website: The
>> initial
>> > design and content, the jekyll plugins and the rework of the
>> documentation
>> > into the repository.
>> >
>> > I'm now going to publish the site at http://flink.incubator.apache.org/.
>> >
>> >
>> > On Thu, Jul 3, 2014 at 8:01 PM, Stephan Ewen <[hidden email]> wrote:
>> >
>> >> Very nice work!
>> >>
>> >> I personally think that "ASF and Flink" can directly link to "
>> >> http://incubator.apache.org/projects/flink.html". The text says
>> basically
>> >> the same as the footer that is on every page.
>> >>
>>

[Robert Metzger]

Sorry, I forgot to document the script. You have to execute it with
"./build.sh -u".  ("u" for "update")
I'll change the script to perform the update by default once I look into it
again.


On Thu, Jul 10, 2014 at 4:26 AM, Henry Saputra <[hidden email]>
wrote:

> Maybe I am doing something wrong, when I run build.sh from Flink svn
> it seems like it wiped out the files inside the docs/0.6-SNAPSHOT/
>
> Is there any steps I need to do before?
>
> - Henry
>
> On Sun, Jul 6, 2014 at 1:06 AM, Robert Metzger <[hidden email]>
> wrote:
> > I pushed the md files to the svn repo:
> > https://svn.apache.org/repos/asf/incubator/flink
> > The md files of the documentation are in the main git repostiory. The
> > build.sh script from the svn assembles the md files from the different
> > locations in the correct way.
> >
> >
> > On Sun, Jul 6, 2014 at 2:32 AM, Henry Saputra <[hidden email]>
> > wrote:
> >
> >> Hi Robert, did you push the md source files to svn or git repo?
> >>
> >> On Fri, Jul 4, 2014 at 2:11 AM, Robert Metzger <[hidden email]>
> >> wrote:
> >> > Thanks for the feedback.
> >> > I've added the link to "How it works" and the incubator status page.
> >> >
> >> > I want to note that Ufuk did most of the work for the website: The
> >> initial
> >> > design and content, the jekyll plugins and the rework of the
> >> documentation
> >> > into the repository.
> >> >
> >> > I'm now going to publish the site at
> http://flink.incubator.apache.org/.
> >> >
> >> >
> >> > On Thu, Jul 3, 2014 at 8:01 PM, Stephan Ewen <[hidden email]>
> wrote:
> >> >
> >> >> Very nice work!
> >> >>
> >> >> I personally think that "ASF and Flink" can directly link to "
> >> >> http://incubator.apache.org/projects/flink.html". The text says
> >> basically
> >> >> the same as the footer that is on every page.
> >> >>
> >>
>

[Markl, Volker, Prof. Dr.]

One comment: on mobile devices like my IPad the stratopshere.eu website seem to have a better layout,
in particular wrt to dynamic features.

For instance, when scrolling, the menu on the top remains on the top. I am not sure if those dynamic
features were not replicate due to using a different CMS. However, if possible, it would be nice
to replicate some of the dynamic features, like the menu staying on top, or  when browsing through the
documentation having the menu on the right highlight the section/topic of the documentation one is
currently looking at, etc.

-----Ursprüngliche Nachricht-----
Von: Robert Metzger [mailto:[hidden email]]
Gesendet: Donnerstag, 10. Juli 2014 11:21
An: [hidden email]
Betreff: Re: Draft for Project Website

Sorry, I forgot to document the script. You have to execute it with "./build.sh -u".  ("u" for "update") I'll change the script to perform the update by default once I look into it again.


On Thu, Jul 10, 2014 at 4:26 AM, Henry Saputra <[hidden email]>
wrote:

> Maybe I am doing something wrong, when I run build.sh from Flink svn
> it seems like it wiped out the files inside the docs/0.6-SNAPSHOT/
>
> Is there any steps I need to do before?
>
> - Henry
>
> On Sun, Jul 6, 2014 at 1:06 AM, Robert Metzger <[hidden email]>
> wrote:
> > I pushed the md files to the svn repo:
> > https://svn.apache.org/repos/asf/incubator/flink
> > The md files of the documentation are in the main git repostiory.
> > The build.sh script from the svn assembles the md files from the
> > different locations in the correct way.
> >
> >
> > On Sun, Jul 6, 2014 at 2:32 AM, Henry Saputra
> > <[hidden email]>
> > wrote:
> >
> >> Hi Robert, did you push the md source files to svn or git repo?
> >>
> >> On Fri, Jul 4, 2014 at 2:11 AM, Robert Metzger
> >> <[hidden email]>
> >> wrote:
> >> > Thanks for the feedback.
> >> > I've added the link to "How it works" and the incubator status page.
> >> >
> >> > I want to note that Ufuk did most of the work for the website:
> >> > The
> >> initial
> >> > design and content, the jekyll plugins and the rework of the
> >> documentation
> >> > into the repository.
> >> >
> >> > I'm now going to publish the site at
> http://flink.incubator.apache.org/.
> >> >
> >> >
> >> > On Thu, Jul 3, 2014 at 8:01 PM, Stephan Ewen <[hidden email]>
> wrote:
> >> >
> >> >> Very nice work!
> >> >>
> >> >> I personally think that "ASF and Flink" can directly link to "
> >> >> http://incubator.apache.org/projects/flink.html". The text says
> >> basically
> >> >> the same as the footer that is on every page.
> >> >>
> >>
>

[Henry Saputra]

Got it, no worries

On Thursday, July 10, 2014, Robert Metzger <[hidden email]> wrote:

> Sorry, I forgot to document the script. You have to execute it with
> "./build.sh -u".  ("u" for "update")
> I'll change the script to perform the update by default once I look into it
> again.
>
>
> On Thu, Jul 10, 2014 at 4:26 AM, Henry Saputra <[hidden email]
> <javascript:;>>
> wrote:
>
> > Maybe I am doing something wrong, when I run build.sh from Flink svn
> > it seems like it wiped out the files inside the docs/0.6-SNAPSHOT/
> >
> > Is there any steps I need to do before?
> >
> > - Henry
> >
> > On Sun, Jul 6, 2014 at 1:06 AM, Robert Metzger <[hidden email]
> <javascript:;>>
> > wrote:
> > > I pushed the md files to the svn repo:
> > > https://svn.apache.org/repos/asf/incubator/flink
> > > The md files of the documentation are in the main git repostiory. The
> > > build.sh script from the svn assembles the md files from the different
> > > locations in the correct way.
> > >
> > >
> > > On Sun, Jul 6, 2014 at 2:32 AM, Henry Saputra <[hidden email]
> <javascript:;>>
> > > wrote:
> > >
> > >> Hi Robert, did you push the md source files to svn or git repo?
> > >>
> > >> On Fri, Jul 4, 2014 at 2:11 AM, Robert Metzger <[hidden email]
> <javascript:;>>
> > >> wrote:
> > >> > Thanks for the feedback.
> > >> > I've added the link to "How it works" and the incubator status page.
> > >> >
> > >> > I want to note that Ufuk did most of the work for the website: The
> > >> initial
> > >> > design and content, the jekyll plugins and the rework of the
> > >> documentation
> > >> > into the repository.
> > >> >
> > >> > I'm now going to publish the site at
> > http://flink.incubator.apache.org/.
> > >> >
> > >> >
> > >> > On Thu, Jul 3, 2014 at 8:01 PM, Stephan Ewen <[hidden email]
> <javascript:;>>
> > wrote:
> > >> >
> > >> >> Very nice work!
> > >> >>
> > >> >> I personally think that "ASF and Flink" can directly link to "
> > >> >> http://incubator.apache.org/projects/flink.html". The text says
> > >> basically
> > >> >> the same as the footer that is on every page.
> > >> >>
> > >>
> >
>

[Robert Metzger]

The two websites are basically using the same technologies behind the
scenes. Having the main navigation always on top is very easy to implement.
If others feel the same, its very easy to change the behavior.

Regarding the navigation in the documentation: We changed some details here
because we are now maintaining the documentation within the source code and
grab it from there for publishing it in the web. Since we are doing this
automatically, its difficult to have a sophisticated layout there.
Lets see if Ufuk (he knows the stuff very well) has an idea for a trade-off.

We certainly have to improve the website's ability to react to different
screen sizes. It seems that stratosphere.eu is switching earlier to the
smaller menu.


On Thu, Jul 10, 2014 at 11:26 AM, Markl, Volker, Prof. Dr. <
[hidden email]> wrote:

> One comment: on mobile devices like my IPad the stratopshere.eu website
> seem to have a better layout,
> in particular wrt to dynamic features.
>
> For instance, when scrolling, the menu on the top remains on the top. I am
> not sure if those dynamic
> features were not replicate due to using a different CMS. However, if
> possible, it would be nice
> to replicate some of the dynamic features, like the menu staying on top,
> or  when browsing through the
> documentation having the menu on the right highlight the section/topic of
> the documentation one is
> currently looking at, etc.
>
> -----Ursprüngliche Nachricht-----
> Von: Robert Metzger [mailto:[hidden email]]
> Gesendet: Donnerstag, 10. Juli 2014 11:21
> An: [hidden email]
> Betreff: Re: Draft for Project Website
>
> Sorry, I forgot to document the script. You have to execute it with
> "./build.sh -u".  ("u" for "update") I'll change the script to perform the
> update by default once I look into it again.
>
>
> On Thu, Jul 10, 2014 at 4:26 AM, Henry Saputra <[hidden email]>
> wrote:
>
> > Maybe I am doing something wrong, when I run build.sh from Flink svn
> > it seems like it wiped out the files inside the docs/0.6-SNAPSHOT/
> >
> > Is there any steps I need to do before?
> >
> > - Henry
> >
> > On Sun, Jul 6, 2014 at 1:06 AM, Robert Metzger <[hidden email]>
> > wrote:
> > > I pushed the md files to the svn repo:
> > > https://svn.apache.org/repos/asf/incubator/flink
> > > The md files of the documentation are in the main git repostiory.
> > > The build.sh script from the svn assembles the md files from the
> > > different locations in the correct way.
> > >
> > >
> > > On Sun, Jul 6, 2014 at 2:32 AM, Henry Saputra
> > > <[hidden email]>
> > > wrote:
> > >
> > >> Hi Robert, did you push the md source files to svn or git repo?
> > >>
> > >> On Fri, Jul 4, 2014 at 2:11 AM, Robert Metzger
> > >> <[hidden email]>
> > >> wrote:
> > >> > Thanks for the feedback.
> > >> > I've added the link to "How it works" and the incubator status page.
> > >> >
> > >> > I want to note that Ufuk did most of the work for the website:
> > >> > The
> > >> initial
> > >> > design and content, the jekyll plugins and the rework of the
> > >> documentation
> > >> > into the repository.
> > >> >
> > >> > I'm now going to publish the site at
> > http://flink.incubator.apache.org/.
> > >> >
> > >> >
> > >> > On Thu, Jul 3, 2014 at 8:01 PM, Stephan Ewen <[hidden email]>
> > wrote:
> > >> >
> > >> >> Very nice work!
> > >> >>
> > >> >> I personally think that "ASF and Flink" can directly link to "
> > >> >> http://incubator.apache.org/projects/flink.html". The text says
> > >> basically
> > >> >> the same as the footer that is on every page.
> > >> >>
> > >>
> >
>

[Ufuk Celebi]

On 14 Jul 2014, at 20:12, Robert Metzger <[hidden email]> wrote:

> The two websites are basically using the same technologies behind the
> scenes. Having the main navigation always on top is very easy to implement.
> If others feel the same, its very easy to change the behavior.

+1

> Regarding the navigation in the documentation: We changed some details here
> because we are now maintaining the documentation within the source code and
> grab it from there for publishing it in the web. Since we are doing this
> automatically, its difficult to have a sophisticated layout there.
> Lets see if Ufuk (he knows the stuff very well) has an idea for a trade-off.

We can definitely highlight the current page on the left. If that is the question: +1

If the problem is the sub navigation: we realized at some point that the table of contents per page (the subnavigation, which is also highlighted) does not work so well with large doc pages like the Java API and therefore moved it to the top of body, where it does not make so much sense to highlight.

[Fabian Hueske]

+1 for the menu to stay on top.

As Ufuk said, we had some bad experiences with a detailed menu on the left.


2014-07-16 9:30 GMT+02:00 Ufuk Celebi <[hidden email]>:

>
> On 14 Jul 2014, at 20:12, Robert Metzger <[hidden email]> wrote:
>
> > The two websites are basically using the same technologies behind the
> > scenes. Having the main navigation always on top is very easy to
> implement.
> > If others feel the same, its very easy to change the behavior.
>
> +1
>
> > Regarding the navigation in the documentation: We changed some details
> here
> > because we are now maintaining the documentation within the source code
> and
> > grab it from there for publishing it in the web. Since we are doing this
> > automatically, its difficult to have a sophisticated layout there.
> > Lets see if Ufuk (he knows the stuff very well) has an idea for a
> trade-off.
>
> We can definitely highlight the current page on the left. If that is the
> question: +1
>
> If the problem is the sub navigation: we realized at some point that the
> table of contents per page (the subnavigation, which is also highlighted)
> does not work so well with large doc pages like the Java API and therefore
> moved it to the top of body, where it does not make so much sense to
> highlight.

[Robert Metzger]

Okay, I updated the website.


On Wed, Jul 16, 2014 at 11:53 AM, Fabian Hueske <[hidden email]> wrote:

> +1 for the menu to stay on top.
>
> As Ufuk said, we had some bad experiences with a detailed menu on the left.
>
>
> 2014-07-16 9:30 GMT+02:00 Ufuk Celebi <[hidden email]>:
>
> >
> > On 14 Jul 2014, at 20:12, Robert Metzger <[hidden email]> wrote:
> >
> > > The two websites are basically using the same technologies behind the
> > > scenes. Having the main navigation always on top is very easy to
> > implement.
> > > If others feel the same, its very easy to change the behavior.
> >
> > +1
> >
> > > Regarding the navigation in the documentation: We changed some details
> > here
> > > because we are now maintaining the documentation within the source code
> > and
> > > grab it from there for publishing it in the web. Since we are doing
> this
> > > automatically, its difficult to have a sophisticated layout there.
> > > Lets see if Ufuk (he knows the stuff very well) has an idea for a
> > trade-off.
> >
> > We can definitely highlight the current page on the left. If that is the
> > question: +1
> >
> > If the problem is the sub navigation: we realized at some point that the
> > table of contents per page (the subnavigation, which is also highlighted)
> > does not work so well with large doc pages like the Java API and
> therefore
> > moved it to the top of body, where it does not make so much sense to
> > highlight.
>