If you’re familiar in any way with Dreamweaver as an authoring tool, you understand that there are three different “views” or ways of looking at a web-page. There’s code view, design view and split view. People who are learning to create a web-page while simultaneously becoming comfortable with the application (Dreamweaver) itself often default into using the design view. As a rule, there’s nothing wrong with this approach. However, working in this WYSIWYG (what you see is what you get) mode doesn’t necessarily produce clean code or accessible (we’ll talk about accessibility in a minute) websites. After a while the learner will start to hear about CSS style sheets, typography, load times, and accessibility and begin to wonder if migrating towards working exclusively with code would be beneficial. Let’s review the reasons that one might choose to make the move.

Next Section: Rationale