Re: [PROPOSAL] New Beam website design?

[Minudika Malshan]

Thanks a lot for your replies.

Could you please provide me the location of the source code of the site.?

Then I could look into it.

BR

On Thu, Oct 27, 2016 at 9:52 PM, Davor Bonaci  wrote:

> The best place to learn how to get started is the Contribution Guide [1].
> The list of pending JIRA issues related to the website is also available
> [2].
>
> I think BEAM-752 would be the best to get your feet wet. Other good
> candidates are 516, 268, 776. If someone knows a good (non-fragile)
> solution to 751, that would be a great contribution!
>
> Davor
>
> [1] http://beam.incubator.apache.org/contribute/contribution-guide/
> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%
> 22%2C%20Reopened)%20AND%20component%20%3D%20website
>
> On Thu, Oct 27, 2016 at 5:20 AM, Jean-Baptiste Onofré 
> wrote:
>
> > Great !! Thanks.
> >
> > You can take a look on BEAM-500 and 501 and also the PR I did last week.
> >
> > I plan to submit new PRs during the week end. So please let me know how
> we
> > can sync.
> >
> > Thanks
> > Regards
> > JB
> >
> > On Oct 27, 2016, at 14:04, Minudika Malshan 
> wrote:
> >>
> >> Hi all,
> >>
> >> I would like to join for the development of the new site.
> >> Is there any issue tracking method for this? (Are there any jirra
> issues)
> >>
> >> Thank you!
> >>
> >>
> >>
> >> On Thu, Oct 27, 2016 at 4:01 PM, Jean-Baptiste Onofré 
> >> wrote:
> >>
> >>
> >>
> >>>Hi
> >>>
> >>>
> >>>
> >>>  You can propose a PR on this Jira.
> >>>
> >>>
> >>>
> >>>  We will be more than happy to review it.
> >>>
> >>>
> >>>
> >>>  Thanks
> >>>
> >>>  Regards
> >>>
> >>>  JB
> >>>
> >>>
> >>>
> >>>  ⁣​
> >>>
> >>>
> >>>
> >>>  On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir <
> mabdullah...@gmail.com>
> >>>
> >>>  wrote:
> >>>
> >>>
> >>>
> Thank you very much for taking time to respond Davor :)
> 
> 
> 
>  Regarding BEAM-752, i can work on that, i have already built some
> 
>  Dataflow
> 
>  Piplines on Google Cloud in Python language.
> 
> 
> 
>  Again Can you tell me where to start for BEAM-752. I am new to ASF
> 
>  contribution, so onboarding steps are kind of a black box to me :).
> 
> 
> 
>  On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci 
> 
>  wrote:
> 
> 
> 
> 
> 
> >  Absolutely!
> >
> >
> >
> >  I'm currently reviewing JB's PR #51, and that should go in shortly.
> >
> >
> >Within
> 
> 
> 
> >  a day or so, I should have a better idea about future work in
> this
> >
> >
> >specific
> 
> 
> 
> >  area; please stay tuned.
> >
> >
> >
> >  There are also separate things that are ready to be started at any
> >
> >
> >time.
> 
> 
> 
> >  BEAM-752 comes to mind first. Is this something you'd be
> interested
> >
> >
> >in?
> 
> 
> 
> >
> >  On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir
> >
> >
> >
> 
> 
> 
> >  wrote:
> >
> >
> >
> >
> >
> >>   Hi Davor,
> >>
> >>
> >>
> >>  I am done with my local setup to start contributing, I have forked
> >>
> >>
> >>
> >and
> 
> 
> 
> >
> >>   merged pull request *(**pull/51)* into my local repo. Then I
> read
> >>
> >>
> >>
> >the
> 
> 
> 
> >
> >>
> >>  google docs, their are two tasks mentioned in it, as [Beam-500] and
> >>
> >>  [Beam-501].
> >>
> >>  I found out that [Beam-500] is closed in JIRA and [Beam-501] is
> >>
> >>  assigned to Jean-Baptiste
> >>
> >>  Onofré, Is their any task that you can assign to me ?
> >>
> >>
> >>
> >>  Thanks.
> >>
> >>
> >>
> >>  Regards,
> >>
> >>  Abdullah Bashir
> >>
> >>
> >>
> >>
> >>
> >>  On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci 
> >>
> >>
> >>
> >wrote:
> 
> 
> 
> >
> >>
> >>
> >>
> >>>Abdullah, welcome!
> >>>
> >>>
> >>>
> >>>  I think it's rather clear we've been struggling with the website,
> >>>
> >>>
> >>>
> >>
> >so any
> 
> 
> 
> >
> >>
> >>>help is very welcome. It is a little bit messy right now --
> there
> >>>
> >>>
> >>>
> >>
> >are a
> 
> 
> 
> >
> >>   few
> >>
> >>
> >>
> >>>outstanding pull requests and forked branches. I'm trying
> to get
> >>>
> >>>
> >>>
> >>
> >all
> 
> 
> 
> >
> >>   

Re: [PROPOSAL] New Beam website design?

[Davor Bonaci]

The best place to learn how to get started is the Contribution Guide [1].
The list of pending JIRA issues related to the website is also available
[2].

I think BEAM-752 would be the best to get your feet wet. Other good
candidates are 516, 268, 776. If someone knows a good (non-fragile)
solution to 751, that would be a great contribution!

Davor

[1] http://beam.incubator.apache.org/contribute/contribution-guide/
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20website

On Thu, Oct 27, 2016 at 5:20 AM, Jean-Baptiste Onofré 
wrote:

> Great !! Thanks.
>
> You can take a look on BEAM-500 and 501 and also the PR I did last week.
>
> I plan to submit new PRs during the week end. So please let me know how we
> can sync.
>
> Thanks
> Regards
> JB
>
> On Oct 27, 2016, at 14:04, Minudika Malshan  wrote:
>>
>> Hi all,
>>
>> I would like to join for the development of the new site.
>> Is there any issue tracking method for this? (Are there any jirra issues)
>>
>> Thank you!
>>
>>
>>
>> On Thu, Oct 27, 2016 at 4:01 PM, Jean-Baptiste Onofré 
>> wrote:
>>
>>
>>
>>>Hi
>>>
>>>
>>>
>>>  You can propose a PR on this Jira.
>>>
>>>
>>>
>>>  We will be more than happy to review it.
>>>
>>>
>>>
>>>  Thanks
>>>
>>>  Regards
>>>
>>>  JB
>>>
>>>
>>>
>>>  ⁣​
>>>
>>>
>>>
>>>  On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir 
>>>
>>>  wrote:
>>>
>>>
>>>
Thank you very much for taking time to respond Davor :)



 Regarding BEAM-752, i can work on that, i have already built some

 Dataflow

 Piplines on Google Cloud in Python language.



 Again Can you tell me where to start for BEAM-752. I am new to ASF

 contribution, so onboarding steps are kind of a black box to me :).



 On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci 

 wrote:





>  Absolutely!
>
>
>
>  I'm currently reviewing JB's PR #51, and that should go in shortly.
>
>
>Within



>  a day or so, I should have a better idea about future work in this
>
>
>specific



>  area; please stay tuned.
>
>
>
>  There are also separate things that are ready to be started at any
>
>
>time.



>  BEAM-752 comes to mind first. Is this something you'd be interested
>
>
>in?



>
>  On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir
>
>
>



>  wrote:
>
>
>
>
>
>>   Hi Davor,
>>
>>
>>
>>  I am done with my local setup to start contributing, I have forked
>>
>>
>>
>and



>
>>   merged pull request *(**pull/51)* into my local repo. Then I read
>>
>>
>>
>the



>
>>
>>  google docs, their are two tasks mentioned in it, as [Beam-500] and
>>
>>  [Beam-501].
>>
>>  I found out that [Beam-500] is closed in JIRA and [Beam-501] is
>>
>>  assigned to Jean-Baptiste
>>
>>  Onofré, Is their any task that you can assign to me ?
>>
>>
>>
>>  Thanks.
>>
>>
>>
>>  Regards,
>>
>>  Abdullah Bashir
>>
>>
>>
>>
>>
>>  On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci 
>>
>>
>>
>wrote:



>
>>
>>
>>
>>>Abdullah, welcome!
>>>
>>>
>>>
>>>  I think it's rather clear we've been struggling with the website,
>>>
>>>
>>>
>>
>so any



>
>>
>>>help is very welcome. It is a little bit messy right now -- there
>>>
>>>
>>>
>>
>are a



>
>>   few
>>
>>
>>
>>>outstanding pull requests and forked branches. I'm trying to get
>>>
>>>
>>>
>>
>all



