| 1 |
Michael Curtis Napier wrote: |
| 2 |
|
| 3 |
>You have to remember that we are just trying to finalize the layout |
| 4 |
>right now. The table vs div and the font issues can all be done later. |
| 5 |
> |
| 6 |
> |
| 7 |
Sorry, I guess it's out of habit for me that makes it hard to |
| 8 |
concentrate on layout alone at start. I usually work by transforming a |
| 9 |
well structured highly accessible plaintext-site into something that |
| 10 |
looks pretty on a graphical display. |
| 11 |
Thus layout first while adding underlying markup/CSS/accessibility |
| 12 |
afterwards to me just feels a little bit like trying to make an omelet |
| 13 |
before breaking the eggs. |
| 14 |
|
| 15 |
To some extent doing layout before markup also means having to do at |
| 16 |
least twice the work to reach your target designs look & feel since once |
| 17 |
it looks like how you want to have it you have to tear it all down again |
| 18 |
and almost start from scratch again to merge in good |
| 19 |
accessibility/behaviour and recreate the look that was evolved ontop of |
| 20 |
another underlying structure. |
| 21 |
|
| 22 |
Also, there is a definite risk of locking/limiting yourself into a |
| 23 |
underlying design that is clumsy and aqward to make accessible when you |
| 24 |
are finalizing layout before leting loose the full power of tableless |
| 25 |
CSS controlled design. |
| 26 |
|
| 27 |
In any case, I'll try to write my thoughts down for now and bring them |
| 28 |
up again once we reach that point on the todolist if the rest of you |
| 29 |
prefer the "Layout before Markup" approach. :) |
| 30 |
I'll just keep my fingers crossed that a "final layout" is not |
| 31 |
compleatly set in stone by the time we reach the CSS & Markup stage so |
| 32 |
it becomes too much of an obstacle to also getting the site accessible |
| 33 |
and well behaved. |
| 34 |
|
| 35 |
Regards /Stefan Huszics |
Archives