@Melvyn_Paulino these last days I have been working on adding DB content translation.
The guide I wrote and George mentions only cover static strings and that is why the strings are stored in filesystem and not in DB. Quicker access as they do not change.
Now I use an improved version compatible with nodejs that includes also DB dynamic content translation. In this small video you can see the outcome.
The category name strings are stored in the database and the strings for link below are stored in filesystem.
On the console on the right you can see that the app downloads on demand the two files for spanish static strings and then it retrieves the database content in the appropriate language.
For the DB content translation I went for jsonb column type(exclusive for PostgreSQL database engine). It is a very powerful data type that tries to implement the wonders of noSQL databases in a SQL database like postgresql.
You can see in this picture how the database content is structured in the category name column.
This way I don’t have to worry about having to change database schema or about joining a huge table of strings. Need a new language? Just add a new key:value pair to the column on the fly.
You end up with a blazing fast translation feature that doesn’t require reloading the browser.
For SEO compatibility I recommend you using nodejs server model as it includes templates and server side rendering that will make things easier when setting meta tags. Regarding SEO URL routes you are free to implement them in the best way you consider. It is easy with Wappler.
i18next framework+postgresql jsonb -> Absolute winner for static and dynamic translations.
This being said Wappler still doesn’t support 100% json and jsonb postgresql types in the database query server connect actions. But I already opened a bug report/feature request and hopefully we can tackle this. Not a hard limitation as you can easily resort to code(very easy code).
