Datasheet

is encouraged, it’s not required with Expression Web. Expression Web allows the developer to structure
and format content, and even connect to and interact with database/XML data visually using a series of
task panes, wizards, toolbars, and toolboxes. With Expression Web, years of learning and mastering com-
plex authoring and programming languages are now cut down to a matter of days and 16 convenient
chapters.
Your journey through Expression Web begins here with an introduction to the product. Specifically, you
will do the following:
❑ Become familiar with the Expression Web interface
❑ Learn about the many options available within the menu bar
❑ Understand the role of Task Panes
❑ Use and customize toolbars
❑ Learn to recognize and use the Development window, the tag selector, the development area,
the tabbed file chooser, and the Design, Split, and Code views
Throughout the book, certain Expression Web Task Panes, toolbars, windows, and more will be
referenced by name. By the end of the chapter, you will have a solid understanding of where these
components are located. You’ll know which component accomplishes which task and when to use
each. This will serve as a foundation for other, more complex processes throughout the book. Let’s
get started!
Familiarizing Yourself with the Interface
Opening Expression Web for the first time reveals a program that looks and, in many cases, functions
much like other Microsoft products. Falling in line with the “familiarization through consistency” approach,
Expression Web at first glance closely resembles other Office products such as Word, Publisher, and even
its predecessor, FrontPage.
Initially, you’ll notice Expression Web’s Multiple Document Interface (MDI), where numerous windows
(otherwise known as Task Panes), the Document window, toolbars, menus, and so on, converge within a
single parent window shown in Figure 1-1.
The beauty in the MDI approach, as you may have seen by now in other Office products, is that the Task
Panes and toolbars aren’t fixed to the environment (otherwise known as docked). Instead, the toolbars and
Task Panes that facilitate the majority of property modifications for your Web pages can be undocked,
moved to a different area of the development environment, and then re-docked to that particular area.
You can also choose to not dock a Task Pane or toolbar and instead leave it floating on top of other tool-
bars and Task Panes within the development environment. Figure 1-2 provides an example of how you
might choose to customize the development environment.
2
Chapter 1
73155c01.qxd 1/24/07 8:54 PM Page 2