Coding; Some Food for Thought
Hey guys, I thought I’d write about coding - that’s right, coding in general.
The design:
Something I’ve recently came across, is www.myp90x.net. Look carefully at the navigation and how it was coded, even visually it looks wrong. I’m pretty sure the reason the last tab has more lighting on it is because it’s supposed to be a rollover, not just supposed to be static (Apologies if it’s not, I’m just using your website as an example). Look here:
See how it has more, I suppose you could say gloss on it? Maybe the coder never understood what was meant by it, or maybe the coder was just lazy - who knows! Do you think that the designers should maybe start to give a text file on what’s expected of the layout when it gets coded to help the coder understand what is meant, instead of making silly little mistakes such as that, or running back to the designer for help.
Images, which could easily be text:
you may not see it, as it’s just an image - but the text on it is static on the actual image itself, and the only way the track my progress button is going to be clicked, would be by using an image map, which I would say isn’t the best way to do it.
The navigation code:
After looking at the code, it also appears that the nav was coded in multiple divs, here’s a snippet:
There was no need for the multiple divs and could have been done using the same one class and with a lot less code.
All it would have required was using li’s and it would have worked but more optimized and faster (Yes, even the split millisecond counts to webdevelopers!)
Sorry for picking on myp90x.net here, just that your website is a prime example. I happen to feel that the design for the site is fantastic, and although the coding isn’t bad at all really, it does touch on some important aspects which were perfect for making points in this article.
I suppose that’s all from me just now, cheers!