Re: [PROPOSAL] New Beam website design?
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 > > > > > > >> this > >> > >> > >> > >>>into one place, so anybody can contribute and make progress. > >>> > >>> > >>> > >
Re: [PROPOSAL] New Beam website design?
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, Jean-Baptiste Onofré >>> >>> >>> >> >>>> > >> >>> >>> wrote: >>> >>> >>> >>> >>>
Re: [PROPOSAL] New Beam website design?
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?
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?
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?
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?
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?
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, 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-vezycmtom...@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 > 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?
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 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?
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?
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?
Great, I will definitely. Thanks ! I'm improving the CSS, and testing live with Jekyll. Hopefully, I will be able to propose a pull request soon. Regards JB On 10/06/2016 05:49 PM, James Malone wrote: 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 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
Re: [PROPOSAL] New Beam website design?
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 > >> > home > >> > page. > >> > > >> > I would love to help here ! > >> > > >> > Regards > >> > JB > >> > > >> >>
Re: [PROPOSAL] New Beam website design?
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 >> >> we create a new design (layout templates, color schemes, >visual >> >> design) >> >> for >> >> the Bea
Re: [PROPOSAL] New Beam website design?
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 message about what Beam is from an user perspective: > why > > > > should > >
Re: [PROPOSAL] New Beam website design?
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] is based on the a > > >> basic > > >> Bootstrap/Jekyll theme. While
Re: [PROPOSAL] New Beam website design?
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 > >> 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. > >> > >>
Re: [PROPOSAL] New Beam website design?
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 >> 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 >
Re: [PROPOSAL] New Beam website design?
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 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 -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: [PROPOSAL] New Beam website design?
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?
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?
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 >
Re: [PROPOSAL] New Beam website design?
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?
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
