Confirmed users
1,276
edits
(Reordered by priority) |
|||
Line 23: | Line 23: | ||
* Also display user created projects without entities, but show admin on click. | * Also display user created projects without entities, but show admin on click. | ||
=== | === User notifications === | ||
* | * Notify users about new strings, updated strings, etc. | ||
* | * Show notifications in the UI. | ||
* | * Send notifications via email (Persona). | ||
=== | === Implement Sandstone design === | ||
* | * http://www.mozilla.org/en-US/styleguide/ | ||
* https://assets.mozillalabs.com/ | |||
* TabZilla: https://github.com/debloper/tabzilla | |||
* Responsive design | |||
* https:// | |||
* | |||
* | |||
=== Glossary & spellchecker === | === Glossary & spellchecker === | ||
Line 56: | Line 45: | ||
* We should make it easy to show all suggestions made by one guy or remove everything that the other guy did, because it’s spam. | * We should make it easy to show all suggestions made by one guy or remove everything that the other guy did, because it’s spam. | ||
* Checking for target = source. | * Checking for target = source. | ||
=== Send e-mails to admins === | |||
* http://david.feinzeig.com/blog/2012/02/18/tips-for-creating-404-page-not-found-and-500-server-error-templates-in-django-plus-configuring-email-alerts/ | |||
* http://stackoverflow.com/questions/6914687/django-sending-email | |||
* https://docs.djangoproject.com/en/1.4/topics/email/ | |||
=== <pontoon> tag === | |||
* Identifying strings is still not perfect: https://github.com/mathjazz/pontoon/commit/7fefc6e2baab8bb174736d996015972bc823cd5f | |||
* Investigate the use of <pontoon> tag? | |||
* Resources: http://horv.at/blog/implementing-hooks/ | |||
=== Crowdsourcing === | === Crowdsourcing === | ||
Line 67: | Line 66: | ||
* example flow: click the "feedback" tab, select the DOM element that you want to give feedback on, type the description of the issue ("a typo") or a suggestion for a new translation, hit submit. Behind the scenes, a request to Pontoon API is made and a new suggestion is recorded. | * example flow: click the "feedback" tab, select the DOM element that you want to give feedback on, type the description of the issue ("a typo") or a suggestion for a new translation, hit submit. Behind the scenes, a request to Pontoon API is made and a new suggestion is recorded. | ||
=== | === Apply Pontoon to the Open Web Apps development template generator === | ||
* | * This should probably be implemented as a hook. | ||
* https:// | * https://wiki.mozilla.org/Apps/Mortar | ||
* | * https://github.com/mozilla/mortar | ||
* | |||
=== Verbatim integration === | |||
* Similar to Transifex. API is being implemented... | |||
=== Save vanilla sites translations to Transifex === | |||
* Transifex API allows creating new projects: http://help.transifex.com/features/api/index.html#projects | |||
* Save non-hooks-powered sites as Transifex projects. | |||
== DONE == | == DONE == |