 Welcome back, welcome back, especially to our online friends joining us streaming. I am Santana, coming to you live from WordCamp Lishboa 2023, track two, where it's at. One of my favorite things about the WordPress community is how international it is, and this next speaker gave me a run for my money this afternoon. This is the first time I'm introducing a speaker of the Galician language. I hope you really enjoy this talk. I'm a language nerd, so you learned that about me today. We have Jesus Amiero coming up. Jesus is an IT engineer and a member of the WordPress community. He works at automatic, where he focuses on localization. Welcome him for his talk in Galician, on building multilingual WordPress sites. Welcome, Jesus. Why do we need to create a multilingual WordPress site? Well, for various reasons. For example, we can have a place in the electronic market in Portugal, and we want to expand our trade to Spain, to France. The guys would set up that place in a language that they speak in that country, in Spanish, in French, in English, etc. We can do the same with e-learning. We have an online training academy and we want to expand other countries' frontiers. We can have a personal cooperative. At the moment we want to capture more customers in another country with a different language, or it will be normal to use languages in the countries where we want to expand. It also happens in cases of other countries, countries with languages, as it can be the case of certain regions in Spain, for example, Galicia, where we have two more official languages, which are Galician or Spanish, or countries like Switzerland, where they have four more official languages. In all these cases, many more, we need to build a multilingual site. As you know, WordPress supports different languages, we can translate them, both in the core, as well as in the plans and in the topics, but what doesn't support multilingual for or with you? In Core, so what we have to do is to see what alternatives we have in the market to be able to make this configuration, heteronoso site, working in several languages. First of all, some previous considerations that we have to analyze before implementing our site. Let's see, first of all, we have to make it clear today, do you need a multilingual site term? That is fundamental. Are you ready for a multilingual site? If you are Portuguese, I want to launch a site in Spanish, I am prepared for this new language. What are you going to translate these countries? I am going to be able to produce them in a continuous way. Who are you going to locate them every day? Who are you going to support the new clients that are in Spain? I have these people, not every day. That is very important. What are your projects? What technical requirements do you have? For example, if you are going to have a commerce installed, if you are going to need specialized SEO plugins, if you are going to use a visual constructor as an elementor, if you are going to have a multisite or a single multilingual site, we will go deeper into that later. Also, if both themes such as plugins that I am going to use have a multilingual support, they are translated, okay? Both things. Once we have all these concepts clear, we are going to see what we should translate so that our site has, as much as possible, the new languages that we are going to have. In principle, we should be able to translate and locate everything that we are going to be able to. That is to say, post-pacinas, media, custom post types, it makes no sense to have a video in portuguese, to mount this video in portuguese, not a pasina in spanish, it would be weird for a new client that is going to buy us a product. Or at least, tipe to the slack, I have counted those elements. It also makes sense to translate taxonomies, widgets, menus, it would make no sense to use a portuguese menu in a French site, contact formaries, so that they can contact us. Also, all those elements that we have in a slider, text, images, videos and links. It is very important that it is as familiar as possible, everything with what we have available for the final user, it is not your own language. Also important, define the domain structure that we are going to use. We can use a subdomain, for example, pt.myshop.com, it would be to attend online for portuguese, it is.myshop.conciliere para español etc etc. We can do it with a subdomain, myshop.pt, myshop.es, or it is more recommended that we use a domain itself, myyaloja.pt for a site in portuguese, mytienda.español, mytienda.gal, for a site in galego, etc etc. It is much more familiar for the final user. Once we have all these previous conditions, that we have to analyze before installing a plugin or start doing anything, once we have it clear, we are going to see how we do it. We have two clear alternatives, we can mount a single wordpress through a plugin with multilingual support, or we can mount a multisite, where each site of a multisite will have a different language. We are going to start with polo multisite. Multisites, basic characteristics, are that each language is going to be in an independent place, so it is easy to negate or remove languages, we simply negate or remove a new place, or that you do need to link them, to link or count, the different languages. Each of these advantages is a solution that is in nuclear, that is, we do not need a plugin or an element, although we are going to need something that we are going to see right away. We are going to execute multiple sites in the same installation and each site is going to be for a language. We are going to be able to share users, plugins, themes for the different sites, the different languages. Something interesting that we can give access to, or translator that is going to translate us to Italian, only Italian site, it is not going to have global access to be able to make other changes on other sites, not other languages. We are going to be able to have different themes in different languages, because that can be interesting to adapt to the culture of each site, of each country. Incomvenient, installation of a Multisite is a little more complex, administration or daily can also be a little more complex, and there are some plugins that do not work for Multisite, they should be the minimums, even you have to run those plans, but you can find this problem. Ok, we mentioned before that we had that problem of linking the different languages. This problem is going to solve our Multilingual Press, which is here in front of that plugin, who allows us to connect different sites within the Multisite network. The advantage of having this plugin is that there is no blocking, that is to say that if you remove everything is going to work as it was working, but we are going to lose the connection between sites. The solution recommended by GoogleCommerce, if you are going to think of an electronic company built with GoogleCommerce, maybe it is the right solution for this plugin using a Multisite in WordPress. Ok, another alternative, a Multisite, is a unique site. Why is it characterized as a unique site? Well, obviously because of the unique installation of WordPress, a plugin works, that plugin allows us to link or remove languages in a very simple way, and we do not need to link the different sites, because we only have one for the different languages. The advantages, it is easier to install in a normal WordPress installation, easy to use, it has very large communities, because if you want to save the public WordPress, most of these plugins have hundreds of thousands of installations, so the community that you see behind them is brutal. Calls are inconvenient, it is a little slower, because this plugin is going to slow down, but it is going to slow down WordPress. A very important problem, Eulokindo plugin, that is to say, if we want to get out of this plugin and use another multilingual plugin, we are going to have problems to do it. There are adapters and different tools, but an important problem is multilingual press. We are going to have incompatibilities with other plugins. This is important, because if you are going to download a plugin, go to the website of the manufacturer, you will see, for example, the support site for Elementor, for Google Commerc, etc., etc. And an important problem that everyone has access to, that is, a person who had permission from the administration will have permission to touch all their languages. If you hire a translator, he will be able to translate it into a single language. What alternatives do we have in the market? A lot of them. I imagine that the first ones you will know are KutraZade, KutraZadeX, KutraZadeXT. They are historical in the market. Nowadays, the last KutraZadeXT is in development, but I do not recommend it, because it does not have the correct support for Google Commerc, it is discarded. The following is Polylang, which has a premium version, WPML, which is a totally paid plugin, also very interesting, Wiglot, which automates all the translation through machine tools. The content is also very interesting to start a web with content translated into nothing, in minutes. And here we give you a few more that are also interesting because you will hear, for example, Translate Press, Smarting, etc. It is important to conclude that you have to consider if you need to have a multilingual site, that is, I have a site in Portuguese, I need to mount, or I have a site in Spanish, in English, in French, etc. Once I have it clear, I analyze all the technical needs of plugins, etc., that I need to install, and from there I analyze different options, both technical and economic, because most plugins have an annual cost, and obviously I will stay with the one that fits the most with all this. I am Jesús Emeiro, I am the developer of Senorino Automatic, and I will leave the presentation for anyone who asks questions that they want to ask me. Woohoo! Woohoo! Don't go anywhere. We have time for one question for Jesús. Woohoo! We have competing questions. No. No. Okay, that's a real question, so I'm going to come over here to this gentleman. Hola, Jesús. Van Español, por no hablo gallego. Dentro de estas dos opciones que planteas, a la hora de implementar un proceso un poco más automatizado que pueda llegar a escalar, cuál recomendarías? La de multicitio o la de sitio único? La de multicitio seguramente. Gracias. Es decir, te permita hacer un escalado a través de distintas tecnologías de escalado de salida más recomendable. Mucha una pregunta ahí. I think we have time if it's a fast question and a fast answer. Okay, fast, fast, fast. Gracias por la charra, Jesús. Muy chula. En términos de optimización, cuáles de las dos opciones, si en multicitio o un sitio único, cuáles crees que son las más... lo más fácil de optimizar, o por lo menos de hacer tareas de WPO, más o menos sencillas. Creo que en términos de optimización sería multisite porque no dependes de ningún plug-in extra que necesitas optimizar, sino que de instalación normal de Wordpress. Por tanto, creo que sí que sería más sincera de optimizar. Okay, is it you? Is it you? Okay, one more. Quick, quick. Hola, Jesús. Obrigado. Más de una vez, estás con nosco y por trazer-se o galego. O que eu te queria preguntar Eu percebo pela tua apresentação que na maior parte das situações tu irias irias para uma solução de multisite. Certo? Porque é que esta solução de multisite não é mais conhecida ou mais utilizada e porque é que não tem mais advogados como tu? Eu creo que por um tema econômico. O plug-in que se permite ligar aos distintos sites multilingual preso, único que é assim no mercado que é bastante conhecido, tem um preço elevado, bom, elevado entre comidas elevado para um projeto que está arrancando. Pero a gente que está dedicado a instalar Google Comer para fazer tendas online, é a solução que por aqui opta. Boa pregunta. That's all we have time for and that's the extent of my Portuguese. So I will say thank you e muito obrigada. We have this lovely gift for you and thank you for your contribution to the community. Take that. Big round of applause for Esu.