If it is one or several pages, it will not be multi-lingual, this will be defined by the general architecture of how the site is assembled. It can be several pages, it can be a template that has the texts filled with what comes from a database or file according to what is selected, it can be a single page that loads the texts with AJAX or something similar.
First define how you will do in one language and then define how you will do it in several languages.
Making a single page for several languages gives more work than people imagine because the texts are not the same size and this creates complications. That's why some people prefer to do everything in their hands. If you make a template to use in all languages it needs to be very well done to handle different text sizes without getting weird, especially without bursting text but also leaving undue spaces.
If you do this you have to decide where to put the texts, it's usually in a database. That's why you need to decide whether your pages will be dynamically generated or statically . Ideally, texts should be loaded and used as required by variables or associative arrays, or if
, since the language identifier already determines what texts are taken.
If you choose to capture the text by AJAX it should not be a site because it may have indexing problems.
Remember that images that have text must be different, so URLs of them must be differentiated as well.
I did not even enter the merit of alphabets very different from ours (Roman) and written in another direction, after all it is rare to do for such different languages.
Obviously the details of how to do it can vary greatly and this is too broad to respond without knowing the need.