+ 1.

Also, the website repo need not wait for the software grants. It might be a 
good idea to get the website into its final destination so every one test their 
commit bits are working.

Suresh

> On Feb 24, 2016, at 12:05 PM, Maximilian Michels <[email protected]> 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
> <[email protected]> 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

Reply via email to