|
44 | 44 | <a href="https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign">issues</a> |
45 | 45 | list some of our unmet needs – and feel free to share your own ideas.</p><h3 id=graphic-design>Graphic design<a class=headerlink href=#graphic-design title="Link to this heading">#</a></h3><p>We can barely begin to list the contributions a graphic designer can make here. |
46 | 46 | Our docs are parched for illustration; our growing website craves images – |
47 | | -opportunities abound.</p><h3 id=translating-website-content>Translating website content<a class=headerlink href=#translating-website-content title="Link to this heading">#</a></h3><p>We plan multiple translations of <a href=https://numpy.org>numpy.org</a> to make NumPy |
48 | | -accessible to users in their native language. Volunteer translators are at the heart |
49 | | -of this effort. See |
50 | | -<a href=https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n>here</a> |
51 | | -for background; comment on <a href=https://github.com/numpy/numpy.org/issues/55>this GitHub |
52 | | -issue</a> to sign up.</p><h3 id=community-coordination-and-outreach>Community coordination and outreach<a class=headerlink href=#community-coordination-and-outreach title="Link to this heading">#</a></h3><p>Through community contact we share our work more widely and learn where we’re |
| 47 | +opportunities abound.</p><h3 id=translating-website-content>Translating website content<a class=headerlink href=#translating-website-content title="Link to this heading">#</a></h3><p>We are working on translating <a href=https://numpy.org>numpy.org</a> into multiple languages to make |
| 48 | +its content more accessible to NumPy users all over the globe. (See |
| 49 | +<a href=https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n>NEP 28</a> |
| 50 | +for background.) Volunteer translators are at the heart of this effort. If you’d like to help, join the |
| 51 | +<em>translation</em> channel on the |
| 52 | +<a href=https://discord.com/channels/786703927705862175/1131695137370669158>Scientific Python Discord server</a>.</p><p>To get familiar with our translation process, read the guide |
| 53 | +<a href=https://scientific-python-translations.github.io/translate/>How to translate content using Crowdin</a>.</p><h3 id=community-coordination-and-outreach>Community coordination and outreach<a class=headerlink href=#community-coordination-and-outreach title="Link to this heading">#</a></h3><p>Through community contact we share our work more widely and learn where we’re |
53 | 54 | falling short. We’re eager to get more people involved in efforts like organizing NumPy <a href=https://scisprints.github.io/>code |
54 | 55 | sprints</a>, a newsletter, and perhaps a blog.</p><h3 id=fundraising>Fundraising<a class=headerlink href=#fundraising title="Link to this heading">#</a></h3><p>For many years, NumPy was maintained by dedicated volunteers, but as its importance grew it |
55 | 56 | became clear that to ensure stability and growth we would need financial support. |
|
0 commit comments