|
Home > Archive > Microsoft Content Management Server > July 2006 > CSS versus table design
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CSS versus table design
|
|
| HokieRTP 2006-07-27, 1:21 pm |
| Hello All -
I have a new client that is asking if we can develop all the templates in
CMS 2002 SP 2 in 100% CSS without any tables. Can this be done and is this a
good idea? Thoughts, comments?
TIA
| |
| Stefan [MSFT] 2006-07-27, 1:21 pm |
| Hi Hokie,
this is not a MCMS related question but a question for general web design
for html/css.
I would suggest to post this question into a html/css related newsgroup.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"HokieRTP" <HokieRTP@discussions.microsoft.com> wrote in message
news:7E45D842-0BD9-4863-AB7C-86B5848251F6@microsoft.com...
> Hello All -
> I have a new client that is asking if we can develop all the templates in
> CMS 2002 SP 2 in 100% CSS without any tables. Can this be done and is
> this a
> good idea? Thoughts, comments?
>
> TIA
| |
| Becky VanBruggen 2006-07-27, 1:21 pm |
| This is not really a CMS question so much as an HTML question. I have done
this for other projects, and it has its advantages and disadvantages. The
advantages are:
- by putting your HTML elements in div tags and assigning the div tags
classes, you can completely rearrange the layout of the entire page just by
changing the CSS file, and without having to touch any of your HTML.
- you can create browser-specific CSS classes that ensure your pages will
look good in any browser
- tables have to wait until all their contents are processed before the
table is rendered to the browser. If your whole page is enclosed in a table,
it slows down the perceptual loading of the page.
The biggest disadvantage is simply a coding one: to fully understand a page
utilizing extensive CSS means you need to have developers who have a firm
grasp of Casacading Style Sheets. Since most developers have a solid
understanding of where an element is positioned on a page when it's built
using tables, most developers prefer to go this route. If a developer is
unsure of how CSS is used, it's hard to look at code an intuitively know
where the element lives on the page. In short, using CSS alone has the
potential to increase development time/headaches.
"HokieRTP" wrote:
> Hello All -
> I have a new client that is asking if we can develop all the templates in
> CMS 2002 SP 2 in 100% CSS without any tables. Can this be done and is this a
> good idea? Thoughts, comments?
>
> TIA
| |
| HokieRTP 2006-07-27, 1:21 pm |
| Thanks for the pros and cons. My questions is more about can CMS templates
handle 100% CSS without any table tags in there, how does it work for those
who have done it.
Thanks for the information!
"Becky VanBruggen" wrote:
[vbcol=seagreen]
> This is not really a CMS question so much as an HTML question. I have done
> this for other projects, and it has its advantages and disadvantages. The
> advantages are:
> - by putting your HTML elements in div tags and assigning the div tags
> classes, you can completely rearrange the layout of the entire page just by
> changing the CSS file, and without having to touch any of your HTML.
> - you can create browser-specific CSS classes that ensure your pages will
> look good in any browser
> - tables have to wait until all their contents are processed before the
> table is rendered to the browser. If your whole page is enclosed in a table,
> it slows down the perceptual loading of the page.
>
> The biggest disadvantage is simply a coding one: to fully understand a page
> utilizing extensive CSS means you need to have developers who have a firm
> grasp of Casacading Style Sheets. Since most developers have a solid
> understanding of where an element is positioned on a page when it's built
> using tables, most developers prefer to go this route. If a developer is
> unsure of how CSS is used, it's hard to look at code an intuitively know
> where the element lives on the page. In short, using CSS alone has the
> potential to increase development time/headaches.
>
> "HokieRTP" wrote:
>
| |
| Becky VanBruggen 2006-07-27, 7:20 pm |
| The short answer is, yes, I have done a CSS-only implementation of CMS, and
the answer is no, there is no problem. Go for it.
"HokieRTP" wrote:
[vbcol=seagreen]
> Thanks for the pros and cons. My questions is more about can CMS templates
> handle 100% CSS without any table tags in there, how does it work for those
> who have done it.
>
> Thanks for the information!
>
> "Becky VanBruggen" wrote:
>
|
|
|
|
|