# HG changeset patch
# Node ID 01ead8d9a2c8
# Parent  a43164c34fb9
diff --git a/hugo/content/_index.md b/hugo/content/_index.md
--- a/hugo/content/_index.md
+++ b/hugo/content/_index.md
@@ -24,7 +24,7 @@
 Pidgin is under constant development. Releases are usually frequent and driven
 by user contributions, such as
 [issues](https://issues.imfreedom.org/issues/PIDGIN?u=1) and
-[contributions](/development/contributing/).
+[contributions]({{< ref "development/contributing" >}}).
 
 Pidgin is free and contains no ads. All our code is open source and licensed
 under the GNU General Public License. This means you can get Pidgin's underlying
diff --git a/hugo/content/about/_index.md b/hugo/content/about/_index.md
--- a/hugo/content/about/_index.md
+++ b/hugo/content/about/_index.md
@@ -41,4 +41,4 @@
 Pidgin is a huge project that is under constant development. Releases are
 usually frequent and driven by user contributions, such as
 [issues](https://issues.imfreedom.org/issues/PIDGIN?u=1) and
-[contributions]({{<ref "development/contributing/">}}).
+[contributions]({{< ref "development/contributing" >}}).
diff --git a/hugo/content/development/_index.md b/hugo/content/development/_index.md
--- a/hugo/content/development/_index.md
+++ b/hugo/content/development/_index.md
@@ -6,3 +6,6 @@
 lastmod: 2019-01-21T22:34:09.000Z
 ---
 
+In this section you'll find information related to developing Pidgin. Keep in
+mind that since Pidgin is a huge project there's a lot of content here so try
+not to feel overwhelmed by it.
diff --git a/hugo/content/development/contributing/_index.md b/hugo/content/development/contributing.md
rename from hugo/content/development/contributing/_index.md
rename to hugo/content/development/contributing.md
--- a/hugo/content/development/contributing/_index.md
+++ b/hugo/content/development/contributing.md
@@ -7,31 +7,48 @@
 lastmod: 2019-08-21T04:05:48.000Z
 ---
 
+## Ideas to contribute
+
 Pidgin is a huge project with a ton of things to be done, even if you're not a
 coder.  Below is a short list of things you can do to help get involved!!
 
- * Triage the issue tracker
+ * Triage the issue tracker.
    * Try to reproduce described bugs.  If you can find an easy way to
-     reproduce, leave a comment to explain how to do it.
+     reproduce, leave a comment explaining how to do it.
    * Find/mark/close duplicates.  Seriously, even just one or two duplicates
      found and properly marked is a huge help to our backlog!
    * Suggest patches be turned into pull requests, or bring patches to the
      attention of the core dev team.
- * Help users and participate in the community [chatrooms]({{< ref "contact#chatrooms" >}}).
+ * Help users and participate in the community
+   [chatrooms]({{< ref "contact#chatrooms" >}}).
  * Proofread the documentation--this is a really, really easy way to start!
  * Help facilitate translators and translations
    * via [transifex](https://www.transifex.com/pidgin/pidgin/)
-   * help translate this repo
-   * other suggestions?
- * Convert wiki pages to markdown for inclusion in this repo.
+   * help translate [this repo](https://keep.imfreedom.org/pidgin/nest)
+ * Convert [legacy wiki](https://old.pidgin.im) pages to markdown for inclusion
+   in [this repo](https://keep.imfreedom.org/pidgin/nest).
  * Walk the links on [ThirdPartyPlugins](https://pidgin.im/plugins)
    and mark broken ones as such.  This is another really easy way to start!
  * Participate in discussion on IRC, XMPP, and/or the Mailing Lists.
 
 For the coders out there:
 
- * Find/fix build warnings
- * Find/fix bugs on your own or via the issue tracker
- * Participate in design discussions
+ * Find/fix build warnings.
+ * Find/fix bugs on your own or via the issue tracker.
+ * Participate in design discussions.
  * Add cool features!
 
+## How to contribute code
+
+We acknowledge that Pidgin leverages tools that a lot of developers may not be
+familiar with so we created documentation that helps you getting started and at
+the same time explains how our contribution process works.
+
+1. Checkout the [version control page]({{< ref version-control >}}). Pay special
+   attention to the branches which host the Pidgin 3 codebase vs the Pidgin 2
+   one.
+2. [Using Pidgin mercurial](https://docs.pidgin.im/libpurple/latest/chapter-using-mercurial.html)
+3. [Pidgin code contribution process]({{< param "contributeGuideURL" >}})
+
+If you have any questions about this process, remember that you have a variety
+of [methods to reach out to us]({{< ref contact >}}).
diff --git a/hugo/content/development/contributing/mercurial.md b/hugo/content/development/contributing/mercurial.md
deleted file mode 100644
--- a/hugo/content/development/contributing/mercurial.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Using Mercurial
-date: 2019-02-01T05:09:48.000Z
-anchor: contributing
-replaces:
-  - developer.pidgin.im/wiki/UsingPidginMercurial
-lastmod: 2019-08-29T20:33:38.000Z
----
-
-### Configure Mercurial
-Mercurial is configured through several rc files.  You can override the
-system-wide settings on a per-user or per-repository basis by changing either
-`~/.hgrc` or `<repository>/.hg/hgrc`.  See `man hgrc` for details.
-
-You must set your username when working with Mercurial repositories.  To do
-that, add two lines to `~/.hgrc` (or optionally `<repository>/.hg/hgrc`, if you
-want to use a different username for other Mercurial repositories):
-
-```
-[ui]
-username = First Last <email@address.tld>
-```
-
-Other useful options that can be set in the `[ui]` section of an `hgrc` are the
-merge tool and to make Mercurial verbose or not:
-
-```
-[ui]
-username = First Last <email@address.tld>
-verbose = True
-merge = meld
-```
-
-Git diffs can be useful too, and making `hg log -v` the default behavior for `hg
-log` can be helpful:
-
-```
-[diff]
-git = True
-
-[defaults]
-log = -v
-```
-
-### Clone the Repository and Select a Branch
-
-To start working with Pidgin from Mercurial, you'll probably want to clone our
-main repository:
-
-```
-hg clone https://{{< repo pidgin >}} pidgin
-```
-
-This will give you a `pidgin` directory with the 3.0.0 development code by
-default.  If you want to develop against Pidgin 3.0.0, you're all set!
-
-Naturally, Pidgin has a number of branches within its repository, and these
-branches handle various projects including our maintenance of Pidgin 2.x.y.  We
-won't go into all the branches here, as there are a lot of them, but we know
-some people would like to work against Pidgin 2.x.y instead of 3.0.0.  In order
-to do that, clone the repository as above, but then do this:
-
-```
-cd pidgin
-hg up release-2.x.y
-```
-
-You now have a Pidgin 2 tree to work with.  Happy hacking!
diff --git a/hugo/content/install/_index.md b/hugo/content/install/_index.md
--- a/hugo/content/install/_index.md
+++ b/hugo/content/install/_index.md
@@ -88,8 +88,8 @@
 distribution.
 
 If you are looking to **modify** Pidgin, you may want to look at our
-[instructions for checking out the code from our
-repository](https://pidgin.im/development/contributing/mercurial/).
+[instructions for contributing code from our
+repository]({{< ref "development/contributing" >}}).
 
 # Finch
 
diff --git a/hugo/content/post/nest-launch.md b/hugo/content/post/nest-launch.md
--- a/hugo/content/post/nest-launch.md
+++ b/hugo/content/post/nest-launch.md
@@ -25,7 +25,7 @@
 choice.
 
 Finally, if you would like to contribute please see the
-[contributing](/development/contributing/) page.
+[contributing]({{< ref "development/contributing" >}}) page.
 
 --
 