>
>>   this
>>
>>
>>
>>>into one place, so anybody can contribute and make progress.
>>>
>>>
>>>
>>>  Also, the general website organization has been discussed before,
>>>
>>>
>>>
>>
>see



>
>>   this
>>
>>
>>
>>>thread [1] and the attached document for details.
>>>
>>>
>>>
>>>  Davor
>>>
>>>
>>>
>>>  [1]
>>>
>>>
>>>   https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
>>>
>>>  mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
>>>
>>>
>>>   mail.gmail.com%3E
>>>
>>>
>>>
>>>  On Sun, Oct 23, 2016 at 12:34 AM, 

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Great !! Thanks.

You can take a look on BEAM-500 and 501 and also the PR I did last week.

I plan to submit new PRs during the week end. So please let me know how we can 
sync.

Thanks
Regards
JB

⁣​

On Oct 27, 2016, 14:04, at 14:04, Minudika Malshan  
wrote:
>Hi all,
>
>I would like to join for the development of the new site.
>Is there any issue tracking method for this? (Are there any jirra
>issues)
>
>Thank you!
>
>
>
>On Thu, Oct 27, 2016 at 4:01 PM, Jean-Baptiste Onofré 
>wrote:
>
>> Hi
>>
>> You can propose a PR on this Jira.
>>
>> We will be more than happy to review it.
>>
>> Thanks
>> Regards
>> JB
>>
>> ⁣​
>>
>> On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir
>
>> wrote:
>> >Thank you very much for taking time to respond Davor :)
>> >
>> >Regarding BEAM-752, i can work on that, i have already built some
>> >Dataflow
>> >Piplines on Google Cloud in Python language.
>> >
>> >Again Can you tell me where to start for BEAM-752. I am new to ASF
>> >contribution, so onboarding steps are kind of a black box to me :).
>> >
>> >On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci 
>> >wrote:
>> >
>> >> Absolutely!
>> >>
>> >> I'm currently reviewing JB's PR #51, and that should go in
>shortly.
>> >Within
>> >> a day or so, I should have a better idea about future work in this
>> >specific
>> >> area; please stay tuned.
>> >>
>> >> There are also separate things that are ready to be started at any
>> >time.
>> >> BEAM-752 comes to mind first. Is this something you'd be
>interested
>> >in?
>> >>
>> >> On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir
>> >
>> >> wrote:
>> >>
>> >>> Hi Davor,
>> >>>
>> >>> I am done with my local setup to start contributing, I have
>forked
>> >and
>> >>> merged pull request *(**pull/51)* into my  local repo. Then I
>read
>> >the
>> >>>
>> >>> google docs, their are two tasks mentioned in it, as [Beam-500]
>and
>> >>> [Beam-501].
>> >>> I found out that [Beam-500] is closed in JIRA and [Beam-501] is
>> >>> assigned to Jean-Baptiste
>> >>> Onofré, Is their any task that you can assign to me ?
>> >>>
>> >>> Thanks.
>> >>>
>> >>> Regards,
>> >>> Abdullah Bashir
>> >>>
>> >>>
>> >>> On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci 
>> >wrote:
>> >>>
>> >>> > Abdullah, welcome!
>> >>> >
>> >>> > I think it's rather clear we've been struggling with the
>website,
>> >so any
>> >>> > help is very welcome. It is a little bit messy right now --
>there
>> >are a
>> >>> few
>> >>> > outstanding pull requests and forked branches. I'm trying to
>get
>> >all
>> >>> this
>> >>> > into one place, so anybody can contribute and make progress.
>> >>> >
>> >>> > Also, the general website organization has been discussed
>before,
>> >see
>> >>> this
>> >>> > thread [1] and the attached document for details.
>> >>> >
>> >>> > Davor
>> >>> >
>> >>> > [1]
>> >>> > https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
>> >>> > mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
>> >>> > mail.gmail.com%3E
>> >>> >
>> >>> > On Sun, Oct 23, 2016 at 12:34 AM, Jean-Baptiste Onofré
>> >> >>> >
>> >>> > wrote:
>> >>> >
>> >>> > > Hi
>> >>> > >
>> >>> > > You can take a look on the PR I creates last Friday. It
>contains
>> >a
>> >>> > > CSS/skin proposal.
>> >>> > >
>> >>> > > The mock-up is there: http://maven.nanthrax.net/beam
>> >>> > >
>> >>> > > Regards
>> >>> > > JB
>> >>> > >
>> >>> > > ⁣​
>> >>> > >
>> >>> > > On Oct 23, 2016, 09:27, at 09:27, Abdullah Bashir <
>> >>> > mabdullah...@gmail.com>
>> >>> > > wrote:
>> >>> > > >Hi,
>> >>> > > >
>> >>> > > >is their any help i can do on website designing ?
>> >>> > > >I am good at HTML5, CSS3 and javascript.
>> >>> > > >
>> >>> > > >Regards,
>> >>> > > >Abdullah Bashir
>> >>> > >
>> >>> >
>> >>>
>> >>
>> >>
>>
>
>
>
>-- 
>*Minudika Malshan*
>Undergraduate
>Department of Computer Science and Engineering
>University of Moratuwa
>Sri Lanka.

Re: [PROPOSAL] New Beam website design?

[Minudika Malshan]

Hi all,

I would like to join for the development of the new site.
Is there any issue tracking method for this? (Are there any jirra issues)

Thank you!



On Thu, Oct 27, 2016 at 4:01 PM, Jean-Baptiste Onofré 
wrote:

> Hi
>
> You can propose a PR on this Jira.
>
> We will be more than happy to review it.
>
> Thanks
> Regards
> JB
>
> ⁣​
>
> On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir 
> wrote:
> >Thank you very much for taking time to respond Davor :)
> >
> >Regarding BEAM-752, i can work on that, i have already built some
> >Dataflow
> >Piplines on Google Cloud in Python language.
> >
> >Again Can you tell me where to start for BEAM-752. I am new to ASF
> >contribution, so onboarding steps are kind of a black box to me :).
> >
> >On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci 
> >wrote:
> >
> >> Absolutely!
> >>
> >> I'm currently reviewing JB's PR #51, and that should go in shortly.
> >Within
> >> a day or so, I should have a better idea about future work in this
> >specific
> >> area; please stay tuned.
> >>
> >> There are also separate things that are ready to be started at any
> >time.
> >> BEAM-752 comes to mind first. Is this something you'd be interested
> >in?
> >>
> >> On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir
> >
> >> wrote:
> >>
> >>> Hi Davor,
> >>>
> >>> I am done with my local setup to start contributing, I have forked
> >and
> >>> merged pull request *(**pull/51)* into my  local repo. Then I read
> >the
> >>>
> >>> google docs, their are two tasks mentioned in it, as [Beam-500] and
> >>> [Beam-501].
> >>> I found out that [Beam-500] is closed in JIRA and [Beam-501] is
> >>> assigned to Jean-Baptiste
> >>> Onofré, Is their any task that you can assign to me ?
> >>>
> >>> Thanks.
> >>>
> >>> Regards,
> >>> Abdullah Bashir
> >>>
> >>>
> >>> On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci 
> >wrote:
> >>>
> >>> > Abdullah, welcome!
> >>> >
> >>> > I think it's rather clear we've been struggling with the website,
> >so any
> >>> > help is very welcome. It is a little bit messy right now -- there
> >are a
> >>> few
> >>> > outstanding pull requests and forked branches. I'm trying to get
> >all
> >>> this
> >>> > into one place, so anybody can contribute and make progress.
> >>> >
> >>> > Also, the general website organization has been discussed before,
> >see
> >>> this
> >>> > thread [1] and the attached document for details.
> >>> >
> >>> > Davor
> >>> >
> >>> > [1]
> >>> > https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
> >>> > mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
> >>> > mail.gmail.com%3E
> >>> >
> >>> > On Sun, Oct 23, 2016 at 12:34 AM, Jean-Baptiste Onofré
> > >>> >
> >>> > wrote:
> >>> >
> >>> > > Hi
> >>> > >
> >>> > > You can take a look on the PR I creates last Friday. It contains
> >a
> >>> > > CSS/skin proposal.
> >>> > >
> >>> > > The mock-up is there: http://maven.nanthrax.net/beam
> >>> > >
> >>> > > Regards
> >>> > > JB
> >>> > >
> >>> > > ⁣​
> >>> > >
> >>> > > On Oct 23, 2016, 09:27, at 09:27, Abdullah Bashir <
> >>> > mabdullah...@gmail.com>
> >>> > > wrote:
> >>> > > >Hi,
> >>> > > >
> >>> > > >is their any help i can do on website designing ?
> >>> > > >I am good at HTML5, CSS3 and javascript.
> >>> > > >
> >>> > > >Regards,
> >>> > > >Abdullah Bashir
> >>> > >
> >>> >
> >>>
> >>
> >>
>



