[thelist] your opinion solicited on coding specs I requested from contractor

[martin.p.burns at uk.pwcglobal.com]

Memo from Martin P Burns of PricewaterhouseCoopers

-------------------- Start of message text --------------------

Or better, not to use classes to replace semantic or structural info, so
instead of
<div class="intro_title">
use
<h2 class="intro_title">
The class styles the structrual tag. This is actually part of the WAI
guidelines -
you should use semantic/structural markup wherever possible.

Worse is where people do this kind of rubbish:
<p><span class="foo">aslda d;aj dlkajsdlkajdla dl</span></p>
(it's pretty common out of GoLive)

If .foo has a different leading value or font size, the last line will
be oddly leaded.

Instead, do
<p class="foo">asdkj ald akd olihj</p>

And don't get me started on people who recreate the look of
hierarchical lists with tables... (minor exception where lack of
width is a factor and the client insists on 3+ levels of list, say
in a nav bar)

Cheers
Martin



Please respond to thelist at lists.evolt.org

Sent by:  thelist-admin at lists.evolt.org

To:   thelist at lists.evolt.org
Subject:  Re: [thelist] your opinion solicited on coding specs I requested
      from contractor

Sorry, I'm a bit late with this, but I'd add two things to your specs.

2. Specify that they must use classes that are a description of the style,
not
what the style is used for. For example, instead of using <span
class="Intro_title">Hello world!</span> They should put <strong
class="large_bold">Hello world!</strong>. I find that CSS, especially in a
large project with different people using it at different times gets very
confusing. So people end up using <span class="Intro_title"> on things that
are
not an introduction or a title, or they make up a new class, exactly the
same
as intro_title and your style sheets become unmanageable and redundant.


spinhead wrote:

> I wrote this last year for the guys who coded our site. We're coming up
on a
> complete redesign (new VP of Marketing) and I'm interested in your take
on
> it. My perspective is that I don't have time to do the initial coding,
but I
> know I'll be maintaining it. I've focused on the things that I've found
> difficult or frustrating in the past.
>
> Any glaringly stupid requirements? Am I missing anything really
important?
> (The last group claimed this was perfectly acceptable, then delivered
> something which was pretty close but didn't work in Netscape, so they
blew
> away all concept of modular code and copied and pasted 15k chunks into
every
> page to get the navigation to work; therefore, I don't have a real feel
for
> whether or not this works in the real world.)
>
> The best suggestion will be rewarded with a happy face. Like this :)
>
> Oh; you thought I'd e-mail you a pint or something?
>
> spinhead
>
> ---------------------------------------
> For unsubscribe and other options, including
> the Tip Harvester and archive of TheList go to:
> http://lists.evolt.org Workers of the Web, evolt !


---------------------------------------
For unsubscribe and other options, including
the Tip Harvester and archive of TheList go to:
http://lists.evolt.org Workers of the Web, evolt !


--------------------- End of message text --------------------

This e-mail is sent by the above named in their
individual, non-business capacity and is not on
behalf of PricewaterhouseCoopers.

PricewaterhouseCoopers may monitor outgoing and incoming
e-mails and other telecommunications on its e-mail and
telecommunications systems.
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.