It's fine for me. Not sure if other guys have additional concern. On Thu, Jul 13, 2017 at 1:52 PM, Luciano Resende <[email protected]> wrote:
> I think we could fork the template repository, and try to push the current > Livy website as a branch (e.g. original_website) ? That should resolve the > current concerns about history/credits. > > On Thu, Jul 13, 2017 at 1:45 PM, Saisai Shao <[email protected]> > wrote: > > > I think this is great. Looking from the previous thread our major concern > > is to keep the contribution history/credits, will this break the > > history/credits? If not I think this probably be better. > > > > On Thu, Jul 13, 2017 at 1:33 PM, Luciano Resende <[email protected]> > > wrote: > > > > > While looking at the current website, it seems that there are only > three > > > pages based on pure HTML content. > > > > > > Should we look into actually creating a new website from scratch, based > > on > > > Jekkyl, similar to what a few of the other projects are using (e.g. > > Spark, > > > Bahir, SystemML, etc). > > > > > > If we choose this approach, there is already a template available ( > > > https://github.com/apache/apache-website-template) that follows most > of > > > the > > > Apache Policy and has most of the structure for pages like download, > > > community, etc. and we will only need to change model and update > content > > > but in the long run will make it easier for the community to contribute > > and > > > extend the website much simpler. > > > > > > Thoughts ? > > > > > > -- > > > Luciano Resende > > > http://twitter.com/lresende1975 > > > http://lresende.blogspot.com/ > > > > > > > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
