1 |
> Xavier Neys wrote: |
2 |
> |
3 |
>> Curtis Napier wrote: |
4 |
>> |
5 |
>>> Xavier Neys wrote: |
6 |
>>> |
7 |
>>>> Links to GWN RSS feeds are not properly displayed: |
8 |
>>>> http://wwwredesign.gentoo.org/news/en/gwn/gwn.xml |
9 |
>>>> http://www.gentoo.org/news/en/gwn/gwn.xml |
10 |
>>> |
11 |
>>> |
12 |
>>> I forgot to copy over the image. fixed. |
13 |
>> |
14 |
>> |
15 |
>> The xml image is underlined and it's darn ugly IMHO. |
16 |
> |
17 |
> |
18 |
> It's even worse on printable pages: |
19 |
> http://wwwredesign.gentoo.org/news/en/gwn/gwn.xml?style=printable |
20 |
|
21 |
Is it OK now? |
22 |
|
23 |
> Xavier Neys wrote: |
24 |
> |
25 |
> I prefer a list of links to older news just like on the current site, |
26 |
> but obviously not crammed in the left margin anymore. |
27 |
> I you choose the "more news" approach, fair enough, but why use an extra |
28 |
> /main/en/morenews.xml file with an extra ID that has to be defined in |
29 |
> the DTD even though those IDs are not use anymore and extra logic in the |
30 |
> xsl? |
31 |
> All you need is a "?newsitemcount=20" link. |
32 |
> |
33 |
|
34 |
I went with the newsitemcount solution. Why didn't I think of that? Oh |
35 |
well, it's fixed now. |
36 |
|
37 |
>> |
38 |
>> 2. This design/layout does not lend itself very well to font resizing. |
39 |
> |
40 |
> |
41 |
> Fair enough. It feels weird that some much emphasis has been put on |
42 |
> accessibility but a site that does not allow visually-impaired users to |
43 |
> grow their fonts is OK. |
44 |
> |
45 |
|
46 |
I'm working on this one. I think after the past year of this I have |
47 |
started to lose sight of a few major principals and have gotten |
48 |
sidetracked. I stepped back today and really looked at everything and I |
49 |
made some major changes to the underlying structure in the content area |
50 |
that will improve the way it handles increased font sizes/small windows. |
51 |
I'm still working on the menu but I should have it done by tomorrow. |
52 |
|
53 |
More about this at the end of this mail. |
54 |
|
55 |
>> 4.2 The nav bar is within the /xsl/handbook.xsl file. I was told not |
56 |
>> to touch that file. I take your suggestion to change the nav bar as |
57 |
>> permission to touch it now. Swift, if you still want me to not touch |
58 |
>> the handbook let me know and I'll drop in the unchanged one. I have |
59 |
>> started experimenting with how to make that nav bar better, if anyone |
60 |
>> has any ideas let me know. |
61 |
> |
62 |
> |
63 |
> Improving could be done, simply removing the <hr>'s is not an improvement. |
64 |
> Anyway, this should not be a requirement to more on with this project IMO. |
65 |
> |
66 |
|
67 |
I'm still working on the handbook menu, anybody have any ideas? I'm |
68 |
going to try the green arrows somehow or other unless someone can come |
69 |
up with something better. |
70 |
|
71 |
|
72 |
> 2nd & 3rd level title look better. |
73 |
> I can't say as much of the top titles :( |
74 |
> |
75 |
|
76 |
How are the titles now? |
77 |
|
78 |
> BTW, numbered chapters in the handbook index would be better IMO |
79 |
> (http://wwwredesign.gentoo.org/doc/en/handbook/handbook-x86.xml) |
80 |
> |
81 |
> Besides, guides start with an unordered list, book chapters start with a |
82 |
> numbered list. Neither has any "Content" title. |
83 |
> |
84 |
|
85 |
I made all the content lists numbered/lettered and added "Content:" to |
86 |
them. Look at the Handbook (the main handbook index AND the content) and |
87 |
a guide and see what you think. Is this good? |
88 |
|
89 |
------------------------------------- |
90 |
|
91 |
I made a major change to the content area. I did this to address the |
92 |
problem of "Dead Space" under the ad bar that several people have |
93 |
complained about and to help make the site degrade properly when fonts |
94 |
are increased or the window is small. |
95 |
|
96 |
Doing this caused a problem with block items overlapping the ads. This |
97 |
is because in order to get text to wrap under it (ad bar) I had to float |
98 |
it instead of absolutely positioning it. Items like: warning, important, |
99 |
note and codetables had to change the way the title is done from a div |
100 |
to a span to keep the background color from stretching across the page |
101 |
and overlapping the ads. The bottom part of them is now a <p> instead of |
102 |
a div for the same reason. The header will now only have a colored |
103 |
background directly under the text instead of a banner that goes across |
104 |
the page. Other than that it still looks the same. |
105 |
|
106 |
Look for this in the next few days: I'm going to be making a change to |
107 |
the way the menu works (not the way it looks, only the HTML that renders |
108 |
it). The change will make it degrade more gracefully with larger fonts |
109 |
or in small windows. As usual IE is giving me lots of headaches or I |
110 |
would already have it done. |
111 |
|
112 |
Thanks for bringing this up neysx. You are right, if I am going to focus |
113 |
on accessibility I need to apply it everywhere and not selectivly. |
114 |
|
115 |
It's all coming together now thanks to the excellent feedback. Keep it |
116 |
coming people! :-) |
117 |
|
118 |
-Curtis |
119 |
-- |
120 |
www-redesign@g.o mailing list |