Results 1 to 25 of 139
Dec 29, 2010, 06:25 #13
- Join Date
- Mar 2006
- Yorkshire, UK
- 90 Post(s)
- 1 Thread(s)
Second, you're tied in to using a particular platform there - Dreamweaver. CSS is independent, and so you can use whatever software, frameworks and templates are best at any time, you aren't stuck with using the same one for ever more just because that's how you built the site in the first place.
2) Faster Load Times Because of Lighter Code Ė I remember load times being a major issue when I first got started but it doesnít seem to be the case anymore with so few people on dialup.
4) Separation of Style and Content Ė I guess this one is related #1, ease of updating?
This is what Dreamweaver template files do. It separates style from content (editable/un-editable). I donít know about you, but generally speaking what my clients want most often is to update the content. I donít understand why it would be easier to update content using CSS more so than tables. (Remember, I DO use CSS for formatting.) If they want to tweak something in the design, again, piece of cake to do. Just change the template file. Itís not hard.
5) Greater Consistency Ė If you use template files and CSS, where is there inconsistency?
1) Inconsistent Browser Support - Different browsers will render CSS layout differently as a result of browser bugs or lack of support for various CSS features.
Personally, if I could instantly convert a design into HTML, Iíd do it.
The foundation of a website is its contents. Start with that. Basic text, wrapped in <p>s. Headings, marked up with <hx>s. Navigation lists, marked as <ul>s. And so on. A bare-bones plain text page, of the sort we used to see back in the early 90s. Then you can think about the layout and the design. Where do you want this bit to go? Where do you want that bit to go? What styling do you want there? Build it from the ground up, and you'll get a much more flexible design than if you try to painstakingly replicate a layout that was never right for the medium in the first place.
Most table-based layouts don't make any of that easy, or often even possible. The more complex the layout, the more likely that when it is linearised (by a speech synthesizer, a mobile phone, a search spider, or someone trying to highlight the text to copy and paste it into another application), it all goes haywire, and you find that the contents doesn't follow a logical sequence from start to end, but jumps around all over the place.
Being a good web designer requires a range of skills. You need to understand HTML code, CSS and the way they work together. You need an eye for visuals and graphics, for colour and shape. You need to know the technological constraints and opportunities the medium has. Different people come to web design from different routes, different backgrounds and with different skill-sets. They can all be equally valid starting points, but that's what they are. A truely good web designer will take the time to learn all of those skills; anything less and you won't be doing the best job you can.
Maybe the decision to go CSS or table depends on who you are, how you like to work, and who your clients are.