[gimp-web-devel/hugo] content: move and update bugs.md.

[Jehan <jehanp src gnome org>]

commit 5c0af3529e706ba70923758c3cb189a8f99f599c
Author: Jehan <jehan girinstud io>
Date:   Sun Aug 7 17:46:53 2022 +0200

    content: move and update bugs.md.
    
    Making this a page about submitting your first patch.

 content/{homepage => core_developers}/bugs.md | 16 +++++++---------
 content/core_developers/setup/_index.md       |  2 +-
 content/core_developers/standards.md          |  1 +
 3 files changed, 9 insertions(+), 10 deletions(-)
---
diff --git a/content/homepage/bugs.md b/content/core_developers/bugs.md
similarity index 55%
rename from content/homepage/bugs.md
rename to content/core_developers/bugs.md
index 64ecd11..69fa47e 100644
--- a/content/homepage/bugs.md
+++ b/content/core_developers/bugs.md
@@ -1,14 +1,15 @@
 +++
-title = "Bug Tracking System"
+title = "Bug Tracking System / Submit your first patch"
 description = "Bugs, bugs, bugs"
 date = "2022-07-19"
 abbrev = "Gitlab"
+weight = 2
 +++
 
 The GIMP project uses Gitlab's
-[issues](https://gitlab.gnome.org/GNOME/gimp/-/issues),
+[issue tracker](https://gitlab.gnome.org/GNOME/gimp/-/issues),
 to coordinate bug reports. Gitlab is also used for enhancement requests
-and the preferred way to submit patches for the GIMP is make a
+and the preferred way to submit patches for the GIMP is to make a
 [merge request](https://gitlab.gnome.org/GNOME/gimp/-/merge_requests).
 
 On [www.gimp.org](https://www.gimp.org) you can find a document describing
@@ -18,10 +19,7 @@ You can also find a document that describes
 
 Below is a list of links to get you started with Gitlab:
 
-* [List of Open Bugs](https://gitlab.gnome.org/GNOME/gimp/-/issues)
+* [List of Open Reports](https://gitlab.gnome.org/GNOME/gimp/-/issues)
+* [List of Open Reports tagged for 
"Newcomers"](https://gitlab.gnome.org/GNOME/gimp/-/issues/?state=opened&label_name%5B%5D=4.%20Newcomers)
 * [List of Open Bugs (excluding enhancement 
requests)](https://gitlab.gnome.org/GNOME/gimp/-/issues/?label_name%5B%5D=1.%20Bug)
-* [Tables of Open/Closed Bugs with milestone 
2.10.34](https://gitlab.gnome.org/GNOME/gimp/-/milestones/20#tab-issues)
-* [Tables of Open/Closed Bugs with milestone 
2.99.12](https://gitlab.gnome.org/GNOME/gimp/-/milestones/19#tab-issues)
-* [Issues without an associated, planned version 
number.](https://gitlab.gnome.org/GNOME/gimp/-/milestones/1#tab-issues)
-
-
+* [Gitlab documentation on creating merge 
requests](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
diff --git a/content/core_developers/setup/_index.md b/content/core_developers/setup/_index.md
index dbc1126..b6acec4 100644
--- a/content/core_developers/setup/_index.md
+++ b/content/core_developers/setup/_index.md
@@ -3,7 +3,7 @@ title: "Setting up your developer environment"
 date: 2022-08-07
 author: "Jehan"
 abbrev: "dev-env-setup"
-weight: 0
+weight: 1
 ---
 
 The first step as a core developer is to build GIMP. This page contains
diff --git a/content/core_developers/standards.md b/content/core_developers/standards.md
index 561f2d2..f22a609 100644
--- a/content/core_developers/standards.md
+++ b/content/core_developers/standards.md
@@ -3,6 +3,7 @@ title = "GIMP and Standards"
 date = "2022-07-20"
 abbrev = "Standards"
 description = "Standards GIMP conforms to"
+weight = 0
 +++
 
 GIMP is supposed to integrate well into your workflow. Thus is