-- 
*Minudika Malshan*
Undergraduate
Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Hi

You can propose a PR on this Jira.

We will be more than happy to review it.

Thanks
Regards
JB

⁣​

On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir  
wrote:
>Thank you very much for taking time to respond Davor :)
>
>Regarding BEAM-752, i can work on that, i have already built some
>Dataflow
>Piplines on Google Cloud in Python language.
>
>Again Can you tell me where to start for BEAM-752. I am new to ASF
>contribution, so onboarding steps are kind of a black box to me :).
>
>On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci 
>wrote:
>
>> Absolutely!
>>
>> I'm currently reviewing JB's PR #51, and that should go in shortly.
>Within
>> a day or so, I should have a better idea about future work in this
>specific
>> area; please stay tuned.
>>
>> There are also separate things that are ready to be started at any
>time.
>> BEAM-752 comes to mind first. Is this something you'd be interested
>in?
>>
>> On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir
>
>> wrote:
>>
>>> Hi Davor,
>>>
>>> I am done with my local setup to start contributing, I have forked
>and
>>> merged pull request *(**pull/51)* into my  local repo. Then I read
>the
>>>
>>> google docs, their are two tasks mentioned in it, as [Beam-500] and
>>> [Beam-501].
>>> I found out that [Beam-500] is closed in JIRA and [Beam-501] is
>>> assigned to Jean-Baptiste
>>> Onofré, Is their any task that you can assign to me ?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Abdullah Bashir
>>>
>>>
>>> On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci 
>wrote:
>>>
>>> > Abdullah, welcome!
>>> >
>>> > I think it's rather clear we've been struggling with the website,
>so any
>>> > help is very welcome. It is a little bit messy right now -- there
>are a
>>> few
>>> > outstanding pull requests and forked branches. I'm trying to get
>all
>>> this
>>> > into one place, so anybody can contribute and make progress.
>>> >
>>> > Also, the general website organization has been discussed before,
>see
>>> this
>>> > thread [1] and the attached document for details.
>>> >
>>> > Davor
>>> >
>>> > [1]
>>> > https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
>>> > mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
>>> > mail.gmail.com%3E
>>> >
>>> > On Sun, Oct 23, 2016 at 12:34 AM, Jean-Baptiste Onofré
>>> >
>>> > wrote:
>>> >
>>> > > Hi
>>> > >
>>> > > You can take a look on the PR I creates last Friday. It contains
>a
>>> > > CSS/skin proposal.
>>> > >
>>> > > The mock-up is there: http://maven.nanthrax.net/beam
>>> > >
>>> > > Regards
>>> > > JB
>>> > >
>>> > > ⁣​
>>> > >
>>> > > On Oct 23, 2016, 09:27, at 09:27, Abdullah Bashir <
>>> > mabdullah...@gmail.com>
>>> > > wrote:
>>> > > >Hi,
>>> > > >
>>> > > >is their any help i can do on website designing ?
>>> > > >I am good at HTML5, CSS3 and javascript.
>>> > > >
>>> > > >Regards,
>>> > > >Abdullah Bashir
>>> > >
>>> >
>>>
>>
>>

Re: [PROPOSAL] New Beam website design?

[Abdullah Bashir]

Thank you very much for taking time to respond Davor :)

Regarding BEAM-752, i can work on that, i have already built some Dataflow
Piplines on Google Cloud in Python language.

Again Can you tell me where to start for BEAM-752. I am new to ASF
contribution, so onboarding steps are kind of a black box to me :).

On Thu, Oct 27, 2016 at 11:34 AM, Davor Bonaci  wrote:

> Absolutely!
>
> I'm currently reviewing JB's PR #51, and that should go in shortly. Within
> a day or so, I should have a better idea about future work in this specific
> area; please stay tuned.
>
> There are also separate things that are ready to be started at any time.
> BEAM-752 comes to mind first. Is this something you'd be interested in?
>
> On Wed, Oct 26, 2016 at 11:17 PM, Abdullah Bashir 
> wrote:
>
>> Hi Davor,
>>
>> I am done with my local setup to start contributing, I have forked and
>> merged pull request *(**pull/51)* into my  local repo. Then I read the
>>
>> google docs, their are two tasks mentioned in it, as [Beam-500] and
>> [Beam-501].
>> I found out that [Beam-500] is closed in JIRA and [Beam-501] is
>> assigned to Jean-Baptiste
>> Onofré, Is their any task that you can assign to me ?
>>
>> Thanks.
>>
>> Regards,
>> Abdullah Bashir
>>
>>
>> On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci  wrote:
>>
>> > Abdullah, welcome!
>> >
>> > I think it's rather clear we've been struggling with the website, so any
>> > help is very welcome. It is a little bit messy right now -- there are a
>> few
>> > outstanding pull requests and forked branches. I'm trying to get all
>> this
>> > into one place, so anybody can contribute and make progress.
>> >
>> > Also, the general website organization has been discussed before, see
>> this
>> > thread [1] and the attached document for details.
>> >
>> > Davor
>> >
>> > [1]
>> > https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
>> > mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
>> > mail.gmail.com%3E
>> >
>> > On Sun, Oct 23, 2016 at 12:34 AM, Jean-Baptiste Onofré > >
>> > wrote:
>> >
>> > > Hi
>> > >
>> > > You can take a look on the PR I creates last Friday. It contains a
>> > > CSS/skin proposal.
>> > >
>> > > The mock-up is there: http://maven.nanthrax.net/beam
>> > >
>> > > Regards
>> > > JB
>> > >
>> > > ⁣​
>> > >
>> > > On Oct 23, 2016, 09:27, at 09:27, Abdullah Bashir <
>> > mabdullah...@gmail.com>
>> > > wrote:
>> > > >Hi,
>> > > >
>> > > >is their any help i can do on website designing ?
>> > > >I am good at HTML5, CSS3 and javascript.
>> > > >
>> > > >Regards,
>> > > >Abdullah Bashir
>> > >
>> >
>>
>
>

Re: [PROPOSAL] New Beam website design?

[Abdullah Bashir]

Hi Davor,

I am done with my local setup to start contributing, I have forked and
merged pull request *(**pull/51)* into my  local repo. Then I read the
google docs, their are two tasks mentioned in it, as [Beam-500] and
[Beam-501].
I found out that [Beam-500] is closed in JIRA and [Beam-501] is
assigned to Jean-Baptiste
Onofré, Is their any task that you can assign to me ?

Thanks.

Regards,
Abdullah Bashir


On Tue, Oct 25, 2016 at 1:50 AM, Davor Bonaci  wrote:

> Abdullah, welcome!
>
> I think it's rather clear we've been struggling with the website, so any
> help is very welcome. It is a little bit messy right now -- there are a few
> outstanding pull requests and forked branches. I'm trying to get all this
> into one place, so anybody can contribute and make progress.
>
> Also, the general website organization has been discussed before, see this
> thread [1] and the attached document for details.
>
> Davor
>
> [1]
> https://mail-archives.apache.org/mod_mbox/beam-dev/201606.
> mbox/%3CCAAzyFAwu992x+xcxN6Ha-avKZZbF-RK00mUg1-vezYCmtOm4Ww@
> mail.gmail.com%3E
>
> On Sun, Oct 23, 2016 at 12:34 AM, Jean-Baptiste Onofré 
> wrote:
>
> > Hi
> >
> > You can take a look on the PR I creates last Friday. It contains a
> > CSS/skin proposal.
> >
> > The mock-up is there: http://maven.nanthrax.net/beam
> >
> > Regards
> > JB
> >
> > ⁣​
> >
> > On Oct 23, 2016, 09:27, at 09:27, Abdullah Bashir <
> mabdullah...@gmail.com>
> > wrote:
> > >Hi,
> > >
> > >is their any help i can do on website designing ?
> > >I am good at HTML5, CSS3 and javascript.
> > >
> > >Regards,
> > >Abdullah Bashir
> >
>

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Hi James,

just to let you know that I did good progress on the website mockup.

I should be able to propose a PR very soon.

Thanks for your patience ;)

Regards
JB

On 06/06/2016 05:29 PM, James Malone wrote:

Hello everyone!

The current design of the Apache Beam website[1] is based on the a basic
Bootstrap/Jekyll theme. While this made getting an initial site out quickly
pretty easy, the site itself is a little bland (in my opinion :). I propose
we create a new design (layout templates, color schemes, visual design) for
the Beam website.

