Gentoo Archives: www-redesign

From: mushroomblue <mushroomblue@××××××××××.net>
To: www-redesign@l.g.o
Subject: Re: [www-redesign] Update of http://wwwredesign.gentoo.org
Date: Wed, 23 Nov 2005 07:04:57
Message-Id: 1132729481.22588.0.camel@zim.mushroomblue.org
In Reply to: [www-redesign] Update of http://wwwredesign.gentoo.org by Curtis Napier
1 other than making the cell that contains the "donate" button the same
2 width as the advertisement column, it looks MUCH better.
3
4 blue ribbon.
5
6
7 On Wed, 2005-11-23 at 01:40 -0500, Curtis Napier wrote:
8 > First of all, thank you everyone for all the feedback. Your input is
9 > important and greatly appreciated.
10 >
11 > I should have said that the last update was not complete as far as
12 > design was concerned. I was mainly looking for accessibility and
13 > rendering issues on as many browsers/OS's as possible. I got that
14 > feedback and fixed the issues that came up. I also implemented the rest
15 > of the design so it should now be more visually appealing and better
16 > match Aarons reference design. I took into consideration all of the
17 > suggestions that were submitted and now ask for additional feedback to
18 > ensure that my changes didn't introduce any additional
19 > rendering/accessibility bugs and that the design is acceptable to as
20 > many people as possible.
21 >
22 > If there are no more outstanding issues reported I will submit this
23 > current layout for approval.
24 >
25 >
26 > Questions to some of the answers and suggestions that were brought up:
27 >
28 > The artwork is all part of the winning design. Any issues with the
29 > infinity symbol should have been addressed a year ago.
30 >
31 > I am not the designer of this site. I am merely implementing it in the
32 > XSL backend. I am the only person working on this and I am the
33 > designated official developer, the project lead is Swift and his role is
34 > to offer advice, enforce design policy and generally oversee my actions
35 > and help me with internal gentoo policies and procedures. The project is
36 > actually owned by Infra and they (they == infra leads which is klieber
37 > and ramereth as far as I know), along with Swift, have the final say on
38 > everything. I welcome any and all patches that you are willing to
39 > submit. All submissions will be evaluated on a case by case basis.
40 >
41 > Aarons reference design at www.aaronshi.com/gentoo/ is exactly that: A
42 > reference. In it's current form it differs from his original submission
43 > which was the winning entry and should not be considered as anything
44 > else but a reference. I tried to stick to that design as much as
45 > possible but some things were simply not possible.
46 >
47 > Aarons design uses a smaller default font, that is not acceptable from
48 > an accessibility POV. The main font is at 1em and all cursory fonts
49 > multipliers of 1em. The main font will remain at 1em which is the
50 > standard for the accessibility guidelines. If you don't like the
51 > standard font size every single graphical browser offers a font zoom
52 > capability, use it.
53 >
54 > Aarons use of a smaller font allows more information to appear on the
55 > page. This is an illusion of size. If you have your browser window set
56 > to 800x600 or smaller the jumpads disappear and the page has to be
57 > scrolled to see them no matter how big/small the font is. If you enlarge
58 > the font on Aarons reference to the standard 1em the jumppads disappear
59 > and the page must be scrolled anyway so this point is moot.
60 >
61 > Purple background with yellow text is hideous. Not going to happen.
62 >
63 > The "Locator" would require rewrites of not only the XSL but also the
64 > actual xml files and is outside the scope of this project. Touching any
65 > xml content file is strictly off limits, all existing xml should be
66 > backwards compatible with the new design. This point is not debatable.
67 > Use of a database would make this task easier while allowing backwards
68 > compatibility but it will have to wait for a future update to the site
69 > to be implemented.
70 >
71 > I actually implemented a search that used google much like the example
72 > that was posted here. The search was discussed at length with the
73 > project lead and it was decided that using a third party search engine
74 > such as google was unacceptable. As Lance said, this will have to be
75 > coordinated with infra at a later date. Gentoo is a not-for-profit but,
76 > unfortunetly, it is the wrong kind of non-profit so Google will not
77 > sponsor us.
78 >
79 > The contents of the uppermost menu are to sites that are outside the
80 > www.gentoo.org website. They will stay in this location. They are green
81 > to contrast with the purple background to ensure that colorblind and
82 > other visually impaired people can see it. Green is the compliment to
83 > purple so I am baffled that people think the combination is not
84 > attractive. In Aarons preview the light purple color of these links is
85 > not visible to color blind individuals thus it is unacceptable. This
86 > color will not change.
87 >
88 > The grey menu should contain links that would be used in order of a new
89 > user and that highlight the main parts of the site. I did this quickly
90 > to have something there to look at. I didn't notice any good suggestions
91 > to replace what is there. If you have suggestions please send them. The
92 > same goes for the wording in the purple boxes, if you don't like what
93 > they say submit a suggestion for each. Suggestions of "I don't like it
94 > you should change it" that don't include a clearly worded replacement
95 > will be ignored. The donate box is here to stay until the search
96 > function is implemented.
97 >
98 > Graphics should be implemented in the CSS as much as possible to aid
99 > future maintenance (the xsl templates are huge and not easy to maintain.
100 > The least amount of editing of these files as possible is one of the
101 > major goals). In text browsers that can handle graphics but don't
102 > support CSS the upper left logo (which is a background image so it can
103 > be put in the css) will not appear but will leave space for the missing
104 > background image. I can't figure out a way around this. If you have a
105 > suggestion I would appreciate it.
106 >
107 > Horizontal scrolling of the entire page when a code listing is wider
108 > than the page only happens in IE. All other browsers understand the CSS
109 > scroll:auto tag and will only scroll the actual code listing. The same
110 > applies to inline images within the page contents. IE is broken but I
111 > did everything I could to make it behave the same as other browsers.
112 > This is one issue that IE is simply broken on and there is nothing I can
113 > do to fix that. Javascript fixes are available but the use of Javascript
114 > is strictly forbidden. Javascript is not debatable.
115 >
116 > Redundant links to important pages such as the Handbook and Documention
117 > only serve to make them easier for a user to locate. They will remain
118 > for the time being unless someone can come up with a good reason to
119 > remove them other than "I don't like it".
120 >
121 > The <hr /> tags in the Handbook navigation are contained within the
122 > handbook xsl template. Touching that file is outside my scope.
123 >
124 > The redesign test site is not a full mirror. I added the security index
125 > page so we could see what it looks like.
126 >
127 > The site is not XHTML it is HTML-4.01 Transitional and it passes the w3c
128 > validator. Manually overriding HTML-4.01 Transitional in the w3c
129 > validator is not required and any errors that it reports if you do this
130 > will not be addressed. If you can come up with a good technical reason
131 > why doing this would benefit anyone I will address it.
132 >
133 > Navigation and useability studies are beyond my scope. These issues
134 > should have been addressed a year ago.
135 >
136 > The left hand navigation column is dead. No amount of beating this dead
137 > horse will resurrect it. The jumppads will remain at the bottom and
138 > appear on all non-documentation pages so that those links are accessible
139 > as much as possible.
140 >
141 > <base href> is not needed for this site to function properly. If you
142 > want to save the page locally you are free to do so and add the tag
143 > yourself for your local copy.
144 >
145 > The CSS is only 12k. Why would shaving 4k off of it to make it 8k make a
146 > difference to anyone?
147 >
148 > The site is dynamically generated with XSL/XML all the pages end in
149 > .xml. There are no plans to change it to .xhtml now or in the future.
150 >
151 > The image on the about page is within the content xml file and not
152 > within the XSL template. Touching about.xml or any other xml content
153 > file is outside my scope.
154 >
155 > GLEP 10 is outside my scope.
156 >
157 > The jumppads have alt text. They always have. They pop up as tool tips
158 > on every browser I have tested. If they aren't for you please submit
159 > your browser version and OS and I will look into it.
160 >
161 > The blue text that represents code was darkened for accessibility
162 > issues. It will not change.
163 >
164 > In Aarons preview the search box and the ads column are placed with a
165 > Position:absolute and has it's size set. At resolutions below 800x600
166 > this makes the ads overlap the content and the search box overlap the
167 > box to the left on every browser. When content is scarce the ads overlap
168 > the footer. This is not fixable given the current state of css support
169 > in the various browsers. After many many many long hours of research and
170 > experimentation I decided that we would have to resort to a table for
171 > the ads column and include the search (now donate) box within the div
172 > that contains the four purple boxes with a % width to fix this issue. I
173 > lowered the % width of the donate box and increased the others to bring
174 > it more inline with Aarons original design. It's not perfect but it's
175 > close enough.
176 >
177 > Accessibilty guidelines say that all text links should be underlined. I
178 > made an exception for the grey menu bar for aesthetic purposes but will
179 > not make an exception for any other links.
180 >
181 > gentoo.org and all domains owned by the Gentoo Foundation should render
182 > correctly in all browsers that are still in general use. IE5 on the mac
183 > is still a valid browser and will be supported as much as possible.
184 >
185 > Summary and authors are important and should be prominently displayed
186 > before the actual content. On the current design they are on the right
187 > in a tiny column that wraps every two words. This is unacceptable. These
188 > items will stay at the top for now unless someone can come up with a
189 > place to put them that makes sense, looks good, allows the summary to be
190 > seen on top and not below the content (because a summary should be above
191 > the content otherwise why have a summary if you have to scroll past the
192 > content to see it?). The handbook is the only page that has a large list
193 > of authors and authors only appear on the first page so this should not
194 > be a problem.
195 >
196 >
197 >
198 > Here is a list of items that have changed since my last post:
199 >
200 > *menu code was changed from a floated block list to a simple inline div
201 > with non-breaking spaces. This should fix the IE5 on Mac issue.
202 >
203 > *Background color for content was made light grey with black text for
204 > better visibility of the text. Bright monitors should no longer be a
205 > problem.
206 >
207 > *background color of the ads was made darker to contrast with the
208 > content area. Decorative header was added.
209 >
210 > *white space was collapsed as much as possible.
211 >
212 > *all extraneous information and decorative news headers were removed
213 > from the front page to help readability and to bring focus to the
214 > information. This includes the cow image and text. Overwhelming amounts
215 > of information on the front page should no longer be a problem. This
216 > also brings the jumppads closer to the top so new users will be better
217 > able to spot them.
218 >
219 > *table headers were centered and data cells left justified.
220 >
221 > *table borders are now collapsed and only 1px thick. They are no longer
222 > ugly.
223 >
224 > *removed the BOLD from the design credit in the footer. This wasn't
225 > supposed to be BOLD in the first place, probably a mistake on my part.
226 >
227 > *The purple boxes below the grey menu bar now only appear on the main index.
228 >
229 > *news poster date and submitter color changed to match Aarons design
230 >
231 > *added a filter that removes the author and date if they are missing or
232 > script generated.
233 >
234 > *removed redundant doc title
235 >
236 > *removed the donation button image and replaced it with a simple button.
237
238 --
239 www-redesign@g.o mailing list