Closed Bug 740566 Opened 10 years ago Closed 9 years ago

Add a hint for users who want a button/banner in an unavailable language that they could help (see also FAQ)

Categories

(Firefox Affiliates Graveyard :: affiliates.mozilla.org, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: Aleksej, Unassigned)

References

()

Details

(Whiteboard: [testday-20120329])

At step 3 of a banner creation, the user is asked to choose a language for the banner. Since the banners are not auto-generated, many languages are not available.


The FAQ has a section about getting involved.
* The first answer says that you can e-mail ideas of buttons to affiliates@.
* The next question is “Can I build my own button?”, the response to which mentions languages, but is basically “Not yet... but soon.”, which IMHO is not enticing contributors to do anything *in the present*.


However, I think a user won’t even go to the FAQ when seeing that his language is not available, unless he is inclined to propose contributions, and/or thinks Mozilla welcomes them.

Also, the button may seem auto-generated, so a user might just think “Why didn’t they include my language?”


I think it would be helpful to add a hint in the banner creation wizard (e.g. near the drop-down list, or something like a footnote with an asterisk near the list) that if the user can’t find a banner in the desired language, he can help.
Product: Websites → Firefox Affiliates
This is an excellent idea! I've added it to the list of things to consider for the redesign.

Marking as WONTFIX since we won't be fixing this for the current site. Thanks for the suggestion!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Bumping to QA verified wontfix -- note this didn't make it into the initial release though a place holder has been added to https://affiliates.mozilla.org/about/
Status: RESOLVED → VERIFIED
Product: Firefox Affiliates → Firefox Affiliates Graveyard
You need to log in before you can comment on or make changes to this bug.