Since the website is currently using Bootstrap and Jekyll, this should be a
relatively easy process. Getting this done will require a new design and
some CSS/HTML work. Additionally, before a design is put in place, I think
it makes sense to discuss any ideas about a future design first.

So, I think there are two open questions behind this proposal:

1. Is there anyone within the community who would be interested in creating
a design proposal or two and sharing them with the community?
2. Are there any ideas, opinions, and thoughts around what the design of
the site *should* be?

What does everyone think?

Cheers!

James

[1]: http://beam.incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] New Beam website design?

[James Malone]

Awesome! If you need or want any help on other styling (like docs and such)
let me know - I am happy to help!

James

On Wed, Oct 5, 2016 at 11:33 PM, Jean-Baptiste Onofré 
wrote:

> Hi
>
> For the website I already proposed a new design and css:
> http://maven.nanthrax.net/beam/
>
> I plan to provide a PR very soon.
>
> I'm late on that.
>
> Regards
> JB
>
>
>
> On Oct 5, 2016, 20:21, at 20:21, James Malone 
> wrote:
> >Hi all!
> >
> >I want to revive this thread if I may. Is there any way I can help on
> >the
> >website redesign? Additionally, is anyone currently working on the
> >UI/UX
> >design? I want to make sure I don't duplicate any work.
> >
> >Cheers!
> >
> >James
> >
> >On Tue, Aug 2, 2016 at 1:41 PM, Frances Perry 
> >wrote:
> >
> >> Just an update for everyone...
> >>
> >> The new website navigation structure is roughly in place. However
> >there's
> >> still work remaining to fill in the pages with the right content.
> >There are
> >> bugs in JIRA tracking the major gaps.
> >>
> >> In addition, JB is working on new CSS to give our site a snazzier
> >look ;-)
> >>
> >> On Thu, Jun 16, 2016 at 10:11 PM, Jean-Baptiste Onofré
> >
> >> wrote:
> >>
> >> > Good point. It make sense to wait that it's actually implemented
> >and
> >> > available before putting on the website.
> >> >
> >> > Thanks !
> >> > Regards
> >> > JB
> >> >
> >> >
> >> > On 06/17/2016 07:01 AM, Frances Perry wrote:
> >> >
> >> >> Good thoughts.
> >> >>
> >> >> There'll be a section on IO that comes over as part of the
> >programming
> >> >> guide being ported from the Cloud Dataflow docs. Hopefully that
> >has the
> >> >> technical info needed. Once we see how that's structured (Devin is
> >still
> >> >> playing around with a single page or multiple), then we can decide
> >if we
> >> >> need to make it more visible. Maybe we should add a summary table
> >to the
> >> >> overview page too?
> >> >>
> >> >> As for DSLs, I think it remains to be seen how we tightly we
> >choose to
> >> >> integrate them into Beam. As we've started discussing before, we
> >may
> >> >> decide
> >> >> that some of them belong elsewhere because they change the
> >user-visible
> >> >> concepts, but should be discoverable from our documentation. Or
> >others
> >> may
> >> >> more closely align and just expose subsets. But in any case --
> >totally
> >> >> agree we should add the right concepts when we cross that bridge.
> >> >>
> >> >>
> >> >>
> >> >> On Thu, Jun 16, 2016 at 9:53 PM, Jean-Baptiste Onofré
> >
> >> >> wrote:
> >> >>
> >> >> Hi Frances,
> >> >>>
> >> >>> great doc !
> >> >>>
> >> >>> Maybe in the "Learn" section, we can also add IOs (like SDKs, and
> >> >>> runners), like we do in Camel
> >(http://camel.apache.org/components.html
> >> )
> >> >>> For the SDKs, I would also add DSLs in the same section.
> >> >>>
> >> >>> WDYT ?
> >> >>>
> >> >>> Regards
> >> >>> JB
> >> >>>
> >> >>>
> >> >>> On 06/17/2016 12:21 AM, Frances Perry wrote:
> >> >>>
> >> >>> Good point, JB -- let's redo the page layout as well.
> >> 
> >>  I started with your proposal and tweaked it a bit to add in more
> >> details
> >>  and divide things a bit more according to use case (end user vs.
> >>  runner/sdk
> >>  developer):
> >> 
> >> 
> >>  https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_
> >> qjBYeNMLm2LusYF3gQ/edit
> >> 
> >>  Let me know what you think, and what part you'd like to drive!
> >I'd
> >>  suggest
> >>  we get the new section layout set this week, so we can
> >parallelize
> >> site
> >>  design and assorted page content.
> >> 
> >>  On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré
> > >> >
> >>  wrote:
> >> 
> >>  Hi James,
> >> 
> >> >
> >> > very good idea !
> >> >
> >> > Couple of month ago, I completely revamped the Karaf website:
> >> >
> >> > http://karaf.apache.org/
> >> >
> >> > It could be a good skeleton in term of sections/pages.
> >> >
> >> > IMHO, for Beam, at least for the home page, we should have:
> >> > 1. a clear message about what Beam is from an user perspective:
> >why
> >> > should
> >> > I use Beam and write pipelines, what's the value, etc. The
> >runner
> >> > writers,
> >> > or DSL writers will find their resources but not on the
> >homepage (on
> >> > dedicated section of the website).
> >> >
> >> > In term of sections, we could propose
> >> > 1.1. Overview (with the three perspective/type of users)
> >> > 1.2. Libraries: SDKs, DSLs, IOs, Runners
> >> > 1.3. Documentation: Dev Guide, Samples, Runners Writer guide,
> >...
> >> > 1.4. Community: mailing list, contribution guide, ...
> >> > 1.5. Apache (link to ASF)
> >> >
> >> > 2. a look'n feel should be clean and professional, at least for
> >the
> >> > 

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Hi

For the website I already proposed a new design and css: 
http://maven.nanthrax.net/beam/

I plan to provide a PR very soon.

I'm late on that.

Regards
JB



On Oct 5, 2016, 20:21, at 20:21, James Malone  
wrote:
>Hi all!
>
>I want to revive this thread if I may. Is there any way I can help on
>the
>website redesign? Additionally, is anyone currently working on the
>UI/UX
>design? I want to make sure I don't duplicate any work.
>
>Cheers!
>
>James
>
>On Tue, Aug 2, 2016 at 1:41 PM, Frances Perry 
>wrote:
>
>> Just an update for everyone...
>>
>> The new website navigation structure is roughly in place. However
>there's
>> still work remaining to fill in the pages with the right content.
>There are
>> bugs in JIRA tracking the major gaps.
>>
>> In addition, JB is working on new CSS to give our site a snazzier
>look ;-)
>>
>> On Thu, Jun 16, 2016 at 10:11 PM, Jean-Baptiste Onofré
>
>> wrote:
>>
>> > Good point. It make sense to wait that it's actually implemented
>and
>> > available before putting on the website.
>> >
>> > Thanks !
>> > Regards
>> > JB
>> >
>> >
>> > On 06/17/2016 07:01 AM, Frances Perry wrote:
>> >
>> >> Good thoughts.
>> >>
>> >> There'll be a section on IO that comes over as part of the
>programming
>> >> guide being ported from the Cloud Dataflow docs. Hopefully that
>has the
>> >> technical info needed. Once we see how that's structured (Devin is
>still
>> >> playing around with a single page or multiple), then we can decide
>if we
>> >> need to make it more visible. Maybe we should add a summary table
>to the
>> >> overview page too?
>> >>
>> >> As for DSLs, I think it remains to be seen how we tightly we
>choose to
>> >> integrate them into Beam. As we've started discussing before, we
>may
>> >> decide
>> >> that some of them belong elsewhere because they change the
>user-visible
>> >> concepts, but should be discoverable from our documentation. Or
>others
>> may
>> >> more closely align and just expose subsets. But in any case --
>totally
>> >> agree we should add the right concepts when we cross that bridge.
>> >>
>> >>
>> >>
>> >> On Thu, Jun 16, 2016 at 9:53 PM, Jean-Baptiste Onofré
>
>> >> wrote:
>> >>
>> >> Hi Frances,
>> >>>
>> >>> great doc !
>> >>>
>> >>> Maybe in the "Learn" section, we can also add IOs (like SDKs, and
>> >>> runners), like we do in Camel
>(http://camel.apache.org/components.html
>> )
>> >>> For the SDKs, I would also add DSLs in the same section.
>> >>>
>> >>> WDYT ?
>> >>>
>> >>> Regards
>> >>> JB
>> >>>
>> >>>
>> >>> On 06/17/2016 12:21 AM, Frances Perry wrote:
>> >>>
>> >>> Good point, JB -- let's redo the page layout as well.
>> 
>>  I started with your proposal and tweaked it a bit to add in more
>> details
>>  and divide things a bit more according to use case (end user vs.
>>  runner/sdk
>>  developer):
>> 
>> 
>>  https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_
>> qjBYeNMLm2LusYF3gQ/edit
>> 
>>  Let me know what you think, and what part you'd like to drive!
>I'd
>>  suggest
>>  we get the new section layout set this week, so we can
>parallelize
>> site
>>  design and assorted page content.
>> 
>>  On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré
>> >
>>  wrote:
>> 
>>  Hi James,
>> 
>> >
>> > very good idea !
>> >
>> > Couple of month ago, I completely revamped the Karaf website:
>> >
>> > http://karaf.apache.org/
>> >
>> > It could be a good skeleton in term of sections/pages.
>> >
>> > IMHO, for Beam, at least for the home page, we should have:
>> > 1. a clear message about what Beam is from an user perspective:
>why
>> > should
>> > I use Beam and write pipelines, what's the value, etc. The
>runner
>> > writers,
>> > or DSL writers will find their resources but not on the
>homepage (on
>> > dedicated section of the website).
>> >
>> > In term of sections, we could propose
>> > 1.1. Overview (with the three perspective/type of users)
>> > 1.2. Libraries: SDKs, DSLs, IOs, Runners
>> > 1.3. Documentation: Dev Guide, Samples, Runners Writer guide,
>...
>> > 1.4. Community: mailing list, contribution guide, ...
>> > 1.5. Apache (link to ASF)
>> >
>> > 2. a look'n feel should be clean and professional, at least for
>the
>> > home
>> > page.
>> >
>> > I would love to help here !
>> >
>> > Regards
>> > JB
>> >
>> >
>> > On 06/06/2016 05:29 PM, James Malone wrote:
>> >
>> > Hello everyone!
>> >
>> >>
>> >> The current design of the Apache Beam website[1] is based on
>the a
>> >> basic
>> >> Bootstrap/Jekyll theme. While this made getting an initial
>site out
>> >> quickly
>> >> pretty easy, the site itself is a little bland (in my opinion
>:). I
>> >> propose
>> 

