|
Chapter 10: Creating Web Sites with FrontPage
Chapter 10 Creating Web Sites with FrontPageWhen you watch the news on TV, the only "equipment" you need is the TV and a place to sit. But what about when you rent a video or order a pay-per-view movie that's filled with cool special effects and has an awesome soundtrack? Instead of turning to grandma's 13-inch hand-me-down TV, you'd probably prefer the ultimate in home entertainment systems: You know, the rare setup that can be easily controlled by a single remote control and has an ultra-clear big-screen TV, digital cable, Dolby stereo, and surround sound components artfully blending into the shadowsall strategically placed for optimal viewing and listening pleasure from the comfortable folds of an enormous leather couch. Granted, these "extras" aren't strictly necessary, but they sure can make a big difference sometimes. The same can be said of HTML editors. Notepad (a basic text editor) can be likened to the "TV, seat, and remote control" way of creating Web pages, whereas FrontPage provides the "luxury home entertainment system" approach to Web site development. In this chapter, we're going for the "extras."To create the Web pages described in this chapter, you'll need the following "supplies":
To download these files, create a folder named "sky" on your computer's hard drive. (For convenience, we refer to your hard drive as the C:\ drive throughout this chapter.) Then connect to www.creationguide.com/projects/chapter10/text, right-click mars.doc, select Save Target As, and save the file to the C:\sky folder on your computer. Repeat the process to save thankyou.htm to your C:\sky folder.
To obtain these figures, first create an images folder in C:\sky. Then connect to www.creationguide.com/projects/chapter10/images, right-click an image's filename (or the Zip file if your computer is set up to open Zip files), choose Save Target As, and save a copy of the file to the C:\sky\images folder on your computer, as shown in Figure 10-1. Repeat the process for each image. Figure 10-1 Before you can complete this project, you need to download the image files from the Internet.
Introducing FrontPage: A Full-Featured HTML EditorFor this book's final project, we show you how to use FrontPage to create a fairly advanced Web site. FrontPage is a full-featured HTML editor that you can purchase as a stand-alone application or as part of Microsoft Office XP Developer. As you'll see in this chapter, using a true HTML editor such as FrontPage opens numerous doors to Web page design for beginning designers. Full-scale HTML editors also provide some handy shortcuts for more seasoned designers. Our goal is to give you firsthand experience in creating a Web site that uses a number of Web page elements that are easily implemented using full-fledged HTML editors. These elements include (but are not limited to) the following:
Before you see how easily you can use FrontPage to create the preceding elements, let's give the FrontPage interface a quick once-over to preview where you're headed.
Strolling Past the FrontPage WindowMuch of the FrontPage interface is similar to that of other Office applications. In other words, when you first open FrontPage, you'll probably feel that it looks quite familiarthat is, if you're used to working in Office. In fact, at first glance, you'll see the Standard and Formatting toolbars across the top, menu bar options, a workspace area, and a status bar along the bottom. But in addition to the standard fare, FrontPage offers a couple key interface options to assist you in creating Web pages. Namely, the FrontPage interface includes a Views bar and three view optionsNormal, HTML, and Previewas shown on the left in Figure 10-2. These elements will help you track the multiple files and folders of your Web site, preview Web pages during development, edit HTML source code, manage hyperlinks, and more. For example, you can use the HTML view to access a Web page's source code, as shown on the right in Figure 10-2, and the Preview view to preview Web pages as you build them. You'll be using all three views in this chapter's project.As you'll soon see, taking advantage of many of the features in FrontPage requires you merely to select menu options, click toolbar buttons, and complete dialog boxesactivities you should be accustomed to if you're a veteran of other Office programs, such as Microsoft Word. Therefore, although FrontPage is considered a high-end HTML editor with advanced Web development capabilities, you should feel comfortable working within its interface pretty quicklyeven if you've never composed so much as a single text-based Web page in an HTML editor. Regardless of any predevelopment jitters, we're confident that if you work through this chapter's project, you'll have a strong grasp of FrontPage's capabilities. Figure 10-2 For the most part, you'll design a FrontPage Web page in Normal viewing. At times, you might need to view and edit a FrontPage Web page's source code in HTML view.
The Advantages of Using FrontPageLike all full-service HTML editors, FrontPage sports some definite advantages. FrontPage is fairly easy to use (after you know where to look and what you're looking for), it provides many advanced design features, and it creates HTML code automatically. Using FrontPage, you can easily create professional-looking Web pages with just a few clicks. Throughout the project in this chapter, we highlight a lot of FrontPage's functionality. Our reasoning for covering a wide range of FrontPage capabilities also includes a hidden benefit: You'll learn how to create Web pages in FrontPage, and you'll also learn about HTML editors in general.Mastering applications (such as HTML editors and word processors) entails knowing the typical functions available in the application. For example, you know that most word-processing applications have a Find feature. Thus, regardless of the word-processing application you're using, if you need to find text, you probably look automatically for the application's Find or Search tool. Similarly, with HTML editors, if you learn some of the capabilities of FrontPageand it has a lot of themyou can benefit from that knowledge when you work in similar environments. So using FrontPage as a model, you'll be introduced to a selection of tasks that most HTML editors offer. That way, if you later decide to design Web pages using another HTML editor, you'll have a good idea of the types of features to look for. Or if you decide to design your Web pages in FrontPage, you'll be way ahead of the game.
FrontPage Server ExtensionsThe final issue we need to touch on before we get going on the chapter project is FrontPage Server Extensions, which are specific to FrontPage. Before the onset of advanced HTML editors, developers had to write, buy, or copy code to enable certain Web page features, such as forms, counters, Java programs, and so forth. FrontPage provides the code for many of these features, enabling designers to easily include functionality that requires some codingwithout having to manually insert code or acquire the code in some other way. The catch is that your server (or your hosting service) needs to support FrontPage Server Extensions. So before you go crazy using the advanced design features of FrontPage, check with your Web hosting service to verify that they support FrontPage Server Extensions.
You can control whether a Web page you're building includes components that require FrontPage Server Extensions. The easiest way to avoid extension-reliant features is to configure FrontPage to deactivate (and dim) features that require extensions. When you do this, you avoid including components that rely on your server's capabilities (because FrontPage won't allow you to insert extension-reliant components). To control the availability of features requiring FrontPage Server Extensions, do the following:
After you complete the preceding steps, all features that require extensions appear as dimmed options in menus and dialog boxes, and any components already installed on the page are disabled and the related HTML code displays as gray text.
In this day and age, most hosting services support FrontPage Server Extensions. You'll definitely find some exceptions, including hosting services that support some but not all of the FrontPage Server Extensions. So if you're shopping for a hosting service and think you'll be using FrontPage extensions (such as for a FrontPage page hit counter), you'll want to ensure that your hosting service supports FrontPage Server Extensions before you plunk down any cash and commit to the hosting service's plan. For our purposes in this chapter, however, you don't need to have server space to create the project. For the most part, you build the site locally on your computer, so you won't need to worry about server space and FrontPage Server Extensions until you're ready to publish your Web site online (that is, "go live") or if you want to test the publishing feature in FrontPage by publishing the project site. We talk a little about publishing FrontPage sites later in this chapter, but you'll need to consult one of the references in the section "Additional Resources" for a full discussion of this topic as well as turn to Chapter 11 for some Web publishing tips. At this point, you know enough to get started on the project. So let's forge ahead to our final frontier in this book's Web-site-development section and have some fun creating a Web site in FrontPage!
Planning Your FrontPage Web SiteWhen we initially planned this chapter's project site, we intended to create a team page featuring a fictitious softball team. Unfortunately, we couldn't bribe enough of our friends to pose for the team picture, so we opted to create a Web site for an astronomy club instead. We ended up incorporating many of the functionalities we had originally planned for the softball site into the astronomy site. For example, instead of making an image map out of a team picture, in which you could click each person's head to access a stats or personal page, we used a solar system image map in which you can click each planet to access a page of information about that planet. We hope that as you experiment with the techniques we present in this project, you'll begin to think of ways you can vary them to create custom Web sites.After determining that an astronomy club site would suit our purposes, we decided that the site should consist of a custom home page linking to standard-format subpages. Using a nonstandard home page is a common Web site design technique used to make the home page stand out from the subpages. Because FrontPage offers so many options, we felt that showing a nonstandard home page made good design sense and would also enable us to show you a few additional features of FrontPage. To see our planning process, take a look at Figures 10-3 through 10-5. Figure 10-3 shows a sketch of the Big Dipper design we came up with for the home page. Figure 10-4 shows the sketch of the standard subpage layout. And finally, Figure 10-5 shows the astronomy club site's storyboard. Figure 10-3 A sketch of the astronomy club's home page shows the big dipper containing links to the site's main subpages. Figure 10-4 A sketch of a typical astronomy club subpage shows that the subpages will be structured differently from the home page. Figure 10-5 Storyboarding the astronomy club's Web site clarifies the Web site's hierarchy. Because of the relative complexity of the home page, you're going to create that page last. In this project, you'll start the design process by solidifying the site's standard layout for subpages by creating a subpage.htm document that you can use as a template to create the site's pages. But first, before you begin building Web pages, you need to tell FrontPage that you want to create a new Web.
Creating a New WebAs we just mentioned, the first step to designing a Web site is to express your Web-page-building intentions to FrontPage by creating a new Web. To do so, follow these steps:
You're now ready to create a standard subpage that you can use as a template for the astronomy club's Web site.
Creating the Subpage LayoutIn this section you'll create a standard subpage layout that you'll be able to copy and use to create foundation pages for each subpage in the site. First you'll set the subpage's page properties.
Setting Page PropertiesTo begin, ensure that you have a blank workspace displaying in FrontPage. If you followed the steps in the preceding section, you should be set. Here are the steps to create a basic subpage:
Figure 10-6 You can enter title text in the Page Properties dialog box.
Figure 10-7 To assign a background image to your Web page, select bg.gif in the Select Background Picture dialog box.
Figure 10-8 The completed Background tab shows the default colors you selected for the current Web page. Even though the project uses the default hyperlink colors, you should click each component's color boxes to replace the "automatic" color setting for each element. If you don't replace the automatic colors with specified colors, some browsers might insert custom hyperlink colors that might not work well with your sitefor example, if a user's "visiting" hyperlinks are set to black, the links will disappear into the black background after the user clicks them.
Saving Your WorkBefore you get too far along, you should save your work. You'll be able to use the same basic settings for all subpages, so you'll save the page you're currently creating as a generic template that you can copy to create all the site's subpages. To save the current file, follow these steps:
Figure 10-9 You configure the Set Page Title dialog box to modify a page's title text.
Adding the Logo and the Title Banner GraphicIn this section you'll continue to configure the subpage template by inserting the astronomy club's logo and title banner graphic, which appears along the top of every page:
At this point, the logo is linked to the (future) home page, and both graphics are inserted and left-aligned by default. In most browsers, the left alignment will help keep the graphics side by side, but because two images span the top of your page, the title bar could feasibly wrap to the next line in some browsers if users resized their browser windows to a very small size (in which case the logo would display on the top line and the title bar would display flush-left below the logo graphic on the next linenot the effect you're after for this Web site). Just to be safe, you can add the "no break" (<NOBR></NOBR>) HTML tags to your page's source code to specify that the two graphics should be kept together regardless of the browser's window size.
Before you add the <NOBR></NOBR> tags, let's make working in FrontPage easier by enabling FrontPage to wrap the code text.
Now you'll be able to view your HTML code without having to scroll left and right as much, which means you're ready to add the <NOBR></NOBR> tags.
Figure 10-10 Adding <NOBR> and </NOBR> to a page's source code ensures that a line break won't separate particular elements.
Figure 10-11 At this point the subpage.htm includes background, logo, and title bar images.
Inserting a TableIn this section you'll create the foundation table used to contain the body text of each subpage in the astronomy club's Web site. Take your time going through the upcoming stepsit's easier to configure your table correctly the first time around instead of trying to find an erroneous setting. Furthermore, although this section might seem to include a few too many steps, the steps throughout are fairly repetitious, so the process isn't overly complex. (In other words, don't let the number of steps get to you.) When you create your own tables, you'll probably have to experiment with a few settings before you get your table just rightwhich is exactly what we do, too. To create your table for this project, follow these steps:
Figure 10-12 By default, FrontPage creates tables with a 1-pixel border.
Figure 10-13 You use the Cell Properties dialog box to configure a table cell.
Figure 10-14 You can modify the internal layout of a table by adjusting cell properties. Notice in Figure 10-14 that the right set of table cells displays as a white rectangular area. You're now going to add small graphics to the white area's corner cells to create the illusion that the table has rounded corners:
Figure 10-15 Small graphics added to table cells create the appearance of rounded table corners.
Adding Navigation ButtonsNow that the table is created, you're ready to start filling the table's cells. First on the agenda is to add some navigation buttons to the first column in the table. FrontPage offers some nice special-effects buttons, which you'll use in this project:
Figure 10-16 FrontPage enables you to create hover buttons by configuring the Hover Button Properties dialog box.
Figure 10-17 Your table and navigation buttons display in Normal view but not yet in Preview view. As you can see in Figure 10-17, FrontPage 2002 encounters a little glitch when you insert hover buttons; basically, you can't preview your hover buttons in Preview view automatically (notice the broken link images in the Preview screen shown in Figure 10-17). In time, Microsoft might offer a patch to correct this, but for now you have two workaround choices:
If you choose to preview your Web pages in your browser throughout the remainder of this exercise, go ahead and skip to the next section and choose Preview In Browser on the File menu or click the Preview In Browser button on the Standard toolbar each time we suggest that you preview your Web page. If you prefer to tweak your HTML code a little to avoid opening your browser throughout the chapter, we present the steps here. The steps are manageable, and this is a prime example of how knowing a little HTML coding can help when you're working with HTML editors.
The code for each hover button appears between an <applet></applet> tag set, so you should see seven <applet></applet> tag sets in HTML. You can tell which button an applet applies to by looking at the value attribute for the parameter that defines the button's text. For example, following is the entire applet code for one button; notice that the fifth line indicates that this applet applies to the Home button:
<applet code="fphover.class" codebase="./" width="120" height="24"> <param name="color" value="#000080"> <param name="hovercolor" value="#0000FF"> <param name="textcolor" value="#FFFFFF"> <param name="text" value="Home"> <param name="effect" value="glow"> <param name="url" valuetype="ref" value="index.htm"> </applet><p> The problem in the current hover button code lies in the codebase="./" attribute in the first line of each <applet> tag. This attribute tells FrontPage to look in a subdirectory for the file fphover.class. In actuality, FrontPage stores the class file in the same folder as your Web page, so there's no need for browsers to look in a subdirectory for the class file. Although this explanation might sound a tad obtuse, the fix is simpleyou just need to delete codebase="./" in each <applet> tag (see Figure 10-18, where we've highlighted some of the instances of the codebase="./" attribute), as described next.
Figure 10-18 If you want to preview your hover buttons in FrontPage's Preview mode, you have to slightly tweak each button's code.
Adding Footer Information below the TableThe final components you'll add to the subpage template before you begin to create actual site pages are the bottom-of-the-page elements: a text-based navigation bar and copyright information. As we discuss earlier in the book, your Web pages should include text-based navigation links for users who turn off graphics or access the Web with nongraphical browsers. Furthermore, you should include copyright information to protect your creation. To add bottom-of-the-page information to the astronomy club's Web, follow these steps:
You're now ready to link the navigation bar's text and add a Mail To link to the E-mail the Webmaster text:
Figure 10-19 The Insert Hyperlink dialog box enables you to easily configure hyperlinks in FrontPage.
Figure 10-20 You can create hyperlinks that automatically open a preaddressed message form.
Figure 10-21 The subpage's footer information provides visitors with text links, Webmaster access, and copyright information.
You now have a subpage template ready for use.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||