| 1 |
Good points. However, the layout was voted on and chosen in advance of |
| 2 |
the markup creation. As swift said in the outline, it's not set in |
| 3 |
stone but it should be followed as a reference. The actual site is done |
| 4 |
by an xsl backend and the final html is just templates. So in essence |
| 5 |
the "text site" you are referring to already exists. We're just |
| 6 |
reworking the layout and design. |
| 7 |
|
| 8 |
For now we need a layout to follow in order to create those templates. |
| 9 |
Once I get a testing backend up and running we can start actual work on |
| 10 |
the templates and finalize the layout. For now we need to concentrate |
| 11 |
on a *general* layout so we have something to follow. |
| 12 |
|
| 13 |
|
| 14 |
--- Stefan Huszics <sauron@×××××××.se> wrote: |
| 15 |
|
| 16 |
> Michael Curtis Napier wrote: |
| 17 |
> |
| 18 |
> >You have to remember that we are just trying to finalize the layout |
| 19 |
> >right now. The table vs div and the font issues can all be done |
| 20 |
> later. |
| 21 |
> > |
| 22 |
> > |
| 23 |
> Sorry, I guess it's out of habit for me that makes it hard to |
| 24 |
> concentrate on layout alone at start. I usually work by transforming |
| 25 |
> a |
| 26 |
> well structured highly accessible plaintext-site into something that |
| 27 |
> looks pretty on a graphical display. |
| 28 |
> Thus layout first while adding underlying markup/CSS/accessibility |
| 29 |
> afterwards to me just feels a little bit like trying to make an |
| 30 |
> omelet |
| 31 |
> before breaking the eggs. |
| 32 |
> |
| 33 |
> To some extent doing layout before markup also means having to do at |
| 34 |
> least twice the work to reach your target designs look & feel since |
| 35 |
> once |
| 36 |
> it looks like how you want to have it you have to tear it all down |
| 37 |
> again |
| 38 |
> and almost start from scratch again to merge in good |
| 39 |
> accessibility/behaviour and recreate the look that was evolved ontop |
| 40 |
> of |
| 41 |
> another underlying structure. |
| 42 |
> |
| 43 |
> Also, there is a definite risk of locking/limiting yourself into a |
| 44 |
> underlying design that is clumsy and aqward to make accessible when |
| 45 |
> you |
| 46 |
> are finalizing layout before leting loose the full power of tableless |
| 47 |
> |
| 48 |
> CSS controlled design. |
| 49 |
> |
| 50 |
> In any case, I'll try to write my thoughts down for now and bring |
| 51 |
> them |
| 52 |
> up again once we reach that point on the todolist if the rest of you |
| 53 |
> prefer the "Layout before Markup" approach. :) |
| 54 |
> I'll just keep my fingers crossed that a "final layout" is not |
| 55 |
> compleatly set in stone by the time we reach the CSS & Markup stage |
| 56 |
> so |
| 57 |
> it becomes too much of an obstacle to also getting the site |
| 58 |
> accessible |
| 59 |
> and well behaved. |
| 60 |
> |
| 61 |
> Regards /Stefan Huszics |
| 62 |
> > begin:vcard |
| 63 |
> fn:Stefan Huszics |
| 64 |
> n:Huszics;Stefan |
| 65 |
> email;internet:sauron@×××××××.se |
| 66 |
> tel;home:0906991299 |
| 67 |
> tel;cell:Comviq 0709995490, Telia 0738177875 |
| 68 |
> x-mozilla-html:FALSE |
| 69 |
> version:2.1 |
| 70 |
> end:vcard |
| 71 |
> |
| 72 |
> |
| 73 |
|
| 74 |
-- |
| 75 |
www-redesign@g.o mailing list |
Archives