Re: [PROPOSAL] New Beam website design?

[Frances Perry]

On Wed, Oct 5, 2016 at 3:51 PM, Kenneth Knowles 
wrote:

> Just because the thread got bumped... I kind of miss the old bucket of
> technical docs. They aren't user-facing, but I used it quite a lot. Perhaps
> instead of deleting it, move from "Learn" to "Contribute" or bury it
> somewhere near the bottom of the contributors' guide?
>

My thinking in pull/42 is that the shared Google Drive folder morphs into a
combination of additional webpages / direct links in the contributor hub
with the well known / agreed on information (always kept up to date) and
the new proposal workflow in jira to make ongoing designs easily
discoverable. The benefits over a single shared folder are that (1) there
are no additional permissions to wrangle, (2) it makes everything available
from a single place instead of organizing information based on what format
it's in, and (3) we are less likely to end up with a bucket of outdated
information. But given that it will take us a while to things moved around,
I'll add it in pull/42.


>
> On Wed, Oct 5, 2016 at 11:21 AM James Malone  invalid>
> wrote:
>
> > Hi all!
> >
> > I want to revive this thread if I may. Is there any way I can help on the
> > website redesign? Additionally, is anyone currently working on the UI/UX
> > design? I want to make sure I don't duplicate any work.
> >
> > Cheers!
> >
> > James
> >
> > On Tue, Aug 2, 2016 at 1:41 PM, Frances Perry 
> > wrote:
> >
> > > Just an update for everyone...
> > >
> > > The new website navigation structure is roughly in place. However
> there's
> > > still work remaining to fill in the pages with the right content. There
> > are
> > > bugs in JIRA tracking the major gaps.
> > >
> > > In addition, JB is working on new CSS to give our site a snazzier look
> > ;-)
> > >
> > > On Thu, Jun 16, 2016 at 10:11 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > > wrote:
> > >
> > > > Good point. It make sense to wait that it's actually implemented and
> > > > available before putting on the website.
> > > >
> > > > Thanks !
> > > > Regards
> > > > JB
> > > >
> > > >
> > > > On 06/17/2016 07:01 AM, Frances Perry wrote:
> > > >
> > > >> Good thoughts.
> > > >>
> > > >> There'll be a section on IO that comes over as part of the
> programming
> > > >> guide being ported from the Cloud Dataflow docs. Hopefully that has
> > the
> > > >> technical info needed. Once we see how that's structured (Devin is
> > still
> > > >> playing around with a single page or multiple), then we can decide
> if
> > we
> > > >> need to make it more visible. Maybe we should add a summary table to
> > the
> > > >> overview page too?
> > > >>
> > > >> As for DSLs, I think it remains to be seen how we tightly we choose
> to
> > > >> integrate them into Beam. As we've started discussing before, we may
> > > >> decide
> > > >> that some of them belong elsewhere because they change the
> > user-visible
> > > >> concepts, but should be discoverable from our documentation. Or
> others
> > > may
> > > >> more closely align and just expose subsets. But in any case --
> totally
> > > >> agree we should add the right concepts when we cross that bridge.
> > > >>
> > > >>
> > > >>
> > > >> On Thu, Jun 16, 2016 at 9:53 PM, Jean-Baptiste Onofré <
> > j...@nanthrax.net>
> > > >> wrote:
> > > >>
> > > >> Hi Frances,
> > > >>>
> > > >>> great doc !
> > > >>>
> > > >>> Maybe in the "Learn" section, we can also add IOs (like SDKs, and
> > > >>> runners), like we do in Camel (
> > http://camel.apache.org/components.html
> > > )
> > > >>> For the SDKs, I would also add DSLs in the same section.
> > > >>>
> > > >>> WDYT ?
> > > >>>
> > > >>> Regards
> > > >>> JB
> > > >>>
> > > >>>
> > > >>> On 06/17/2016 12:21 AM, Frances Perry wrote:
> > > >>>
> > > >>> Good point, JB -- let's redo the page layout as well.
> > > 
> > >  I started with your proposal and tweaked it a bit to add in more
> > > details
> > >  and divide things a bit more according to use case (end user vs.
> > >  runner/sdk
> > >  developer):
> > > 
> > > 
> > >  https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_
> > > qjBYeNMLm2LusYF3gQ/edit
> > > 
> > >  Let me know what you think, and what part you'd like to drive! I'd
> > >  suggest
> > >  we get the new section layout set this week, so we can parallelize
> > > site
> > >  design and assorted page content.
> > > 
> > >  On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré <
> > j...@nanthrax.net
> > > >
> > >  wrote:
> > > 
> > >  Hi James,
> > > 
> > > >
> > > > very good idea !
> > > >
> > > > Couple of month ago, I completely revamped the Karaf website:
> > > >
> > > > http://karaf.apache.org/
> > > >
> > > > It could be a good skeleton in term of sections/pages.
> > > >
> > > > IMHO, for Beam, at least for the home page, we should have:
> > > > 1. a clear 

Re: [PROPOSAL] New Beam website design?

[Kenneth Knowles]

Just because the thread got bumped... I kind of miss the old bucket of
technical docs. They aren't user-facing, but I used it quite a lot. Perhaps
instead of deleting it, move from "Learn" to "Contribute" or bury it
somewhere near the bottom of the contributors' guide?

On Wed, Oct 5, 2016 at 11:21 AM James Malone 
wrote:

