Reformat and reword the derivatives front page.

CVS version numbers

english/derivatives/index.wml: 1.2 -> 1.3

1 files changed, 57 insertions, 36 deletions

diff --git a/english/derivatives/index.wml b/english/derivatives/index.wml
index 2a15b877fe9..79b35622ebb 100644
--- a/english/derivatives/index.wml
+++ b/english/derivatives/index.wml
@@ -1,36 +1,57 @@
-#use wml::debian::cdimage title="Software distributions derived from Debian" BARETITLE=true
-
-<p>There are a <a href="https://wiki.debian.org/Derivatives/CensusFull">
-number of distributions</a> based on Debian. Some users might want
-to take a look at these distributions <em>in addition to</em> the official
-Debian releases.</p> <p>Debian welcomes and encourages organisations
-that want to develop new distributions based on Debian. However, in
-the spirit of Debian's <a href="https://www.debian.org/social_contract">
-social contract</a>, we ask them to contribute their work to the main
-distribution so that ultimately, all users can benefit from improvements.</p>
-
-<h2>Why deriving from Debian?</h2>
-
-<p>It's faster to modify an existing distribution like Debian than
-starting from scratch : a packaging format, repositories, packages
-base, etc. are specified and usable immediately. A lot of softwares
-are packaged so there are no need to waste time to package them. This
-allows derivatives to focus on the specific add-ons.</p>
-
-<p>Derived distributions are done for a number of reasons (better
-localization support, specific hardware support, simplified
-installation, etc.).</p>
-
-<p>If the goal is only defining a set of packages to install, creating
-a <a href="/blends/">Debian blend</a> could be a better choice than
-creating a derivative.</p>
-
-<h2>Instructions for creating derivatives</h2>
-
-<p>Derivatives can use part of Debian's infrastructure if needed (like
-repositories). Derivatives have to change direct references to Debian
-(like the logo, the name, etc.) and the links interfering to Debian'
-services (like popcon).</p>
-
-<p>Detailed development informations are available on the
-<a href="https://wiki.debian.org/Derivatives/Guidelines">wiki pages</a>.</p>
+#use wml::debian::template title="Debian derivatives"
+## TRANSLATORS: no need to translate this directory,
+## it will be undergoing a lot of changes initially
+## and discussion of the content needs to happen
+
+<p>
+## FIXME: replace link to the census with curated list
+There are a <a href="https://wiki.debian.org/Derivatives/Census">number of distributions</a> based on Debian.
+Some users might want to take a look at these distributions <em>in addition to</em> the official Debian releases.
+</p>
+
+<p>
+Debian welcomes and encourages organisations that want to develop new distributions based on Debian.
+In the spirit of Debian's <a href="https://www.debian.org/social_contract">social contract</a>,
+we hope derivatives will contribute their work to Debian and upstream projects,
+so that everyone can benefit from their improvements.
+</p>
+
+<h2>Why derive from Debian?</h2>
+
+<p>
+It can be faster to modify an existing distribution like Debian than starting from scratch since
+a packaging format, repositories, base packages and other things are specified and usable.
+A lot of software is packaged so there is no need to spend time packaging most things.
+This allows derivatives to focus on the needs of a specific audience.
+</p>
+
+<p>
+The Debian community and people from derivatives are available
+and willing to help guide new distributions in their work.
+</p>
+
+<p>
+Derivatives are created for a number of reasons
+(better localization support, specific hardware support, simplified installation,etc.).
+</p>
+
+<h2>How to derive from Debian?</h2>
+
+<p>
+Derivatives can use parts of Debian's infrastructure if needed (like repositories).
+Derivatives should change references to Debian (like the logo, name, etc.)
+and to Debian services (like the website and BTS).
+</p>
+
+<p>
+If the goal is to define a set of packages to install,
+creating a <a href="$(HOME)/blends/">Debian blend</a>
+could be an interesting way to do that within Debian.
+</p>
+
+<p>
+Detailed development information is available in the
+<a href="https://wiki.debian.org/Derivatives/Guidelines">guidelines</a> and
+guidance is available from the
+<a href="https://wiki.debian.org/DerivativesFrontDesk">front desk</a>.
+</p>