I am working with JS frontend and am learning JS backend. Therefore, I want to understand the best practices of how to implement localized articles (content with markup).

Sorry if this question is a bit silly, but I just can't seem to find information on this.

This is how I imagine it:

1. I am creating an HTML / Markdown article using a simple form / CMS
2. The article is saved on the server
3. The magic happens (google translation API or whatever) and then I have an article translated into multiple languages
4. I fetch and parse my localized article on frontend.

So, I have a few questions:

1. Articles contain markup.

• Do I need to save the text of the article in HTML format or in Markdown?
• How to store it on the backend? As separate files like .md / .html or in DB tables like HTML strings?

I think of it like this: a DB table that stores an HTML string, an article ID and its other parameters, such as date, etc. And a separate directory on the server with images.

2. How to implement localization of this type of content?

In the frontend, we can use something like i18next and store files with translations in the client side of the application in JSON files or fetch them from a database or from some localization CMS (locize, etc.). This is the part I really can't imagine.

• Do I need to store different files in the backend like my-article.en-us.html / my-article.ru-ru.html? Or separate DB tables or something else?
• Is it possible to create an article in Markdown / HTML format in any CMS and translate it automatically? (the quality of the translation does not matter at the moment)

If it matters, for this pet-project I'm going to use:

• Next.js (frontend)
• Nest.js (backend)
• Mongo or GraphQL (DB)