… and fat bloated train wreck design can tank even the most basic of sites in terms of user experience – which is what the majority of “designers” seem to do. Sometimes you have to have the authority to tell the designer “NO!”.
A good example of someplace someone should have been told NO is on Sitepoint’s products page – fixed height background images, dynamic fonts over fixed height elements, no planning for what happens when it word wraps – take a look at it on a LF/120 dpi machine to see how badly it falls apart.
Much less the artsy fartsy layout elements and “gee aint it neat!” bloated scripting that result in wasting 526k total on delivering 5k of plaintext and ten content images.
In other words layout (CSS’ job) and things that should be dictated by the CONTENT… Too many websites it’s painfully obvious the content is shoe-horned into some pretty picture an artist drew making the site painfully slow to load, painfully bad to navigate, painfully broken from an accessibility standpoint, etc, etc…
Though you are quite correct in pointing out there’s more to design than the graphics; there’s usability, accessibility, and total bandwidth consumption which generally is when you have to start telling the PSD jockey “OH <snip /> NO!” and shine up the point of your boot using their rectum.
I find ‘wireframes’ and ‘mockups’ (and that’s what these alleged templates really are, mockups) invariable cause MORE headaches for me since they often do NOT work how I would make logic flow decisions in outputting my content… But then I don’t think just ONE appearance when coding a site; I code for screen, screen with images disabled, handheld, CSS not present, print – they all get different appearances crafted for the best user experience of each – a single crappy mockup for 96 dpi often gets in the way of doing that.
What the devil does the hardware have to do with it?!? Unless you’re talking bandwidth related hardware, in which case you’re going to tell the user what they can and cannot connect with? Tell that to the guy in Coose County NH where 28.8 is a good day.
I have, but I generally refuse to code support for alpha .png, DEMAND that all elements be able to be dynamically resized making elements like this one for example:
Be a “Try again Charlie”. Completely non-viable non-deployable element to have text atop as SitePoint does on their products page.
That however I do wholeheartedly agree with – I based a lot of what I said just looking up the ‘clients’ off the sites in OP’s signature… where 500k of javascript for nothing and megabyte plus site sizes appear to be the norm, even on the simplest of pages where there’s less than 1k of content… basically sites I would NEVER allow a client to deploy on hosting costs and likely bounce-rate ALONE.
ALL of them having broken layouts here too.
Without seeing the layout in question we are all just making wild guesses – I assumed since he was taking issue with it that it’s your typical “guy who knows nothing but photoshop” drawing goofy pictures that are completely impractical trash so far as web design is concerned – that MAY have been a overreaction; it’s just the reaction I get every time I deal with the PSD first crowd.