You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be super cool if the plugin recognised all of the string I have used to name and describe fields and sections and offer them in the plugin for translation.
I don't see it addressed very often, but I often have the case where I want to localize the CMS for editors in different locales. A great part of the author experience would be even more improved if a user could read instructions in their native language.
How I would see this working:
Plugin sniffs for the presence of project.yaml file and extract a whitelist of keys that should be translateable — "name", "instructions", "label" and so on
These keys would be presented as a distinct category on the left side in the plugin interface.
The text was updated successfully, but these errors were encountered:
Follow up on this. Do I understand correctly that the question addresses ability to translate field names and field instructions, so that each user can see field names and instructions in their own language inside Craft CMS?
Description
It would be super cool if the plugin recognised all of the string I have used to name and describe fields and sections and offer them in the plugin for translation.
I don't see it addressed very often, but I often have the case where I want to localize the CMS for editors in different locales. A great part of the author experience would be even more improved if a user could read instructions in their native language.
How I would see this working:
project.yaml
file and extract a whitelist of keys that should be translateable — "name", "instructions", "label" and so onThe text was updated successfully, but these errors were encountered: