1 |
Sven Vermeulen wrote: |
2 |
|
3 |
> - Can we have the "warning"/"important"/"note" stuff with a graphical |
4 |
> icon |
5 |
> and a nice rounded border? But without having it take up too much |
6 |
> space of |
7 |
> course. |
8 |
> |
9 |
> |
10 |
That would probably be a good idea. Pretty easy to do as well with CSS |
11 |
(eg :before & border-radius), but it won't show up in all browsers. |
12 |
Alternatively one could of cource add graphical images which is a bit |
13 |
more "clumsy" & b/w hungry way to do it, but more reliable. What method |
14 |
to choose, if implemented, basicly comes down to how severe one thinks |
15 |
the loss of the visual image & rounded corner is. |
16 |
|
17 |
> - Perhaps the td's of a table should have a wider padding, the text |
18 |
> currently touches the borders (or at least it seems like this) |
19 |
> |
20 |
> |
21 |
I don't understand/see where this text is that touch borders , then |
22 |
again I also think the tables should be replaced in any case. |
23 |
|
24 |
> - Is it a good idea to have the contents indented wrt the titles? Some |
25 |
> people find it less readable - I don't have a personal opinion though, |
26 |
> just passing along |
27 |
> |
28 |
> |
29 |
Feel somewhat like a parrot now, but a tableless design allows for a |
30 |
greater flexibility in indentations/placement of different parts. |
31 |
|
32 |
> - The titles of the news items currently have a colored background. If |
33 |
> you |
34 |
> have two news items with different length, it disturbs the vision a bit. |
35 |
> Can we use a fixed width for this coloring or don't do any color at all? |
36 |
> |
37 |
> |
38 |
My vote would be for preferably no color at all. |
39 |
Colored backgrounds is always a bit "dangerous" to use since not |
40 |
everybody has the same colorvision. In worst case it could make text you |
41 |
are trying to emphasize almost or compleatly unreadable to a person with |
42 |
some deficiency in their ability to see certain colors. Thus though |
43 |
background colors can sometimes look more astetically pleasing, |
44 |
size/boldness/borders are usually a better alternative to highligting |
45 |
something from an accessability POV. |
46 |
|
47 |
> Further, we should take a look at how we would display a plethora on |
48 |
> authors/editors (such as on |
49 |
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml) |
50 |
> |
51 |
> |
52 |
> Aaron's design (see http://www.siphos.be/~svermeulen/gentoo/generic.html) |
53 |
> looks good for one, perhaps a few, authors, but might need some |
54 |
> tweaking for |
55 |
> a larger amount. We can do some magic on this, such as having |
56 |
> Authors: Sven Vermeulen, Daniel Robbins, Chris Houser |
57 |
> Editors: Eric Stockbridge, Rajiv Manglani, Jungmin Seo, Stoyan |
58 |
> Zhekov, ... |
59 |
> but even doing so would generate about 11 categories for the handbook |
60 |
> page. |
61 |
> |
62 |
> |
63 |
That looks like a generally good solution. To solve the "11 categories" |
64 |
problem we could possibly add a show/hide functionality with scripting |
65 |
if people think it's needed. Though I would like to see a mockup of this |
66 |
(I assume) worst case scenario with your suggested layout before making |
67 |
up my mind about if it's needed. |
68 |
|
69 |
/ Stefan |
70 |
|
71 |
PS Aaron, are you on the list now or should I/we continue CCing you |
72 |
directly? |
73 |
-- |
74 |
www-redesign@g.o mailing list |