Re: <div>s based layout

[Sameer Naik]

hi, 
first of, i am sorry for not having responded earlier. i had a rather tiring 
work week.

On Wednesday 31 October 2007 1:32:58 pm Antenore Gatta wrote:
> This would be a "brain storming" regarding the div's layout.
> 
> On 10/28/07, Davi Leal <address@hidden> wrote:
> 
> >
> > I have updated the expected deadline of the <div>s task to September 2009.
> 
> 
> As the end deadline it's fine, but I'd suggest a different approach.
> IMHO is better to define a migration strategy with shorter deadlines, in
> this way we can already rewrite small piece of the CSS and take directly
> advantage of the modifications and without risking to put in place a whole
> new bugged design.
i'll work om making the first CSS design draft as simple, and as modular as 
possible. simplifying the backend migration.
then we can build on adding new interface extensions
> 
> See below my proposal.
> 
>   task: http://savannah.nongnu.org/task/?6177
> >
> >
> > Some guy has advised just checkout the themes from a CMS like Drupal. It
> > is
> > said that the GNU Herds layout is pretty typical for them, and they're
> > nearly
> > all well written CSS-based websites.
> 
i do not recommend this approach, little time consuming. after all its just 
CSS and HTML, not rocket science ;) 
> 
> Personally I prefer to develop our own CSS and honestly I don't like so much
> the default Theme (I on't have time to see others).
> More over I think it takes too much time too analyze and adapt another CSS
> to our needs (always IMHO).
> 
> My proposal is....
> 
> 1. Layout migration section by section.
> 
> Identifying the sections and pages that will most benefit from the
> conversion will simplify the whole work.
> I think that as a good start we should focus our attention to the content,
> fixing headings and paragraphs, removing <br> and <b> (search for <b>ad and
> <br>eakfast ;-) , replacing where possible tables with div/lists, paddings
> and margins.
> Cleaning the base html tags styles.
> 
right.
> 2. Logical divisions of content.
> 
> This should the second logical step. We should identify our pages for
> logical divisions of content.
> I mean something like:
> 
>    - Main menu
>    - Login/registration menu
>    - Option/languages menu
>    - Headers and footers
>    - Content
>    - Related information
>    - Others...
> 
> And start to replace these with divs and lists (ul) where possible and/or
> fixing existing tables.
> 
the layout of the page, menu positioning , needs to be defined. the colors and 
look can be done later.
> 3. Look and feel.
> 
> When the content will be more organized and clean we can start to think
> about the look.
> 
>    - Colors.
>    - Header style.
>    - Menus positioning.
>    - and so on...
> 
> All of these always taking care of usability and accessibility (feeling)...
> 
right...
> What do you think?
> 
> Cheers
> Antenore.
>