Show description

The users: The people who will be using the site that the client is paying you to build. 3. You: The developer, who has to work with, scale and maintain the site. You need to remember these stakeholders and make sure you do the right things for the right people for the right reasons. The Client The client doesn舗t care about semantics. The client doesn舗t care about how many IDs and classes you have or haven舗t used. They don舗t want to know that you can舗t quickly duplicate a piece of content because you used an ID and IDs aren舗t reusable.

Each article I read spoke of semantics, clean HTML, and using as few IDs and classes as possible. CSS made its entrance years before my interest in building websites. Tables were phased out and replaced with a far more powerful and suitable language. For many this was a huge change from what they were used to; for me it was just how things were done when I arrived on the scene. The transition from table-based to CSS-based layouts seemed, on the whole, a welcome change. It took a while for some developers to make the move because, as is always the case with front-end development, people were largely at the mercy of the browsers their audiences were using.

Content (forms, typography, images, tables) 6. Footer styles This is obviously a vast simplification, but I really did order style sheets with no appreciation of how the CSS was structured, and with no real regard for the cascade or inheritance. Since starting to work on larger sites, I found that the most effective way to order rule sets was in inheritance order. That is to say, every rule set should inherit from and add to the previous ones. You start with your very basic stuff, your foundations, and you add structure, then components, then visual design.