Hi All: Finally, I am going to put the blogs to the incubator-doris-website repo. You can see README[1]. So that all following new blogs should be push to the incubator-doris-website repo, and the github action will automatically merge it with the `docs/` of main repo, and update the website.
[1] https://github.com/apache/incubator-doris-website -- 此致！Best Regards 陈明雨 Mingyu Chen Email: chenmin...@apache.org 在 2021-11-19 13:17:54，"ling miao" <lingm...@apache.org> 写道： >Putting the document in another code base is indeed a solution, >but this requires us to ensure the **collaborative compilation** of the >document library and the code base when compiling. >Because the current Doris system is a built-in help document, >and it also needs to be synchronized to the website. > >Ling Miao > >Gabriel Lee <gabrielleeb...@gmail.com> 于2021年11月19日周五 下午1:01写道： > >> I think it will be a serious problem soon. Could we maintain the >> doris-website project separately? It means we should update documents or >> upload a blog post in doris-website instead of doris. This will keep doris >> project in a reasonable size but increase maintenance cost. >> >> On Fri, 19 Nov 2021 at 10:59, ling miao <lingm...@apache.org> wrote: >> >> > First of all, I am looking forward to the blog feature very much. >> > But when I was reviewing blog posts, I found that general blog posts will >> > carry a lot of resources, such as pictures. >> > In the future, we will definitely add a lot of blog posts. Will this lead >> > to a larger and larger code base? >> > If the answer is yes, is it a correct operation for us to put the >> resouces >> > of these blog articles in the code base? >> > Or how do other projects manage these blogs? >> > >> > Ling Miao >> > >>