> Hi all!
>
> I want to revive this thread if I may. Is there any way I can help on the
> website redesign? Additionally, is anyone currently working on the UI/UX
> design? I want to make sure I don't duplicate any work.
>
> Cheers!
>
> James
>
> On Tue, Aug 2, 2016 at 1:41 PM, Frances Perry 
> wrote:
>
> > Just an update for everyone...
> >
> > The new website navigation structure is roughly in place. However there's
> > still work remaining to fill in the pages with the right content. There
> are
> > bugs in JIRA tracking the major gaps.
> >
> > In addition, JB is working on new CSS to give our site a snazzier look
> ;-)
> >
> > On Thu, Jun 16, 2016 at 10:11 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> > > Good point. It make sense to wait that it's actually implemented and
> > > available before putting on the website.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > >
> > > On 06/17/2016 07:01 AM, Frances Perry wrote:
> > >
> > >> Good thoughts.
> > >>
> > >> There'll be a section on IO that comes over as part of the programming
> > >> guide being ported from the Cloud Dataflow docs. Hopefully that has
> the
> > >> technical info needed. Once we see how that's structured (Devin is
> still
> > >> playing around with a single page or multiple), then we can decide if
> we
> > >> need to make it more visible. Maybe we should add a summary table to
> the
> > >> overview page too?
> > >>
> > >> As for DSLs, I think it remains to be seen how we tightly we choose to
> > >> integrate them into Beam. As we've started discussing before, we may
> > >> decide
> > >> that some of them belong elsewhere because they change the
> user-visible
> > >> concepts, but should be discoverable from our documentation. Or others
> > may
> > >> more closely align and just expose subsets. But in any case -- totally
> > >> agree we should add the right concepts when we cross that bridge.
> > >>
> > >>
> > >>
> > >> On Thu, Jun 16, 2016 at 9:53 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > >> wrote:
> > >>
> > >> Hi Frances,
> > >>>
> > >>> great doc !
> > >>>
> > >>> Maybe in the "Learn" section, we can also add IOs (like SDKs, and
> > >>> runners), like we do in Camel (
> http://camel.apache.org/components.html
> > )
> > >>> For the SDKs, I would also add DSLs in the same section.
> > >>>
> > >>> WDYT ?
> > >>>
> > >>> Regards
> > >>> JB
> > >>>
> > >>>
> > >>> On 06/17/2016 12:21 AM, Frances Perry wrote:
> > >>>
> > >>> Good point, JB -- let's redo the page layout as well.
> > 
> >  I started with your proposal and tweaked it a bit to add in more
> > details
> >  and divide things a bit more according to use case (end user vs.
> >  runner/sdk
> >  developer):
> > 
> > 
> >  https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_
> > qjBYeNMLm2LusYF3gQ/edit
> > 
> >  Let me know what you think, and what part you'd like to drive! I'd
> >  suggest
> >  we get the new section layout set this week, so we can parallelize
> > site
> >  design and assorted page content.
> > 
> >  On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré <
> j...@nanthrax.net
> > >
> >  wrote:
> > 
> >  Hi James,
> > 
> > >
> > > very good idea !
> > >
> > > Couple of month ago, I completely revamped the Karaf website:
> > >
> > > http://karaf.apache.org/
> > >
> > > It could be a good skeleton in term of sections/pages.
> > >
> > > IMHO, for Beam, at least for the home page, we should have:
> > > 1. a clear message about what Beam is from an user perspective: why
> > > should
> > > I use Beam and write pipelines, what's the value, etc. The runner
> > > writers,
> > > or DSL writers will find their resources but not on the homepage
> (on
> > > dedicated section of the website).
> > >
> > > In term of sections, we could propose
> > > 1.1. Overview (with the three perspective/type of users)
> > > 1.2. Libraries: SDKs, DSLs, IOs, Runners
> > > 1.3. Documentation: Dev Guide, Samples, Runners Writer guide, ...
> > > 1.4. Community: mailing list, contribution guide, ...
> > > 1.5. Apache (link to ASF)
> > >
> > > 2. a look'n feel should be clean and professional, at least for the
> > > home
> > > page.
> > >
> > > I would love to help here !
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 06/06/2016 05:29 PM, James Malone wrote:
> > >
> > > Hello everyone!
> > >
> > >>
> > >> The current design of the Apache Beam website[1] 

Re: [PROPOSAL] New Beam website design?

[Frances Perry]

Good thoughts.

There'll be a section on IO that comes over as part of the programming
guide being ported from the Cloud Dataflow docs. Hopefully that has the
technical info needed. Once we see how that's structured (Devin is still
playing around with a single page or multiple), then we can decide if we
need to make it more visible. Maybe we should add a summary table to the
overview page too?

As for DSLs, I think it remains to be seen how we tightly we choose to
integrate them into Beam. As we've started discussing before, we may decide
that some of them belong elsewhere because they change the user-visible
concepts, but should be discoverable from our documentation. Or others may
more closely align and just expose subsets. But in any case -- totally
agree we should add the right concepts when we cross that bridge.



On Thu, Jun 16, 2016 at 9:53 PM, Jean-Baptiste Onofré 
wrote:

