OSGeo · veroandreo · Apr 19, 2020 · Apr 15, 2020 · Apr 15, 2020
diff --git a/content/contribute/_index.en.md b/content/contribute/_index.en.md
@@ -1,5 +1,5 @@
 ---
-title: "Contribute"
+title: "Get involved"
 date: 2018-12-29T11:02:05+05:00
 icon: "fa fa-user"
 description: "Contribute to Open Source Geospatial through GRASS GIS development"
@@ -8,7 +8,78 @@ layout: "contribute"
 weight: 3
 ---
 
+### Report a bug or enhancement wish
+<i class="fa fa-bug fa-5x" style="float:right;padding-left:10px"></i>
+Bug reports and feature requests can be submitted as issues in the [GRASS GIS bugtracking system](https://github.com/OSGeo/grass/issues).
+All new submissions in the tracker will be automatically forwarded to the GRASS GIS development mailing list.
 
-<h3 class="mt-2 mb-4"> Coming soon</h3>
+###### Some recommendations
+<small>
+<ul>
+ <li>Check if the bug you found is still present in the current stable release version or, better, in the "master" version before reporting. If you use an older version, please consider to [upgrade](/download) first.</li>
+ <li>Make sure that the developers have all the information needed to reproduce the bug (e.g. explain how to reproduce the bug using the [North Carolina example dataset](/download/data.en))</li>
+ <li>Report only a single bug or feature request with each issue</li>
+ <li>Before reporting a bug, please check that it hasn't been reported already in the [GRASS GIS bugtracking system](https://github.com/OSGeo/grass/issues)</li>
+</ul>
+We recommend to read [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) by Simon Tatham.
+</small>
 
-<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
+### Documentation
+<i class="fa fa-file-text fa-5x" style="float:left;padding-right:10px"></i>
+
+Each GRASS GIS module comes with a respective [manual page](/learn/manuals) that provides clear and up-to-date documentation including working examples.
+
+There are also several [tutorials](/learn/tutorials), courses and wikis contributed by different developers and users. These are a very important tool to learn how to use GRASS GIS, too.
+
+**Writing or editing documentation and tutorials is an ideal platform for your first contribution to the project.**
+
+### Translation
+<i class="fa fa-language fa-5x" style="float:right;padding-left:10px"></i>
+The great worldwide interest in GRASS suggests value in translating GRASS messages to languages other than English. 
+The GRASS Development Team is continuously seeking translators.
+
+This is an opportunity to contribute even for non-programmers since messages can be easily translated in a user friendly platform. 
+**No programming skills required! See below how to join.**
+
+#### Want to join?
+
+Great! Please subscribe to the dedicated [mailing list](http://lists.osgeo.org/mailman/listinfo/grass-translations)
+and check the [messages translation Wiki page](http://grasswiki.osgeo.org/wiki/GRASS_messages_translation)
+on how we translate on [**Transifex**](https://www.transifex.com/grass-gis/grass7/).
+
+### Create an Add-on
+<i class="fa fa-plug fa-5x" style="float:left;padding-right:10px"></i>
+Developing your own modules? Great! 
+
+Please upload your add-ons to the **GRASS GIS Addons repository**. In this way, they become available to the community
+through the extension manager (g.extension or graphical user interface). 
+Here is the full list of [existing addons](https://grass.osgeo.org/grass7/manuals/addons/) to get inspired.
+
+Further details about how to gain access to our [GitHub Addons repository](https://github.com/OSGeo/grass-addons/) can be
+found in [this document](https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASSaddonsrepository).
+
+### Contribute to GRASS GIS core
+<i class="fa fa-gear fa-5x" style="float:right;padding-left:10px"></i>
+The GRASS GIS core consists of the libraries used by GRASS GIS modules and GUI, as well as the code used to develop the Graphic User Interface and the most important modules.
+
+It may be a good idea to send a small posting to the [GRASS developers mailing list](http://lists.osgeo.org/mailman/listinfo/grass-dev) to announce your activities
+(maybe someone will join you!). Please read [how to write source code](https://trac.osgeo.org/grass/wiki/HowToProgram) before submitting. 
+
+We'd also appreciate if you could support us with [bug fixing and enhancement wishes](https://github.com/OSGeo/grass/issues).
+
+### Other opportunities
+
+#### Google Summer of Code (GSoC)
+
+**GSoC is a stipend program for students by Google.**
+
+Students are encouraged to propose their own ideas. Otherwise, they can choose from the 
+[GRASS GSoC Ideas](http://trac.osgeo.org/grass/wiki/GSoC) list. If selected, Google 
+will pay a monthly stipend for 3 months.
+
+#### Google Code-in (GCI)
+
+**GCI is an online contest introducing high school students to open source development**.
+
+Students can participate with the [OSGeo organization](https://codein.withgoogle.com/organizations/osgeo/) 
+and solve tasks for different projects. Tasks might include documentation, design, coding, etc.
diff --git a/content/contribute/community.md b/content/contribute/community.md
diff --git a/content/contribute/development.md b/content/contribute/development.md
@@ -12,81 +12,3 @@ GRASS GIS is developed and supported by a [worldwide team of developers](https:/
 Many people have contributed to GRASS GIS throughout time. Without them, GRASS GIS would not exist in its current form.
 The authors of the individual programs or modules are listed at the end of the respective manual pages.
 
-## Get Involved
-
-### Report a bug or enhancement wish
-<img src="../../images/bugreport.svg" width="30%" alt="" style="float:right">
-Bug reports and feature requests can be submitted as issues in the [GRASS GIS bugtracking system](https://github.com/OSGeo/grass/issues).
-
-All new submissions in the tracker will be automatically forwarded to the GRASS GIS development mailing list.
-
-###### Some recommendations
-<small>
-<ul>
- <li>Check if the bug you found is still present in the current stable release version or, better, in the "master" version before reporting. If you use an older version, please consider to [upgrade](/download) first</li>
- <li>Make sure that the developers have all the information needed to reproduce the bug (e.g. explain how to reproduce the bug using the [North Carolina example dataset]())</li>
- <li>Report only a single bug or feature request with each issue</li>
- <li>Before reporting a bug, please check that it hasn't been reported already in the [GRASS GIS bugtracking system](https://github.com/OSGeo/grass/issues)</li>
-</ul>
-If you want, you can read [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) by Simon Tatham.
-</small>
-
-### Documentation
-<img src="../../images/document.svg" width="20%" alt="" style="float:left">
-
-Each GRASS GIS module comes with a respective [manual page](/learn/manuals) that provides clear and up-to-date documentation including working examples.
-
-There are also several [tutorials](/learn/tutorials), courses and wikis contributed by different developers and users. These are a very important tool to learn how to use GRASS GIS, too.
-
-**Writing or editing documentation and tutorials is an ideal platform for your first contribution to the project.**
-
-### Translation
-<img src="../../images/translation.svg" width="30%" alt="" style="float:right">
-The great worldwide interest in GRASS suggests value in translating GRASS messages to languages other than English. 
-The GRASS Development Team is continuously seeking translators.
-
-This is an opportunity to contribute even for non-programmers since messages can be easily translated in a user friendly platform. 
-**No programming skills required! See below how to join.**
-
-#### Want to join?
-
-Great! Please subscribe to the dedicated [mailing list](http://lists.osgeo.org/mailman/listinfo/grass-translations)
-and check the [messages translation Wiki page](http://grasswiki.osgeo.org/wiki/GRASS_messages_translation)
-on how we translate on [**Transifex**](https://www.transifex.com/grass-gis/grass7/).
-
-### Create an Add-on
-<img src="../../images/addons.svg" width="30%" alt="" style="float:left">
-Developing your own modules? Great! 
-
-Please upload your add-ons to the **GRASS GIS Addons repository**. In this way, they become available to the community
-through the extension manager (g.extension or graphical user interface). 
-Here is the full list of [existing addons](https://grass.osgeo.org/grass7/manuals/addons/) to get inspired.
-
-Further details about how to gain access to our [GitHub Addons repository](https://github.com/OSGeo/grass-addons/) can be
-found in [this document](https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASSaddonsrepository).
-
-### Contribute to GRASS GIS core
-<img src="../../images/core_devel.svg" width="30%" alt="" style="float:right;padding-left:10px">
-The GRASS GIS core consists of the libraries used by GRASS GIS modules and GUI, as well as the code used to develop the Graphic User Interface and the most important modules.
-
-It may be a good idea to send a small posting to the [GRASS developers mailing list](http://lists.osgeo.org/mailman/listinfo/grass-dev) to announce your activities
-(maybe someone will join you!). Please read [how to write source code](https://trac.osgeo.org/grass/wiki/HowToProgram) before submitting. 
-
-We'd also appreciate if you could support us with [bug fixing and enhancement wishes](https://github.com/OSGeo/grass/issues).
-
-### Other opportunities
-
-#### Google Summer of Code (GSoC)
-
-**GSoC is a stipend program for students by Google.**
-
-Students are encouraged to propose their own ideas. Otherwise, they can choose from the 
-[GRASS GSoC Ideas](http://trac.osgeo.org/grass/wiki/GSoC) list. If selected, Google 
-will pay a monthly stipend for 3 months.
-
-#### Google Code-in (GCI)
-
-**GCI is an online contest introducing high school students to open source development**.
-
-Students can participate with the [OSGeo organization](https://codein.withgoogle.com/organizations/osgeo/) 
-and solve tasks for different projects. Tasks might include documentation, design, coding, etc.