Hugo and jekyll both work for me. Sheng Wu 吴晟 Twitter, wusheng1108
Willem Jiang <willem.ji...@gmail.com> 于2020年3月6日周五 下午4:46写道： > Let's start the discussion first. > BTW, we also need to find a website framework engine to render the > markdown file into html. > There is a vote[1] on the dev@community about using Hugo[2] or > Jekyll[3] for the community website. > > [1] > https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%40%3Cdev.community.apache.org%3E > [2]https://gohugo.io/ > [3]https://jekyllrb.com/ > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Mar 6, 2020 at 3:22 PM Sheng Wu <wu.sheng.841...@gmail.com> wrote: > > > > Should I create an ALC-Beijing repo for now? Or an org? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Willem Jiang <willem.ji...@gmail.com> 于2020年3月6日周五 下午3:14写道： > > > > > It should be fine that we have public github repo to let other work > > > together. > > > With the help of Github Page[1] or ASF GitPublish it's quite easy for > > > us to create a website. > > > > > > [1]https://pages.github.com/ > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, Mar 6, 2020 at 10:23 AM Juan Pan <panj...@apache.org> wrote: > > > > > > > > Hi > > > > > > > > > > > > Thanks for everyone’s effort. > > > > My main concern is that we just want to record content of each > meeting > > > for us or to promote ALC Beijing to welcome others join? > > > > If it is the later, is gitHub a friendly way for people to look? I > think > > > it is better to record and promote along with twitter or a website. > > > > > > > > > > > > Cheers, > > > > Trista > > > > > > > > > > > > Juan Pan (Trista) > > > > > > > > Senior DBA & PPMC of Apache ShardingSphere(Incubating) > > > > E-mail: panj...@apache.org > > > > > > > > > > > > > > > > > > > > On 03/6/2020 07:23，Willem Jiang<ningji...@apache.org> wrote： > > > > As we discussed during the ALC-Beijing meeting[1], the better > solution > > > > is use git to host the content for us to corparted and the WeChat > > > > Public Account is for releasing the content to WeChat user. > > > > > > > > Willem Jiang > > > > > > > > > > > > On Thu, Mar 5, 2020 at 8:29 PM Sheng Wu <wu.sheng.841...@gmail.com> > > > wrote: > > > > > > > > I am feeling a similar thing about private(sort of) content. Maybe > it is > > > > not a big deal as it is still free and open to everyone as the fact > is, > > > > everyone has the wechat already, but we could consider host it > somewhere > > > > else, or achieve them in some way. > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > > > > 适兕 <lijiangshe...@gmail.com> 于2020年3月5日周四 下午6:45写道： > > > > > > > > Hi, Willem > > > > > > > > Well done. > > > > > > > > But I have a question, WeChat Public is can not access from > outside of > > > > Tencent system. and it‘s URL is not for human being. Google can't > search > > > , > > > > the worst is in the WeChat Public article can not link Internet > content. > > > > So I suggest , We need a space for store content first , Just like > > > > GitHub page etc. WeChat Public is just one of the spread channel. > > > > > > > > Any feedback is appreciated. > > > > > > > > > > > > On Thu, Mar 5, 2020 at 6:26 PM Willem Jiang <ningji...@apache.org> > > > wrote: > > > > > > > > FYI, I just applied a WeChat Public Account of alc-beijing. > > > > You can use "ALC Beijing" to search for the account if you are using > > > > WeChat. > > > > Please feel free to drop your articles about ASF or ASF projects in > > > > Chinese, we are happy to share it with our audience. > > > > > > > > Willem Jiang > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > -- > > > > Welcome to http://opensourceway.community! The open source way: > > > Dedicated > > > > to the exploration of ideas, knowledge and values related to open > source. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
