chaokunyang commented on PR #148: URL: https://github.com/apache/fury-site/pull/148#issuecomment-2289331619
> > Hi @yuluo-yx, thank you for your contribution. I appreciate your effort. I have a couple of suggestions that may help improve our workflow. Firstly, it would be best to avoid duplicating documents in the source tree. We can handle that when building the website pages. Also, could we use git mv instead? There are numerous file deletions and creations, but they all contain the same content. Additionally, I noticed that #142 is working on the same thing. Perhaps we could collaborate and work together on this. Thank you! > > Thanks for the reply, I have a couple questions that 1, if we avoid duplication of documents, where do we put the Chinese and English documents? 2, what should be the process when git mv moves the documentation, as far as I know, the internationalization method is the same in the documentation sites built with docusaurus. 3, live blood we can use hugo this documentation website framework, it can avoid extra placeholder file 4, for the documentation building program you mentioned, is there a feasibility reference? What should be done? 1. When we translate a page, we can create a Chinese document for it. But if we don't translate it, we should copy english document to Chinese location before building docusaurus 2. I don't dive into docusaurus, I'm not sure whether it needs the placeholder. @theweipeng @LofiSu do you have any suggestions? 3. You mean use [`hugo`](https://gohugo.io/)? I prefer keeping using docusaurus unless it's too hard to add internationalization support 4. Like mentioned in step one, we can add some extra steps to execute some shell script to copy english documents to chinese documents if they doesn't exist, then execute `npm run build` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
