You can no longer use the old automatic deployment method because of jekyll-paginate-v2, a plugin that is not officially supported by GitHub. Now you need to deploy it manually or via the CI. That is, you no longer deploy from the master branch. After the code is merged into master, the new pages are generated manually or by CI (core command: jekyll build). Then, the generated content, which is in the folder _site, is uploaded to the gh-pages branch for deployment.
It's easy to copy html and replace language in place. But using template strings would make it way easier for a translator to come in, use a tool like Transifex, and make sure everything makes sense.
中文 + en
this blog is the best post I've seen for getting this done. It's specifically about En / ZH too!
it suggests the jekyll-paginate-v2 plugin but that's not supported out of the box by pages. [We do have options](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll to support the plugin. Run CI to build the site and push the static resources to GitHub after.
this post also looks good but it's old
--
It's easy to copy html and replace language in place. But using template strings would make it way easier for a translator to come in, use a tool like Transifex, and make sure everything makes sense.