Translating Nodes

Each Node in Quanta can be translated into multiple languages.

Each translation of the node, will have an individual JSON file associated, in the format: 

data_LANGCODE.json

In example, the english version of a node, will be stored into data_en.json, the italian version into data_it.json, etc.

A language neutral version of nodes is also envisioned, and it's stored in data.json files, with no prefix.


Create Node Translation Links

The [TRANSLATE_LINKS] qtag, will show all the available translation. For your convenience, it's automatically included in Shadow node forms.

The qTag will take all available languages, and create a [TRANSLATE] link per each of them. 

Once clicked, the translate link will open a Shadow box for editing the node in the correspondent language.


Customize the Translation Links

The [TRANSLATE] qtag is merely an extension of the [EDIT] qtag, to which it adds the related language attribute.

Therefore, all the attributes supported by [EDIT] and [LINK] will be supported by [TRANSLATE] as well.



What happens when you translate a Node

When you translate a Node in some language, you are creating a language version of that node.

That language version will be available for users whose current language is that language. 

So, in example, when browsing a website in Italian, all the website's lists will automatically filter out nodes that are not translated in Italian (OR language neutral).


What kind of Nodes can you actually translate?

All of them, including users, statuses, language nodes themselves!

Since Quanta does not envision "content types" and everything is a node, everything can be translated.

This approach makes multilingualism flexible, easy and straightforward.