Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Versions to Translate #71

Closed
maddhruv opened this issue Apr 14, 2018 · 1 comment
Closed

Versions to Translate #71

maddhruv opened this issue Apr 14, 2018 · 1 comment

Comments

@maddhruv
Copy link
Contributor

maddhruv commented Apr 14, 2018

Targeted versions to be translated into #70
Primarily --

  • [v4.x] - EOL - 04/18 - M. LTS βŒ›
  • [v5.x] - EOL πŸ’€
  • [v6.x] - EOL - 04/19 - A. LTS
  • [v7.x] - EOL πŸ’€
  • [v8.x] - EOL - 12/19 - A. LTS
  • [v9.x] - EOL - 06/18 βŒ›
  • [v10.x] - A. LTS - 10/18 πŸŽ‚

Which all versions shall we be targeting for translations?
5/7 are dead, 4 is used at many places but LTS gonna die soon

Refer - https://nodejs.org/dist/index.json

@zeke
Copy link
Contributor

zeke commented May 11, 2018

I like the idea of this repo only having the freshest docs for each major version of node. Following the lead of the existing website and @maddhruv's example above, I'd be in favor of naming the content directories v<MAJOR>.x instead of using specific version numbers.

content
β”œβ”€β”€ v10.x
β”œβ”€β”€ v6.x
β”œβ”€β”€ v7.x
β”œβ”€β”€ v8.x
└── v9.x

It will take some work to get the build process to gracefully overwrite existing docs as new minors and patches are imported, but we can figure it out. We can use Crowdin's Translation Memory workflows to fill in existing translations as new content comes in. See #56

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants