Confirmed users
950
edits
No edit summary |
|||
Line 64: | Line 64: | ||
** Suggestion: Leave this for a later iteration. | ** Suggestion: Leave this for a later iteration. | ||
* Is the need for a JSON API just for seeing what strings are available for translation, or do we want more, like a way to pull the translations out of the system via the API? | * Is the need for a JSON API just for seeing what strings are available for translation, or do we want more, like a way to pull the translations out of the system via the API? | ||
== Pages == | |||
=== Public Community Localizer Interface === | |||
* Global Header | |||
** Has Persona login/logout button | |||
* List of strings to translate | |||
** Auto-choose locale, allow to switch to another locale, save in a cookie for next time. | |||
** Filter list by translation status (untranslated, user has suggested a translation, string has approved translation) | |||
* Suggestion detail page | |||
** Show preview of snippet in an iframe with translations applied. | |||
*** If snippet has strings without suggested translations, use the user's own suggestion for it, or English if none is found. | |||
** Update preview as user enters in suggestion. | |||
=== Admin Approved Localizer Interface === | |||
* Admin log in | |||
** Auths user via LDAP? Or maybe Persona, and verify email ends in mozilla.com? Or maybe Persona/username and password, but an admin gives their account permission for translation? | |||
* List of strings to translate | |||
** Filter by locale, translation status. | |||
* Translation detail page | |||
** Show preview of snippet in iframe with accepted translation applied. | |||
** Live update preview as accepted translation changes. | |||
** Show list of suggestions from users. |