You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/04/22 11:54:48 UTC

[GitHub] [apisix-website] SkyeYoung commented on issue #1048: [Proposal]: refactor Blog module

SkyeYoung commented on issue #1048:
URL: https://github.com/apache/apisix-website/issues/1048#issuecomment-1106440056

   > > But as for the blog program to be used, we would like to get some suggestions. The options that are already under consideration are:
   > > 
   > > * [Hexo](https://hexo.io/)
   > > * [Hugo](https://gohugo.io/)
   > > * [Asciidoctor](https://asciidoctor.org/)
   > 
   > Sorry, Asciidoctor is not a blog engine, it's a format.
   > 
   > I personally use Jekyll. It's in Ruby, it's easy to create plugins even if you don't know Ruby (I did) and the ecosystem is quite large - there's an Asciidoctor integration.
   > 
   > Whatever we choose, we need to make sure such an integration exists.
   
   > Sorry, Asciidoctor is not a blog engine, it's a format.
   
   Emmmm, I think AsciiDoc is a format, and Asciidoctor is a tool chain. (I don't really know it)
   
   But I'm really not familiar with ruby. In fact almost everyone I know is not familiar with ruby (you are the first :D).
   
   In fact, I was very concerned about whether using Ruby would have some impact on our subsequent maintenance. Here are some of my concerns: 
   
   1. It would introduce additional and possibly huge Ruby dependencies in the CI. 
   2. Most of the people I know who maintain the front end are not familiar with Ruby, and probably Nodejs and Go have more influence than that.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org