MOSS Research 2 (multilingual): Overview
What can CiviCRM do to better engage with and support non-English language users and non-profits?
According to recent website analysis (PDF download), 48.3% of website visitors are from non-English language-speaking regions. However the website is completely in English, and there are limited non-English spaces across the ecosystem of docs, Stack-exchange, Matter, Gitlab and translation. At the same time site usage analaysis (e.g. https://civicrm.org/registered-sites-map & https://stats.civicrm.org) shows sites all over the world. There are dedicated non-English language sites from Poland to Taiwan. How do we improve this?
As with MOSS Research 1 we plan to design and market a survey, analyze and publish the results.
However, there are also ongoing CiviCRM initiatives we want this to overlap/collaborate with: this is more of a two-way discussion where as well as 'what do you want' we ask 'what can you do'? The ideal outcome would be significantly increased engagement & activity across a range of areas:
- Website translation and support for new landing pages - marketing/local-sites#3
- Documentation translation - https://lab.civicrm.org/documentation/docs/issues/13
- CiviCRM core translation - https://lab.civicrm.org/dev/translation
- Strengthened/increased local/national networks & events - https://lab.civicrm.org/community/region
- Make-it-happens to fund specific translation drives (and research into other areas of funding)
As with Moss Research 1, this research could form the basis for further funding applications to undertake specific work/translations/outreach/etc.
Specific tasks
-
A. design a survey, in discussion with people associated with initiatives above https://lab.civicrm.org/community/fundraising/issues/5 -
B. market it to relevant CiviCRM users in the dbse from non-English-speaking countries, and via a blog -
C. analyze the results -
D. communicate with (some) respondents inviting them to engage in a number of ways (events, translations, etc) -
E. collate and publish findings/outcomes
Maximum 30 hours paid time.