> Hi Frances,
>
> great doc !
>
> Maybe in the "Learn" section, we can also add IOs (like SDKs, and
> runners), like we do in Camel (http://camel.apache.org/components.html)
> For the SDKs, I would also add DSLs in the same section.
>
> WDYT ?
>
> Regards
> JB
>
>
> On 06/17/2016 12:21 AM, Frances Perry wrote:
>
>> Good point, JB -- let's redo the page layout as well.
>>
>> I started with your proposal and tweaked it a bit to add in more details
>> and divide things a bit more according to use case (end user vs.
>> runner/sdk
>> developer):
>>
>> https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_qjBYeNMLm2LusYF3gQ/edit
>>
>> Let me know what you think, and what part you'd like to drive! I'd suggest
>> we get the new section layout set this week, so we can parallelize site
>> design and assorted page content.
>>
>> On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré 
>> wrote:
>>
>> Hi James,
>>>
>>> very good idea !
>>>
>>> Couple of month ago, I completely revamped the Karaf website:
>>>
>>> http://karaf.apache.org/
>>>
>>> It could be a good skeleton in term of sections/pages.
>>>
>>> IMHO, for Beam, at least for the home page, we should have:
>>> 1. a clear message about what Beam is from an user perspective: why
>>> should
>>> I use Beam and write pipelines, what's the value, etc. The runner
>>> writers,
>>> or DSL writers will find their resources but not on the homepage (on
>>> dedicated section of the website).
>>>
>>> In term of sections, we could propose
>>> 1.1. Overview (with the three perspective/type of users)
>>> 1.2. Libraries: SDKs, DSLs, IOs, Runners
>>> 1.3. Documentation: Dev Guide, Samples, Runners Writer guide, ...
>>> 1.4. Community: mailing list, contribution guide, ...
>>> 1.5. Apache (link to ASF)
>>>
>>> 2. a look'n feel should be clean and professional, at least for the home
>>> page.
>>>
>>> I would love to help here !
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 06/06/2016 05:29 PM, James Malone wrote:
>>>
>>> Hello everyone!

 The current design of the Apache Beam website[1] is based on the a basic
 Bootstrap/Jekyll theme. While this made getting an initial site out
 quickly
 pretty easy, the site itself is a little bland (in my opinion :). I
 propose
 we create a new design (layout templates, color schemes, visual design)
 for
 the Beam website.

 Since the website is currently using Bootstrap and Jekyll, this should
 be
 a
 relatively easy process. Getting this done will require a new design and
 some CSS/HTML work. Additionally, before a design is put in place, I
 think
 it makes sense to discuss any ideas about a future design first.

 So, I think there are two open questions behind this proposal:

 1. Is there anyone within the community who would be interested in
 creating
 a design proposal or two and sharing them with the community?
 2. Are there any ideas, opinions, and thoughts around what the design of
 the site *should* be?

 What does everyone think?

 Cheers!

 James

 [1]: http://beam.incubator.apache.org


 --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Hi Frances,

great doc !

Maybe in the "Learn" section, we can also add IOs (like SDKs, and 
runners), like we do in Camel (http://camel.apache.org/components.html) 
For the SDKs, I would also add DSLs in the same section.


WDYT ?

Regards
JB

On 06/17/2016 12:21 AM, Frances Perry wrote:

Good point, JB -- let's redo the page layout as well.

I started with your proposal and tweaked it a bit to add in more details
and divide things a bit more according to use case (end user vs. runner/sdk
developer):
https://docs.google.com/document/d/1-0jMv7NnYp0Ttt4voulUMwVe_qjBYeNMLm2LusYF3gQ/edit

Let me know what you think, and what part you'd like to drive! I'd suggest
we get the new section layout set this week, so we can parallelize site
design and assorted page content.

On Mon, Jun 6, 2016 at 8:38 AM, Jean-Baptiste Onofré 
wrote:


Hi James,

very good idea !

Couple of month ago, I completely revamped the Karaf website:

http://karaf.apache.org/

It could be a good skeleton in term of sections/pages.

IMHO, for Beam, at least for the home page, we should have:
1. a clear message about what Beam is from an user perspective: why should
I use Beam and write pipelines, what's the value, etc. The runner writers,
or DSL writers will find their resources but not on the homepage (on
dedicated section of the website).

In term of sections, we could propose
1.1. Overview (with the three perspective/type of users)
1.2. Libraries: SDKs, DSLs, IOs, Runners
1.3. Documentation: Dev Guide, Samples, Runners Writer guide, ...
1.4. Community: mailing list, contribution guide, ...
1.5. Apache (link to ASF)

2. a look'n feel should be clean and professional, at least for the home
page.

I would love to help here !

Regards
JB


On 06/06/2016 05:29 PM, James Malone wrote:


Hello everyone!

The current design of the Apache Beam website[1] is based on the a basic
Bootstrap/Jekyll theme. While this made getting an initial site out
quickly
pretty easy, the site itself is a little bland (in my opinion :). I
propose
we create a new design (layout templates, color schemes, visual design)
for
the Beam website.

Since the website is currently using Bootstrap and Jekyll, this should be
a
relatively easy process. Getting this done will require a new design and
some CSS/HTML work. Additionally, before a design is put in place, I think
it makes sense to discuss any ideas about a future design first.

So, I think there are two open questions behind this proposal:

1. Is there anyone within the community who would be interested in
creating
a design proposal or two and sharing them with the community?
2. Are there any ideas, opinions, and thoughts around what the design of
the site *should* be?

What does everyone think?

Cheers!

James

[1]: http://beam.incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] New Beam website design?

[Jean-Baptiste Onofré]

Hi James,

very good idea !

Couple of month ago, I completely revamped the Karaf website:

http://karaf.apache.org/

It could be a good skeleton in term of sections/pages.

IMHO, for Beam, at least for the home page, we should have:
1. a clear message about what Beam is from an user perspective: why 
should I use Beam and write pipelines, what's the value, etc. The runner 
writers, or DSL writers will find their resources but not on the 
homepage (on dedicated section of the website).


In term of sections, we could propose
1.1. Overview (with the three perspective/type of users)
1.2. Libraries: SDKs, DSLs, IOs, Runners
1.3. Documentation: Dev Guide, Samples, Runners Writer guide, ...
1.4. Community: mailing list, contribution guide, ...
1.5. Apache (link to ASF)

2. a look'n feel should be clean and professional, at least for the home 
page.


I would love to help here !

Regards
JB

On 06/06/2016 05:29 PM, James Malone wrote:

Hello everyone!

The current design of the Apache Beam website[1] is based on the a basic
Bootstrap/Jekyll theme. While this made getting an initial site out quickly
pretty easy, the site itself is a little bland (in my opinion :). I propose
we create a new design (layout templates, color schemes, visual design) for
the Beam website.

Since the website is currently using Bootstrap and Jekyll, this should be a
relatively easy process. Getting this done will require a new design and
some CSS/HTML work. Additionally, before a design is put in place, I think
it makes sense to discuss any ideas about a future design first.

So, I think there are two open questions behind this proposal:

1. Is there anyone within the community who would be interested in creating
a design proposal or two and sharing them with the community?
2. Are there any ideas, opinions, and thoughts around what the design of
the site *should* be?

What does everyone think?

Cheers!

James

[1]: http://beam.incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

[PROPOSAL] New Beam website design?

[James Malone]

Hello everyone!

The current design of the Apache Beam website[1] is based on the a basic
Bootstrap/Jekyll theme. While this made getting an initial site out quickly
pretty easy, the site itself is a little bland (in my opinion :). I propose
we create a new design (layout templates, color schemes, visual design) for
the Beam website.

Since the website is currently using Bootstrap and Jekyll, this should be a
relatively easy process. Getting this done will require a new design and
some CSS/HTML work. Additionally, before a design is put in place, I think
it makes sense to discuss any ideas about a future design first.

So, I think there are two open questions behind this proposal:

1. Is there anyone within the community who would be interested in creating
a design proposal or two and sharing them with the community?
2. Are there any ideas, opinions, and thoughts around what the design of
the site *should* be?

What does everyone think?

Cheers!

James

[1]: http://beam.incubator.apache.org

Re: New beam website!

[Maximilian Michels]

Hi JB,

I've pushed the web site to the empty repository and I'll tell Infra
to switch to the new repository.

Cheers,
Max


On Fri, Mar 4, 2016 at 5:00 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> Hi Max,
>
> fair enough.
>
> Regards
> JB
>
>
> On 03/04/2016 03:52 PM, Maximilian Michels wrote:
>>
>> Hi JB,
>>
>> Good question. I didn't create the page but one problem about relative
>> URLs is changing the root directory or switching to https. So instead
>> of relative URLs which should use {{ site.baseurl }}/resource for all
>> links. That way, we can simply change baseurl in the _config.yml and
>> we're good to go. For local testing, we set jekyll --baseurl "". That
>> approach has worked well for the Flink website which is also built
>> with Jekyll.
>>
>> Cheers,
>> Max
>>
>> On Fri, Mar 4, 2016 at 1:48 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
>> wrote:
>>>
>>> Hi Max,
>>>
>>> I just cloned your repo and built using jekyll.
>>>
>>> I just wonder why not using relative URL (for images and js location)
>>> instead of absolute ? It would allow us to directly open the website in a
>>> browser. WDYT ?
>>>
>>> Regards
>>> JB
>>>
>>> On 03/01/2016 01:59 PM, Maximilian Michels wrote:
>>>>
>>>>
>>>> As a summary from
>>>> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11318
>>>> it would work as follows:
>>>>
>>>> We use the 'asf-site' branch of the repository. When we change the
>>>> website, we execute "jekyll build" followed by "jekyll serve" to
>>>> preview the site. Everything is generated in the 'content' directory.
>>>> We then push the changes and they are deployed.
>>>>
>>>> I've prepared everything in my fork:
>>>> https://github.com/mxm/beam-site/tree/asf-site
>>>>
>>>> Unfortunately, I couldn't push the changes to the new repository. The
>>>> permissions don't seem to be set up correctly.
>>>>
>>>> On Tue, Mar 1, 2016 at 10:24 AM, Maximilian Michels <m...@apache.org>
>>>> wrote:
>>>>>
>>>>>
>>>>> Quick update. The Git repository is ready under
>>>>> https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git
>>>>>
>>>>> I'm sorting out the last things and will push the website thereafter.
>>>>> Infra can then proceed to do the pubsub switch to deploy the website
>>>>> from there.
>>>>>
>>>>> On Thu, Feb 25, 2016 at 11:31 PM, Maximilian Michels <m...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi JB,
>>>>>>
>>>>>> Greetings to Mexico! I was using Infra's "SVN to Git migration"
>>>>>> service desk. That seems like a standard way for migration to me. It
>>>>>> has also worked fine in the past.
>>>>>>
>>>>>> Could you explain the role of the SCM-Publish Maven plugin? What would
>>>>>> be different from just committing the changes of the website to the
>>>>>> Git/SVN repository? Is it necessary that people use another wrapper
>>>>>> around a version control system?
>>>>>>
>>>>>> After all, what counts is that we can use a Git repository to check in
>>>>>> website changes and use the GitHub mirror. That is not only much
>>>>>> faster (pushing in SVN takes a long time and there is no local
>>>>>> repository) but also more convenient for most people that use Git on a
>>>>>> daily basis. How the actual website is served, shouldn't matter to the
>>>>>> developer.
>>>>>>
>>>>>> Cheers,
>>>>>> Max
>>>>>>
>>>>>> On Thu, Feb 25, 2016 at 11:23 PM, Jean-Baptiste Onofré
>>>>>> <j...@nanthrax.net>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I agree and it's what we have: the website sources are on my github
>>>>>>> and
>>>>>>> we will move it on apache git. Anyway the source is not where you
>>>>>>> promote
>>>>>>> with the scm-pub

Re: New beam website!

[Jean-Baptiste Onofré]

Hi Max,

fair enough.

Regards
JB

On 03/04/2016 03:52 PM, Maximilian Michels wrote:

Hi JB,

Good question. I didn't create the page but one problem about relative
URLs is changing the root directory or switching to https. So instead
of relative URLs which should use {{ site.baseurl }}/resource for all
links. That way, we can simply change baseurl in the _config.yml and
we're good to go. For local testing, we set jekyll --baseurl "". That
approach has worked well for the Flink website which is also built
with Jekyll.

Cheers,
Max

On Fri, Mar 4, 2016 at 1:48 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

Hi Max,

I just cloned your repo and built using jekyll.

I just wonder why not using relative URL (for images and js location)
instead of absolute ? It would allow us to directly open the website in a
browser. WDYT ?

Regards
JB

On 03/01/2016 01:59 PM, Maximilian Michels wrote:


As a summary from
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11318
it would work as follows:

We use the 'asf-site' branch of the repository. When we change the
website, we execute "jekyll build" followed by "jekyll serve" to
preview the site. Everything is generated in the 'content' directory.
We then push the changes and they are deployed.

I've prepared everything in my fork:
https://github.com/mxm/beam-site/tree/asf-site

Unfortunately, I couldn't push the changes to the new repository. The
permissions don't seem to be set up correctly.

On Tue, Mar 1, 2016 at 10:24 AM, Maximilian Michels <m...@apache.org>
wrote:


Quick update. The Git repository is ready under
https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git

I'm sorting out the last things and will push the website thereafter.
Infra can then proceed to do the pubsub switch to deploy the website
from there.

On Thu, Feb 25, 2016 at 11:31 PM, Maximilian Michels <m...@apache.org>
wrote:


Hi JB,

Greetings to Mexico! I was using Infra's "SVN to Git migration"
service desk. That seems like a standard way for migration to me. It
has also worked fine in the past.

Could you explain the role of the SCM-Publish Maven plugin? What would
be different from just committing the changes of the website to the
Git/SVN repository? Is it necessary that people use another wrapper
around a version control system?

After all, what counts is that we can use a Git repository to check in
website changes and use the GitHub mirror. That is not only much
faster (pushing in SVN takes a long time and there is no local
repository) but also more convenient for most people that use Git on a
daily basis. How the actual website is served, shouldn't matter to the
developer.

Cheers,
Max

On Thu, Feb 25, 2016 at 11:23 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:




I agree and it's what we have: the website sources are on my github and
we will move it on apache git. Anyway the source is not where you promote
with the scm-publish. The PR or patches are not created based on the
"resulting" location (on svn now) but on the sources (on my github now).
That's why I didn't understand the jira.
I don't mind to move the "resulting/promotion" location from svn to
git, but I don't see how it changes for the devs. It would be exactly the
same workflow  (using the scm-publish plugin).
Regards JB


Sent from my Samsung device

 Original message 
From: James Malone <jamesmal...@google.com.INVALID>
Date: 25/02/2016  21:38  (GMT+01:00)
To: dev@beam.incubator.apache.org
Subject: Re: New beam website!

I'll chime in here - I'd greatly prefer a git-based repo for the
website.
If nothing else, it's what many of the committers on our side are
familiar
with.

Cheers!

James

On Thu, Feb 25, 2016 at 10:49 AM, Henry Saputra
<henry.sapu...@gmail.com>
wrote:


Hi JB,

ASF infra now offer Git pubsub to support website source code [1]

I think this is what Max was trying to enable so instead of using svn
for
website it will be using Git that also allow pubsub to publish it.

- Henry

[1] https://blogs.apache.org/infra/entry/git_based_websites_available

On Thu, Feb 25, 2016 at 4:38 AM, Jean-Baptiste Onofré
<j...@nanthrax.net>
wrote:




Hi guys
Max your jira doesn't make sense imho: the svn for the website is for
pubsub, it's not where the website source has to be located. The
website
can be on git or where ever you want but the scm-publish has to be on


svn.


Please close your jira and wait when I'm back to deal with that.
Regards JB from Mexico ;)


Sent from my Samsung device

 Original message 
From: Maximilian Michels <m...@apache.org>
Date: 25/02/2016  10:43  (GMT+01:00)
To: dev@beam.incubator.apache.org
Subject: Re: New beam website!

Alright, I've asked the Infra team to migrate the repository to Git
and setup a GitHub sync.

Git migration:

https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11318
GitHub sync:

http

Re: New beam website!

[Jean-Baptiste Onofré]

Hi guys
Max your jira doesn't make sense imho: the svn for the website is for pubsub, 
it's not where the website source has to be located. The website can be on git 
or where ever you want but the scm-publish has to be on svn.
Please close your jira and wait when I'm back to deal with that.
Regards JB from Mexico ;)


