1 |
Hi All, |
2 |
|
3 |
I've developed a set of guidelines for the website redesign, as well as an "action plan". |
4 |
|
5 |
www.gentoo.org Mission Statement |
6 |
================================ |
7 |
|
8 |
www.gentoo.org exists to assist those who use and develop for Gentoo Linux by |
9 |
providing relevant, up-to-date information about Gentoo Linux and Linux in |
10 |
general, focusing on topics related to Gentoo Linux installation, use, |
11 |
administration and development. As the central "hub" for all things Gentoo, |
12 |
the site should also feature important news relevant to Gentoo Linux users and |
13 |
developers. In addition to catering to Gentoo Linux users and developers, |
14 |
www.gentoo.org has the secondary purpose of meeting the needs of *potential* |
15 |
Gentoo Linux users, providing the necessary information so that they can decide |
16 |
whether Gentoo Linux is right for them. |
17 |
|
18 |
www.gentoo.org Target Audience |
19 |
============================== |
20 |
|
21 |
www.gentoo.org has three target audiences -- Gentoo Linux developers, users, |
22 |
and potential users. While no one group is absolutely a higher "priority" than |
23 |
another, right now the needs of Gentoo Linux developers are our highest |
24 |
priority, followed by Gentoo Linux users, and then potential users. This is |
25 |
because Gentoo Linux is currently in a pre-release state. When Gentoo Linux |
26 |
reaches version 1.0, Gentoo Linux users and potential users will also become a |
27 |
priority. |
28 |
|
29 |
www.gentoo.org Implementation Standards |
30 |
======================================= |
31 |
|
32 |
www.gentoo.org will be redesigned a section at a time, starting with the highest |
33 |
priority section. Redesigned sections will be added to the existing website |
34 |
incrementally so that visitors can benefit from the improvements immediately. |
35 |
|
36 |
All aspects of the redesign will be geared towards the need of our target |
37 |
audiences (developers, users, and potential users). We need to keep this in mind, |
38 |
especially myself since it's easy for me to get distracted by the graphical |
39 |
aspect of things when the important stuff is the XML and content. |
40 |
|
41 |
Action Plan |
42 |
=========== |
43 |
|
44 |
Right now, *developers* are our highest priority target audience. |
45 |
|
46 |
Since www.gentoo.org has a serious lack of developer documentation, our #1 |
47 |
priority is *developer* documentation. |
48 |
|
49 |
To add new developer documentation, the following tasks must be completed: |
50 |
|
51 |
1. select docbook or guide as our official XML format |
52 |
2. if guide is selected, create a DTD, finish XSLT |
53 |
if docbook, we need to learn docbook and begin working on docbook->HTML XSLT code |
54 |
3. start writing the documentation in XML |
55 |
4. integrate new developer documentation into existing website |
56 |
|
57 |
We are also going to complete one other easy task in parallel. We're going to |
58 |
add a new mailing list for the discussion/posting of CVS commits. |
59 |
|
60 |
-- |
61 |
Daniel Robbins <drobbins@g.o> |
62 |
President/CEO http://www.gentoo.org |
63 |
Gentoo Technologies, Inc. |