How to correctly and concisely make multilingualism on the site?

Question

Internationalization and localization

Hey! Recently I was wandering around freelancing and came across such a project: there is a website (I’ll attach a photo below) and I need to make it multilingual (for now it’s just html + css).

A photo

It seems like a simple task, but depending on the language, the pictures should also change. You just can’t do it on HTML + JS (at first I wanted to make some kind of json file and let the customer fill it out himself (cheaply and cheerfully)). Something needs to be connected. First thought is WordPress.

I heard that there is a Polylang plugin, but it just translates texts and is good for blogs, etc. And how can they translate the existing layout with the change of pictures?

There was an option somehow through Elementor. Make a site in the constructor and give different sites for different languages. It seems to be very convenient for the customer: he can change the blocks in places, all the pictures and texts. N̶O̶ ̶z̶a̶ch̶e̶m̶ ̶ya̶ ̶T̶O̶G̶D̶A̶ ̶u̶h̶h̶l̶ ̶f̶r̶o̶n̶t̶-̶e̶n̶d̶+̶b̶c̶k̶-̶e̶n̶d̶ ̶n̶ ̶ ̶ ̶ ̶l̶e̶t̶? ̶ But I'm not right that this is right.

How is this done in the enlightened WordPress (or Web) community?

Answer 1

The plugin helps to translate the content, you can also change the pictures in the article for different languages, so this plugin will help you first of all.
Translation of static texts (signatures of links, buttons, etc.) - there are special language functions in the WP core itself, but they require the creation of translation files. To change the design, in theory, wp itself must add a class indicating the language in the body, I think there should be one, it is important that this function be called in the theme near the body tag.
There is a course , there at the end there is a series of videos on site localization.

Answer 2

There are three approaches:
The page does not change, all content for all languages ​​on the page is switched via CSS with changing the LANG attribute of html. Pictures can be changed as well. For one-pagers
Second:
Two different document trees or a subdomain for the language version (either inside one or two different admins)
Third:
Translation of each page into admins for all fields - when the resource tree is completely the same. language copies are created for all fields of the document, a redirect via htaccess and a cookie from the language switcher
All of this can be implemented through ± any admin panel