List Archive: www-redesign
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Good points. However, the layout was voted on and chosen in advance of
the markup creation. As swift said in the outline, it's not set in
stone but it should be followed as a reference. The actual site is done
by an xsl backend and the final html is just templates. So in essence
the "text site" you are referring to already exists. We're just
reworking the layout and design.
For now we need a layout to follow in order to create those templates.
Once I get a testing backend up and running we can start actual work on
the templates and finalize the layout. For now we need to concentrate
on a *general* layout so we have something to follow.
--- Stefan Huszics <sauron@...> wrote:
> Michael Curtis Napier wrote:
> >You have to remember that we are just trying to finalize the layout
> >right now. The table vs div and the font issues can all be done
> Sorry, I guess it's out of habit for me that makes it hard to
> concentrate on layout alone at start. I usually work by transforming
> well structured highly accessible plaintext-site into something that
> looks pretty on a graphical display.
> Thus layout first while adding underlying markup/CSS/accessibility
> afterwards to me just feels a little bit like trying to make an
> before breaking the eggs.
> To some extent doing layout before markup also means having to do at
> least twice the work to reach your target designs look & feel since
> it looks like how you want to have it you have to tear it all down
> and almost start from scratch again to merge in good
> accessibility/behaviour and recreate the look that was evolved ontop
> another underlying structure.
> Also, there is a definite risk of locking/limiting yourself into a
> underlying design that is clumsy and aqward to make accessible when
> are finalizing layout before leting loose the full power of tableless
> CSS controlled design.
> In any case, I'll try to write my thoughts down for now and bring
> up again once we reach that point on the todolist if the rest of you
> prefer the "Layout before Markup" approach. :)
> I'll just keep my fingers crossed that a "final layout" is not
> compleatly set in stone by the time we reach the CSS & Markup stage
> it becomes too much of an obstacle to also getting the site
> and well behaved.
> Regards /Stefan Huszics
> > begin:vcard
> fn:Stefan Huszics
> tel;cell:Comviq 0709995490, Telia 0738177875
email@example.com mailing list