Hi, Hanks, Thanks for the reorganization, you can create an issue to summarize all the work and I will help you finding volunteers to rewrite the documents.
Thanks. Adam Feng On 13 Oct 2017, 9:00 PM +0800, Hanks Zhang <[email protected]>, wrote: > Hi everybody, > > I think to put our website in the incubator-weex-site [1] repo is more > properly. I have already reorganized the structure of our documents and > website, I will push to master branch later. > > But the documents need to be rewritten as Weex has been changed a lot. Need > all of your members work together to accomplish it. > > Thanks, everyone. > > [1] https://github.com/apache/incubator-weex-site > > ---- > > Hanks > > 2017-10-11 16:52 GMT+08:00 Adam Feng <[email protected]>: > > > +1, that will also make it easier to contribute documentation and make > > the website code clear and detached. incubator-weex is such a big repo > > which contains everything(iOS, Android, JS, Website, Document, etc.), > > finding the documents' location always makes my life harder. > > > > > > Thanks. > > Adam Feng > > > > On 11 Oct 2017, 1:14 PM +0800, Hanks Zhang <[email protected]>, wrote: > > > Dear Weex Members, > > > > > > Currently, the source code of Weex website is in the doc subfolder of > > > incubator-weex [1]. It's independent of Weex SDK. > > > > > > I wonder if it's a good idea to move the website out of the > > incubator-weex > > > repo. As we adjust our commit and pr strategy, I think it would be more > > > efficient to use another pr rule for our website. > > > > > > Moreover, I have noticed that there is an "incubator-weex-site" repo [2] > > > under apache, but it only has few commits and seems not being used. Does > > > anyone know what the role of this repo is? Should we move our website > > into > > > it? > > > > > > [1] https://github.com/apache/incubator-weex/tree/master/doc > > > [2] https://github.com/apache/incubator-weex-site > > > > > > ------ > > > > > > Hanks > >
