Re: GNU Herds' HTML 4.01 Strict + CSS. -- current state

[Sameer Naik]

hi, sameer here, 
its been a while since i've made any updates on the design front. though i 
thought i would make at least weekly progress, i haven't been able to stick 
with the plan. finally i managed to get some work done and its up at 
www.damagehead.com/gnuherds.org 

changelog:
[1] completed content view styling
[2] completed account management menu
[3] document type is now HTML 1.0 STRICT
[4] updated both default and blue themes

pending tasks:
[1] CSS definition for the login area. forms in general
[2] add logo (still haven't done that, sorry david)

For fellow developers who would like to contribute to the look and feel front 
can download the current design sources here:
http://www.damagehead.com/gnuherds.org/src/

design breakup:
index.php 
        main page with the divs and stuff
layout.css
        CSS that defines the layout.
        contains whats to be drawn where, what are the widths, etc
color/
        the files in this folder contains coloring information, these make up 
the       
        individual themes. i.e. what colors to use, what images to use, etc.
color/default.css
        the current default red look of gnuherds.org. 
color/blue.css
        the experimental blue theme

so designers interested in making a cool new theme(s) could just use/edit 
default.css from color/ and add their own coloring information.
i guess later we could make a collection of all these themes and allow users 
to select their own default theme.

it would be logical if we could move the design to gnuherds servers, just to 
make sure we don't have multiple different versions coming out of the same 
base design and of course work concurrently of the layout specification.

we could now break up the tasks and work on the index.php and layout.css to 
get the whole task to completion. the discussion should be regarding making 
the design take full advantage of CSS such that we should be able change the 
design by just altering the layout.css and not the requiring any changes on 
the index.php, hence not requiring any recoding from the backend developers. 
visit www.csszengarden.com to know what im trying to say.
of other things that we need to finalize on is the names to be given to the 
div's, etc.

at this point i'd like to bring up a new topic.
- how about a new logo for gnuherds.
if this is acceptable to the core gnuherds developers/managers of course. 
designers please send in your designs.

looking forward to your comments and suggestions.
~sameer 

On Saturday 01 December 2007 11:14:27 am Davi Leal wrote:
> Antenore Gatta wrote:
> > * I (antenore) start a new div's layout trying to keep/modify the
> > original.
>
>   Status: http://gnuherds.org/div/
>
> > * Sameer starts from scratch a new div's layout.
>
>   Status: http://www.damagehead.com/gnuherds.org/
>
>   The Sameer's work expose some look & feel improvements, and along the
>   Sameer's conversation some good ideas have raised.
>
> > * Someone else seems to work on a new div's layout as well.
> > * Andrew would like to start from scratch as well.
>
> All guys included in the "To" have contributed or exposed the desire to
> realize or contribute to the HTML-CSS task.
>
> > it would be more convenient to organize better the job.
> >
> > More focus on small tasks (divide et impera)...
>
> There are two sub-task types:
>
>   1) Figure out how to _fit together_ all the main <div>s.
>      Please, see the next link and comment if it is needed:
>        http://gnuherds.org/webpage_main_layout__proposal.png
>
>      Note: That is what Antenore and Sameer have been trying to do.
>
>   2) Convert each <div> content to HTML 4.01 Strict, for heading,
>      menu, ... and the content of each page.
>
>      Victor and me has already done something which you can see at:
>        http://gnuherds.org/doc/tmp/
>      We could just merge it with the current web pages state.
>
>
> All sub-tasks can be done in parallel. Although the main one is (1), which
> as you already know is the more difficult to figure out.
>
> > Maybe we could use the base layout realized by Sameer and subdivide all
> > the div's between us. So for example someone (who wants) could work just
> > on the menu, after Sameer and/or me (and others also) could merge the
> > div's menu in the full layout... Steps by steps?
>
> I agree with you, Antenore. We could work as a team.
>
> That was the plan when we proposed work on a "Save as" copy of the HTML
> code of the home page to realize the (1) sub-task, and later the (2)
> sub-tasks.
>
> As exposed above there are already some <div>s done, for example:
>   http://gnuherds.org/doc/tmp/menu.tpl.gz
> Only some pages were processed, and some of them are now out of sync
> respect to the current state. You can see: http://gnuherds.org/doc/tmp/
>
> Davi