Comments on: Why the class name “wrapper” is so common

By: Alex

Alex — Mon, 12 Oct 2009 12:07:58 +0000

because it´s describes the functionality accurate! hillos is right “there’s a wrapper everywhere” :)

By: hillos

hillos — Sat, 03 May 2008 16:33:25 +0000

now there’s a wrapper everywhere :P

By: Dave

Dave — Fri, 02 May 2008 19:23:17 +0000

I think CMS’s usually fail at producing quality output because by their nature, CMS’s are intended to have low-quality input from untrained users.

Still, I don’t understand why CMS’s have such horrible CSS support. Maybe it’s just in the K12 education CMS’s I’ve worked with.

By: Olly

Olly — Fri, 02 May 2008 14:39:32 +0000

I think the reason is much simpler than that. Fixed-width layouts often need a div to wrap around all the content, wrapper seems like a good name for it.

As for semantics not taking a hold in the CMS world, that’s a whole different problem. The blame lies with CMS vendors, the WYSIWYG editors they use, and the people who implement the products. There’s a lot of education that still needs to happen.

By: Emil Stenström

Emil Stenström — Fri, 02 May 2008 07:21:28 +0000

@Rasmus Kaj: Does that mean you’re against CMS:es?

By: Rasmus Kaj

Rasmus Kaj — Thu, 01 May 2008 22:30:06 +0000

If the person creating the design of a site doesn’t know anything about the content, I think xe should ask someone.

Design is about communication, and I think the person doing the design should know what kind of information it will be used to communicate.

By: Devon

Devon — Wed, 30 Apr 2008 17:04:30 +0000

This points to another benefit of HTML5, since common class names will become element names (footer, aside, etc), making it a little easier on CMS makers & web developers who use them.