Open cutecutecat opened 1 year ago
A typical version format for their document likes:
%{
version: "1.3.0",
title: "Basics",
excerpt: """
Getting started, basic data types, and basic operations.
"""
---
Thanks for the issue! We will have a look.
Maybe we can extract this part and write them as a standalone Github Action plugin, it will work with CI, and deploy a page of this repo when any merge happens.
Do we have such a github action?
There is an issue tracking the translation: https://github.com/tensorchord/envd/issues/481
Refer: https://xuanwo.io/reports/2022-47/
This looks cool.
Let's do it!
/cc @Xuanwo Thanks for the awesome post.
Now it is not easy for contributor to find which essay has not been translated and pick the one they want, only to manually check the files inside the repo.
The community
elixirschool
has a good practice for this problem. User can quickly pick those files which are not translated. translate report sourceMaybe we can extract this part and write them as a standalone Github Action plugin, it will work with CI, and deploy a page of this repo when any merge happens.
Apart from that, version is also nessassary for translation for we to continus track which translation is out-of-date.