Account confirmers, canmove, Confirmed users
2,357
edits
| Line 31: | Line 31: | ||
#* Functionality | #* Functionality | ||
#* Locales affected | #* Locales affected | ||
#** Keep in mind that our localizer community is overall very active and enthusiastic. However, other locales (not from the | #** Keep in mind that our localizer community is overall very active and enthusiastic. However, other locales (not from the "affected" list) may ask why they weren't targeted for your project and if they can participate. Be prepared to have an answer for them. | ||
#** | #** Consider as well what happens if a localization team does not have time to take on your request or simply says, "No." | ||
#* | #* Available budget and resources | ||
#* | #* Expected life-cycle (one-time/short/long?) | ||
#** | #** For projects with short life-cycles: | ||
#** | #*** Localization requirements should be simple. | ||
#*** Updating content is | #** For projects with long life-cycles: | ||
#*** Use techniques to make updating the site much easier. | |||
#*** Updating content is a laborious task. Beware of localization burnout. | |||
#*** How "evergreen" is the content on your site? | #*** How "evergreen" is the content on your site? | ||
#*** How often do you plan to change it? | #*** How often do you plan to change it? | ||