diff --git a/i2p2www/pages/site/get-involved/index.html b/i2p2www/pages/site/get-involved/index.html
index 081347d326b56a9646b2689d3ba928e08faae36b..d08659e85882e617b1bfb1de4a971d7d518294c0 100644
--- a/i2p2www/pages/site/get-involved/index.html
+++ b/i2p2www/pages/site/get-involved/index.html
@@ -1,15 +1,13 @@
{% extends "global/layout.html" %} {% block title %}{% trans %}Get Involved{% endtrans %}{% endblock %} {% block content %}
-<h2>{% trans %}There are many ways you can help I2P.{% endtrans %}</h2>
-<h3>{% trans %}Grow the Community{% endtrans %}</h3>
+<h2>{% trans %}Contribute to the I2P Network .{% endtrans %}</h2>
+
<ul>
+ </li>
<li><b>{% trans %}Support I2P Core Development{% endtrans %}</b>{% trans %}The project hosts meetings on the first Tuesday of every month that are open to the community. This is a great opportunity to see what is happening with I2P core development and
- familiarize yourself with Roadmap tasks. Additionally, protocol development meetings take place every Tuesday and zzz's development forum is available all of the time as a place to participate in development and issues that need fixing. See the
+ familiarize yourself with Roadmap tasks. See the
new developer's guide for how to get started.{% endtrans %}
</li>
- <li><b>{% trans %}Spread the Word.{% endtrans %}</b> — {% trans -%} Tell people about I2P on forums, blogs, and comments to articles. Fix up the
- <a href="https://wikipedia.org/wiki/I2P">Wikipedia article about I2P in your language</a>. Tell your friends, and more importantly, use I2P to communicate with your friends. We have many tools that can help you keep your private conversations
- private. {%- endtrans %}
- </li>
+
<li><b><a href="{{ newtrans }}">{{ _('Translation and Documentation') }}</a></b> — {% trans newtrans=site_url('get-involved/guides/new-translators') -%} Help translate the website and the software into your language. Translators are a very important
part of this decentralized project and your work is always appreciated. See the new translator's guide for details. The project also welcomes support to help keep its documentation updated. See the <a href="{{ newtrans }}">new translator's guide</a> for details. {%- endtrans %}
</li>
@@ -17,10 +15,10 @@
<h3>{% trans %}Host Services for Yourself and Others{% endtrans %}</h3>
<ul>
<li><b><a href="{{ site_url('/about/software') }}">{{ _('Services') }}</a></b> — {% trans -%} Self-hosting almost anything, from an SSH server for yourself to an ActivityPub forum for everyone and anything in between, is helpful to the I2P network,
- especially if you write down instructions for others. Almost anything you can think of can be made to work with I2P, and your service is valuable to the network. {%- endtrans %}
+ especially if you write down instructions for others. Almost anything you can think of can be made to work with I2P. {%- endtrans %}
</li>
- <li><b><a href="{{ reseed }}">{{ _('Reseeding') }}</a></b> — {% trans reseed=site_url('get-involved/guides/reseed') -%} Getting new users onto the network is a very important task, and that task is handled by our reseed servers. The more reseed
- servers we have, the more de-centralized and redundant our infrastructure is. It's a big responsibility, but it's pretty easy to set up a reseed server for new routers to bootstrap from. Detailed instructions are on our <a href="{{ reseed }}">reseed server page</a>.
+ <li><b><a href="{{ reseed }}">{{ _('Reseeding') }}</a></b> — {% trans reseed=site_url('get-involved/guides/reseed') -%} Getting new participanting routers onto the network is a very important task, and that task is handled by reseed servers. The more reseed
+ servers the network has, the more de-centralized and redundant its infrastructure becomes. It's a big responsibility, but it's pretty easy to set up a reseed server for new routers to bootstrap from. Detailed instructions can be found here <a href="{{ reseed }}">reseed server page</a>.
{%- endtrans %}
</li>
</ul>
@@ -29,18 +27,16 @@
<li><b><a href="{{ site_url('/get-involved/guides/dev-guidelines') }}">{{ _('Applications') }}</a></b> — {% trans apps=site_url('get-involved/develop/applications') -%} Write or port applications for I2P. There's some guidelines and a list of ideas
on the <a href="{{ apps }}">applications page</a>. {%- endtrans %}
</li>
- <li><a href="{{ site_url('/get-involved/guides/new-developers') }}"><b>{{ _('Coding') }}</a></b> — {% trans trac=i2pconv('trac.i2p2.i2p'), zzz=i2pconv('zzz.i2p'), newdevs=site_url('get-involved/guides/new-developers') -%} There's plenty to do if
- you know Java or are ready to learn. Check for open tickets on <a href="http://{{ trac }}/report/1">Trac</a> or the TODO list on <a href="http://{{ zzz }}">{{ zzz }}</a> for some ideas on where to start. See the <a href="{{ newdevs }}">new developer's guide</a> for details. {%- endtrans %}
- </li>
- <li><b><a href="{{ site_url('research/index') }}">{{ _('Analysis') }}</b> — {% trans threatmodel=site_url('docs/how/threat-model') -%} Study or test the code to look for vulnerabilities. Both anonymity vulnerabilities from the various
+
+ <li><b><a href="{{ site_url('research/index') }}">{{ _('Research') }}</b> — {% trans threatmodel=site_url('docs/how/threat-model') -%} Study or test I2P code to look for vulnerabilities. Both anonymity vulnerabilities from the various
<a href="{{ threatmodel }}">threat models</a>, and DOS and other weaknesses due to security holes, benefit from ongoing research. {%- endtrans %}
</li>
</ul>
-<h4>{% trans %}When you're ready, join us on our Gitlab{% endtrans %}</h4>
+<h4>{% trans %}Join I2P On Gitlab{% endtrans %}</h4>
<ul>
<li><strong><a href="http://git.idk.i2p">{% trans %}Inside I2P - (http://git.idk.i2p){% endtrans %}</a></strong>
</li>
<li><strong><a href="https://i2pgit.org">{% trans %}Outside I2P - (https://i2pgit.org){% endtrans %}</a></strong>
</li>
</ul>
-{% endblock %}
\ No newline at end of file
+{% endblock %}