1 |
Hi all, |
2 |
|
3 |
What follows may seem like a long list of rants. |
4 |
Please do not take it the wrong end, it's all for a good cause. |
5 |
Besides, it's difficult to know which page you're supposed to comment on at |
6 |
the moment. Some issues might have been solved by now. |
7 |
BTW, I still haven't looked at the html/css code. |
8 |
|
9 |
>>> To address the issue of font sizes, I've implemented a font size |
10 |
>>> changer on |
11 |
>>> the content pages. The user could increase/decrease the content font |
12 |
>>> size |
13 |
>>> and the changes are saved into a cookie so that it will apply site |
14 |
>>> wide. I |
15 |
>>> think this give users flexibility without compromising the layout of the |
16 |
>>> pages. Without this system, the user would use his browser to |
17 |
>>> increase font |
18 |
>>> size. The browser would increase all the fonts...making the |
19 |
>>> navigation bar |
20 |
>>> (and other) fonts extremely out of proporation |
21 |
>>> |
22 |
> That sort of works in most cases. |
23 |
> But what happens if a user don't have eg JS or cookies turn on (for |
24 |
> security/preference/whatever reasons)? The browser default setting is |
25 |
> already applied site wide without any extra magic that may or may not work. |
26 |
|
27 |
> In the days of a CRT doinated world it was pretty safe to make |
28 |
> assumtions about users fontsizes, you couldn't go too wrong if it was |
29 |
> readable to yourself. But nowdays there are really tiny LCDs with HUGE |
30 |
> resolutions of 1280 or more. In a world where a user on a 14" monitor |
31 |
> might be using anything from 640 to 1600 res, all bets are off. That is |
32 |
> why I belive it's a better design principle to simply let go of textsize |
33 |
> control and concentrate on making a design highly resilient to whatever |
34 |
> fontsize is thrown at it. |
35 |
|
36 |
Exactly. |
37 |
FYI, I use 2 CRTs (19" and 17") both at 1600x1200 and don't consider it huge |
38 |
at all. 2nd hand 21" CRTs that do 1920x1440 now sell for about 100 euros. |
39 |
|
40 |
The font control on the page is not a good idea. |
41 |
Browsers already have such a functionality. |
42 |
On the one hand, if users blow up their fonts beyond anything reasonable, it's |
43 |
their problem. |
44 |
On the other hand, the current design does not react properly to font |
45 |
increases. A slight increase makes the text in the top navigation grow out of |
46 |
the bar. Same goes for the line with the chapter index combo. The navigation |
47 |
pads at the bottom grow beyond the footer which does not appear at the bottom |
48 |
anymore. |
49 |
|
50 |
"Advertisements" is always under its green triangle, no matter how small the |
51 |
fonts. It usually appears in the grey area, at least partly. |
52 |
|
53 |
About those green triangles, I hope they'll be added by the css and not be |
54 |
part of the html. |
55 |
|
56 |
Slight indentation is very annoying to say the least. |
57 |
|
58 |
Credits should either appear in the right column or after the text. They just |
59 |
don't fit in the nice floating box with the abstract and date. |
60 |
Another option might be to group them by title. |
61 |
|
62 |
Please do not assume some text will always be as short as you think. |
63 |
For instance, displaying a date in a narrow column is a bad idea. Some will be |
64 |
wider than you think (different languages, different formats, |
65 |
http://www.gentoo.org/proj/en/gdp/tests/testdate.xml). |
66 |
|
67 |
Still to be shown: |
68 |
<pre> with <comments>, <i> and normal text |
69 |
<impo> <warn> <note> elements |
70 |
Handbook pages with their nav bar |
71 |
Properly padded tables and please keep in mind that <ti> can contain <note> |
72 |
|
73 |
BTW, I agree that using tables for the layout should be avoided but using |
74 |
tables to show tabular data is exactly what they were meant for in the first |
75 |
place. We have plenty of them and they stay. |
76 |
|
77 |
Origin and rights of the pictures need to be established. |
78 |
|
79 |
|
80 |
Many thanks to all who work hard on the www-redesign project. |
81 |
|
82 |
Cheers, |
83 |
-- |
84 |
/ Xavier Neys |
85 |
\_ Gentoo Documentation Project |
86 |
/ French & Internationalisation Lead |
87 |
\ http://www.gentoo.org/doc/en |
88 |
/\ |