Sent from my Samsung device

 Original message 
From: Maximilian Michels <m...@apache.org> 
Date: 25/02/2016  10:43  (GMT+01:00) 
To: dev@beam.incubator.apache.org 
Subject: Re: New beam website! 

Alright, I've asked the Infra team to migrate the repository to Git
and setup a GitHub sync.

Git migration: 
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11318
GitHub sync: 
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11319

Cheers,
Max

On Wed, Feb 24, 2016 at 9:00 PM, James Malone
<jamesmal...@google.com.invalid> wrote:
> That would be awesome. Full disclosure - I 
> Happy to help however I can and any experience anyone has for making that
> happen is welcomed. :)
>
> On Wed, Feb 24, 2016 at 9:05 AM, Maximilian Michels <m...@apache.org> wrote:
>
>> Hi James,
>>
>> The updated website looks good to me. I agree that it will simplify
>> work for a lot of people who are used to Jekyll.
>>
>> The website is already in the SVN repository. After we have sorted out
>> the CCLAs, the only thing that is left is a GitHub sync to make it
>> more accessible for contributors. The prerequisite for that is that we
>> change it to Git. Apache Infra can do that (we have done likewise for
>> the Flink website repository and it works great).
>>
>> Cheers,
>> Max
>>
>> On Wed, Feb 24, 2016 at 7:04 AM, James Malone
>> <jamesmal...@google.com.invalid> wrote:
>> > Hello everyone,
>> >
>> > Since we're in the process of getting bootstrapped, I wanted to improve
>> on
>> > our website a bit, especially since we have a new logo.
>> >
>> > The first site was built using Maven sites. To be honest, it presented a
>> > bit of a problem because many of the Beam committers have used GitHub
>> docs
>> > to date and wanted a system which was somewhat similar. Since GH docs is
>> > built on Jekyll (as far as I know) I figured that might actually be an
>> > easier way to build the website anyway.
>> >
>> > So, I just updated the incubator website. with an exact copy of the old
>> > site but using Jekyll + Bootstrap 3. That should hopefully make it easier
>> > for anyone and everyone to work against (and to move existing docs.)
>> >
>> > The repository for the current site is here:
>> >
>> > https://github.com/evilsoapbox/beam-site
>> >
>> > I also have a tgz of the old site in case there's any concern or
>> > disagreement. Needless to say, when we sort out the CCLAs (which should
>> be
>> > very soon) I'd like to get this in a project repo somewhere so we can
>> have
>> > better version control and review.
>> >
>> > Finally, the theme is basic bootstrap with a few changes (like using
>> Roboto
>> > as the font to match the logo.) I figure if/when there's interest in
>> > detailed design, we can cover that as a seperate discussion.
>> >
>> > Cheers!
>> >
>> > James
>>

Re: New beam website!

[Maximilian Michels]

Alright, I've asked the Infra team to migrate the repository to Git
and setup a GitHub sync.

Git migration: 
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11318
GitHub sync: 
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11319

Cheers,
Max

On Wed, Feb 24, 2016 at 9:00 PM, James Malone
 wrote:
> That would be awesome. Full disclosure - I 
> Happy to help however I can and any experience anyone has for making that
> happen is welcomed. :)
>
> On Wed, Feb 24, 2016 at 9:05 AM, Maximilian Michels  wrote:
>
>> Hi James,
>>
>> The updated website looks good to me. I agree that it will simplify
>> work for a lot of people who are used to Jekyll.
>>
>> The website is already in the SVN repository. After we have sorted out
>> the CCLAs, the only thing that is left is a GitHub sync to make it
>> more accessible for contributors. The prerequisite for that is that we
>> change it to Git. Apache Infra can do that (we have done likewise for
>> the Flink website repository and it works great).
>>
>> Cheers,
>> Max
>>
>> On Wed, Feb 24, 2016 at 7:04 AM, James Malone
>>  wrote:
>> > Hello everyone,
>> >
>> > Since we're in the process of getting bootstrapped, I wanted to improve
>> on
>> > our website a bit, especially since we have a new logo.
>> >
>> > The first site was built using Maven sites. To be honest, it presented a
>> > bit of a problem because many of the Beam committers have used GitHub
>> docs
>> > to date and wanted a system which was somewhat similar. Since GH docs is
>> > built on Jekyll (as far as I know) I figured that might actually be an
>> > easier way to build the website anyway.
>> >
>> > So, I just updated the incubator website. with an exact copy of the old
>> > site but using Jekyll + Bootstrap 3. That should hopefully make it easier
>> > for anyone and everyone to work against (and to move existing docs.)
>> >
>> > The repository for the current site is here:
>> >
>> > https://github.com/evilsoapbox/beam-site
>> >
>> > I also have a tgz of the old site in case there's any concern or
>> > disagreement. Needless to say, when we sort out the CCLAs (which should
>> be
>> > very soon) I'd like to get this in a project repo somewhere so we can
>> have
>> > better version control and review.
>> >
>> > Finally, the theme is basic bootstrap with a few changes (like using
>> Roboto
>> > as the font to match the logo.) I figure if/when there's interest in
>> > detailed design, we can cover that as a seperate discussion.
>> >
>> > Cheers!
>> >
>> > James
>>