Previous Page TOC Next Page



4


Introducing FrontPage


by William Robert Stanek

Whether you plan to set up a corporate intranet or create a site on the World Wide Web, FrontPage should be your application of choice. With this easy-to-use toolkit, anyone can create and manage a world-class Web site. This chapter introduces the applications that are a part of the FrontPage toolkit and provides a quick tour that should help you get started.

Quick Setup and Installation


Before installing FrontPage 97, you should quit all other applications running on your desktop. This ensures that there are no conflicts for files FrontPage must update on your system.

Installing FrontPage from CD-ROM or floppy disk is easy. The first step is to select Run from the Windows 95 or Windows NT Start menu. Then, as shown in Figure 4.1, enter the directory path to the FrontPage setup program on your CD or floppy drive, such as




E:\Setup.exe

In the example, E: is the location of the CD-ROM drive and Setup.exe is the name of the file you want to run. If your CD-ROM is on the D drive, you type the following to run the setup program:




D:\Setup.exe

Figure 4.1. Running the setup program.


NOTE

With the AutoPlay CD-ROM feature enabled, Windows 95 users need only to insert the FrontPage 97 CD-ROM to automatically start the setup program.


When you start the setup program, you see one of two startup screens. The setup program for Microsoft FrontPage with Bonus Pack CD displays the dialog box shown in Figure 4.2. Using this dialog box, you can install FrontPage 97 and bonus software that includes the Personal Web Server, Microsoft Image Composer, Internet Explorer 3.0, and WebPost—the Web Publishing Wizard.

Figure 4.2. FrontPage 97 with Bonus Pack startup screen.

To install FrontPage 97, click the button labeled FrontPage 97. You should now see the Welcome page for the FrontPage 97 setup program, as shown in Figure 4.3. If you are not installing FrontPage 97 with Bonus Pack CD, the Welcome page should display immediately as your startup screen.

Figure 4.3. Welcome to the FrontPage 97 installation program.

Most dialog boxes in FrontPage contain buttons you can use to obtain help, make selections, or exit the program. The Help button accesses the online help. The Cancel button exits the program. To move to the previous or next phase of the setup process, use the Back or Next buttons. When you complete the setup process, you can press the Finish button, and the setup program starts installing FrontPage on your system. You should click the Next button to continue.

You need about 11MB of free space to install FrontPage and the FrontPage server extensions. By default, the setup program installs FrontPage on the C drive in a folder called Microsoft FrontPage under the Program Files directory. To change the default, click the Browse button, shown in Figure 4.4. This opens a dialog box that lets you specify a new folder and path for the base installation. When you are satisfied with the path, click the Next button.

Figure 4.4. Installing FrontPage for the first time on your file system.

Anyone upgrading to FrontPage 97 does not see the setup page shown in Figure 4.4. Instead, you see the page shown in Figure 4.5, which notifies you that a current version of FrontPage exists on your system. You can upgrade the current version by installing FrontPage to the same directory or installing FrontPage 97 to a new directory.

Figure 4.5. Select a location for your upgrade.

Generally, you simply click the Next button to install the new version as an upgrade. However, if you have the room on your hard drive and you are concerned about changes to your system and existing FrontPage configuration files, you might want to install FrontPage 97 to a different directory. Click the Browse button to choose a new directory.

As shown in Figure 4.6, FrontPage allows you to select one of two types of installation: typical and custom. The typical installation installs everything most users need, including the client software, the Personal Web Server, and the FrontPage server extensions. The custom installation allows you to select the components you want to install. The client software includes the FrontPage Explorer and the FrontPage Editor. The Personal Web Server is the server you use to provide services for just about everything you do in FrontPage. The FrontPage server extensions are used with external Web servers, such as your Internet service provider's (ISP) UNIX-based Web server.

Figure 4.6. Selecting the type of installation.


NOTE

When you install the Personal Web Server, it is configured to be directly accessible at startup. Windows 95 users should see a new icon on the taskbar that allows you to control and access the server.



TIP

FrontPage makes extensive use of both the client and the server software. The only components you might not need are the server extensions. Unless you are sure you do not need to use an external Web server, you really should install all the components.


Because most users need all the components, you probably want to use the typical installation option. However, the typical installation assumes that you have enough space on your hard drive for the installation. If you want to check the space on your hard drive, you should select the custom installation option and possibly change the destination directory.

When you select custom installation and click the Next button, you see the setup page shown in Figure 4.7. Not only can you select the FrontPage components you want to install from this page, but you can also see the disk space you need and the amount of free space on your hard drive.

Figure 4.7. Custom installation lets you see all the components and disk space.

If you choose to install the Personal Web Server and you are installing FrontPage for the first time, the next setup page lets you specify a directory for the server executables and content (see Figure 4.8). . Keep in mind that this same directory stores all the files and documents you create or import into FrontPage. By default, the server directory is




C:\FrontPage Webs

The default directory for server executables is C:\FrontPage Webs\Server, and the default directory for content is C:\FrontPage Webs\Content.

Figure 4.8. Determining the directory for server content and executables.


TIP

Creating content for your Web site is easy with FrontPage. It is also easy to get caught up in the content-creation process and quickly eat up several megabytes of disk space. For this reason, I recommend using a drive with 2 to 5MB of free disk space if you plan to create a small to moderately sized Web site. This disk space requirement is in addition to the 11MB of free space you need for the base installation.


After you select a server directory or decide to accept the default, click the Next button (see Figure 4.9). You can now choose a name for the folder that holds the program icons.

Figure 4.9. Selecting a folder name for the FrontPage installation.


TIP

The name of the folder is not as important as remembering where the folder is located. This folder holds the icons used to start the FrontPage Editor, the FrontPage Explorer, the Personal Web Server, and other tools provided with the installation.

You need to run the FrontPage Editor, the FrontPage Explorer, and the Personal Web Server just about every time you want to create, manage, or edit web files. As a result, most users want to move the entire folder onto the desktop after the installation, which provides easy access to all the programs you need for publishing. If you use your computer exclusively or mostly for web publishing, you can also move the FrontPage Editor, the FrontPage Explorer, and the Personal Web Server to the Startup folder, which ensures the applications are started every time you turn on your computer.


If you are upgrading to a new version of FrontPage, the server setup page provides you with the additional options shown in Figure 4.10. Click the Upgrade radio button if you want to install the new version of the server software in the same directory as the old version, which effectively overwrites the old version. Click the Install radio button if you want to install the new version of the server software to a new directory.

Generally, you want to upgrade the current Web server software. The primary reason you would not want to use the upgrade option is if you made special configurations for the old server software. Installing the new software in a different location allows you to compare configuration options and ensure you have the same settings.

Figure 4.10. When upgrading the Personal Web Server, you have two new installation options.

If you install the server to a new location, the server usually runs on port 8080; the next page you see warns you about this (see Figure 4.11). Because port 8080 is not the default port used by browsers, you have to include the port in your hypertext references, such as http://www.yourcompany.com:8080/ or http://localhost:8080/home.htm.

Figure 4.11. When upgrading the Personal Web Server, the server usually runs on port 8080.

The next page pertains to the FrontPage server extensions. If you chose to install server extensions, the setup program searches your local file system for installed servers and displays the page shown in Figure 4.12. If you did not install the server extensions, you do not see this page.

Figure 4.12. Installing server extensions on servers you plan to use with FrontPage.

Generally, you want to install server extensions on any servers that you plan to use with FrontPage. Select servers as appropriate for your system and then click the Next button.


NOTE

Keep in mind the setup program looks only at servers on the local file system. You might need to install server extensions on remote servers.


You are now finished with most of the setup process and the setup program is ready to begin the installing FrontPage 97. When you click the Next button, you can review the current settings for the installation (see Figure 4.13). If you are not satisfied with any settings, click the Back button. Otherwise, click the Next button, and the setup program begins copying files to your hard drive.

Figure 4.13. Reviewing the installation settings before copying files.

Before the setup completes, you need to set up an account for the server administrator. FrontPage prompts you for this information automatically.

Another name for the server administrator is the Webmaster. The Webmaster is the person who controls access to the server and is also responsible for administering the server. As shown in Figure 4.14, you need to enter a user name and password for the server administrator. You also need to re-enter the password in the Password Confirmation field. Remember the user name and password you enter. You need it to verify your user name and password each time you restart the FrontPage Explorer.


TIP

To protect the security of your web, you should use a secure password. I recommend using a password that is at least six characters long and includes numbers and wild card characters, such as !, @, #, $, and ?.


Figure 4.14. Setting a user name and password for the server administrator.

When setup completes successfully, you have the option of starting the FrontPage Explorer (see Figure 4.15). The Explorer lets you create new webs. Usually, you want to start the FrontPage Explorer immediately. You can click the Finish button to complete the setup process.

Figure 4.15. A successful installation.

After the Explorer starts, FrontPage attempts to determine the IP address and host name of your system, and you see the dialog box shown in Figure 4.16. FrontPage uses a tool that checks for a Transmission Control Protocol/Internet Protocol (TCP/IP) connection to a network.

Figure 4.16. FrontPage checks your IP address and host name automatically.

If you are connected to a network and your system has an IP address and host name, FrontPage should return accurate results. If you are not connected to a network but use a TCP/IP dialer to access the Internet, as most Web publishers do, FrontPage might return inaccurate results. For example, on my system, FrontPage returned my login name with my ISP instead of a valid server name. Don't worry; the next section looks briefly at configuring your new Web server.

After checking the TCP/IP connection, the FrontPage Explorer displays the Getting Started With FrontPage dialog box. This dialog box is intended to help you get a quick start with the FrontPage Explorer. To avoid problems you might experience with the FrontPage Explorer at this stage, click the Cancel button to close the dialog box without executing any of the options. I discuss this dialog box in the next chapter.

Configuring Your New Web Server


If you have browsed the Web, you know how Hypertext Markup Language (HTML) documents are served to your browser. The browser is a client application. When you access a file with a client, the client contacts a server and requests a uniform resource locator (URL), such as http://www.mcp.com/. The Web server gets the referenced file and passes it to the client. The client displays the file in its viewing window.

FrontPage has two client applications: the FrontPage Explorer and the FrontPage Editor. You can configure both applications to use a server to retrieve files for them. The server included in FrontPage is the Personal Web Server. FrontPage also includes tools for configuring and testing the server: the Server Administrator, the Internet Services Administrator, and the FrontPage TCP_IP Test.

Although Part X, "Managing Your Web," covers server administration and testing in detail, this section is designed to get you started so you can use FrontPage. You can use one of three basic setups to do this. The first basic setup is for anyone using a computer physically connected to the corporate network or to the Internet and who does not want to test FrontPage locally before publishing documents. The second setup is for anyone who doesn't want to use the Personal Web Server. The final setup is for anyone using a computer not physically connected to a network. Jump forward to the section that details the setup you plan to use.

Configuring and Testing Your Networked System


To configure and test your server using the networking techniques discussed in this section, you must use a computer physically connected to the corporate network or to the Internet. This means your computer has a numeric IP address and a host name. If your system is connected or you plan to connect to the Internet, you must also have registered your IP address and host name with the InterNIC as discussed in Chapter 3, "Developing and Planning an Intranet."


NOTE

When you are done reading this section, you can skip the section, "Configuring and Testing Your Non-Networked System."


When you installed FrontPage, the TCP/IP test probably returned valid results. You can test the results using the TCP/IP Test tool included with FrontPage. To run this tool, execute the TcpTest.exe program located in the bin directory in the FrontPage installation or select About the FrontPage Explorer from the FrontPage Explorer's Help menu and then click the button labeled Network Test. After you start the test tool, you see a dialog box similar to the one shown in Figure 4.17.

Figure 4.17. The TCP/IP Test tool at startup.

To have FrontPage automatically test your TCP/IP connection, click the Start Test button. It takes a few minutes for the test tool to check your connection. When the test finishes, you see information similar to that shown in Figure 4.18. To see a detailed explanation that relates to your system, click the Explain Results button.

Figure 4.18. The TCP/IP Test tool returns results.


NOTE

When you click the Start Test button, the test tool might launch your Internet dialer, and you will see a dialog box prompting you for user name and password information. If this happens, you are not on a network or do not have a dedicated connection to the Internet. You should skip this section and read the next section in this chapter. Although you can enter the login name and password you use to connect to your Internet or commercial service provider's Web server and follow the steps you usually take to log in, you probably will not be able to use the results returned by the TCP/IP Test tool.


As you can see from the figure, FrontPage tests to see whether your system uses a 16-bit or 32-bit Winsock. The Winsock is used in network communications. Next, FrontPage checks to see if the local loopback host 127.0.0.1 is usable on your system. On most networked systems, 127.0.0.1 is the IP address listed in the /etc/hosts file for the local host. You use the local host when you want to test your web or publish documents for testing purposes.

The next three tests determine your system's host name, IP address, and local loopback address. The final test ensures that if your local host is different from the standard 127.0.0.1, you will know about it. You should write down this information if you do not already know it.

Now that you know key server information, you can start the Personal Web Server and the FrontPage Explorer. In the FrontPage Explorer, you create a new web by pressing Ctrl+N. This opens the New FrontPage Web dialog box, shown in Figure 4.19. You use this dialog box to select the type of web you want to create.

Figure 4.19. Selecting a new web template.


NOTE

Although the Personal Web Server should run automatically at startup, the tested software did not run as advertised. You'll know the server is not running when you see errors.

You might need to start the Personal Web Server by hand from the FrontPage folder or directory. The directory path is usually



For now, create a web based on the normal web by double-clicking the words Normal Web. The Explorer prompts you with the dialog box shown in Figure 4.20.

Figure 4.20. Creating a new web for testing purposes.

You can create a new web with or without the Web server. Because you use a networked PC, you usually want to create the web using the server, so select the option labeled Create Using Web Server. Now, you must enter the numeric IP address or host name information for the Web server on which you want to create the web, such as 143.15.8.9 or www.your_company.com. If you connect to a remote server that recognizes the Secure Socket Layer (SSL) protocol, you can select the Connect Using SSL option to ensure you have a secure connection to the remote server.


CAUTION

If you use your system's host name or IP address, anything you publish in FrontPage is available to anyone accessing your Web server. To start, you might want to publish files only locally, which means only someone logged in to the Web server will be able to access the files. To publish files locally, enter the IP address of the local host, such as 127.0.0.1 or use the key word localhost. Because FrontPage allows you to use multiple host names and IP addresses, you can enter a valid host name or IP address when you decide to publish materials for others to access.


After entering this information, FrontPage creates your web and loads the related pages into the FrontPage Explorer. If you have not identified yourself to FrontPage by entering your user name and password, the FrontPage Explorer displays a dialog box that asks you to enter that information. Whenever you create webs, you probably want to use the account you created for the system administrator.

In the FrontPage Explorer, double-click the Normal Page icon in the Link View window. If your web is working normally, the FrontPage Explorer should contact the Personal Web Server, which in turn starts the FrontPage Editor with the normal page loaded for editing. If the FrontPage Editor does not start, re-read this section and ensure you followed the instructions. Remember, both the FrontPage Explorer and the Personal Web Server should have been running on your system before you attempted to access the normal page in your new web.

Configuring and Testing Your System Without a Server


FrontPage lets you create webs on your local file system without using a server. A web is essentially a folder to hold your FrontPage files. Each time you create a web in a new location, FrontPage creates directories within the folder for storing FrontPage-specific data, such as parameter files.

Unlike an environment that uses a server to retrieve files, your webs are only available to someone using your computer. This means that when you create HTML documents, you need to transfer them to a server with access to the Internet or the company intranet. FrontPage includes great tools such as the Web Publishing Wizard that help you publish entire webs or single documents in a few easy steps.

Testing the installation without a server is easy. Your first step is to start the FrontPage Explorer and create a new web by pressing Ctrl+N. This opens the New FrontPage Web dialog box shown in Figure 4.21. You use this dialog box to select the type of web you want to create.

Figure 4.21. Selecting a new web template.

For now, create a web based on the normal web by double-clicking the words Normal Web. The Explorer prompts you with the dialog box shown in Figure 4.22.

Figure 4.22. Create your Web without using the Web server by entering the file path.

In the Web Server or File Location field, enter the directory path for the new web, such as D:\Webs\MyWeb\. If you specify a new folder, FrontPage will create the folder for you. If you enter the path to an existing folder, FrontPage will convert the folder to a FrontPage folder.

The next field you need to complete is the name of your web. After you enter the path and web information, FrontPage display a dialog box similar to the one shown in Figure 4.23. This dialog box relates to whether this is a new or existing directory. Here FrontPage tells you that the existing directory will be converted to a FrontPage web, which means the Explorer creates FrontPage-specific data and subdirectories. Click the Yes button to continue and FrontPage creates your web and loads the related pages into the FrontPage Explorer. This web is now the base of your new Web site.

Figure 4.23. Click the Yes button to convert the directory to a FrontPage web.

In the FrontPage Explorer, double-click the Normal Page icon shown in the Link View window. The FrontPage Explorer starts the FrontPage Editor with the normal page loaded for editing. If the FrontPage Editor does not start, re-read this section and ensure you followed the instructions.

Configuring and Testing Your Non-Networked System


If your system is not physically connected to a network and you do not have a dedicated connection to the Internet, FrontPage can create a pseudo-networked environment for you. This pseudo-networked environment works only on your local system.

When you installed FrontPage, the TCP/IP test probably returned results you do not want to use; FrontPage thinks you have a dedicated connection to the Internet and you do not. The first step in testing the server is to start the Personal Web Server and the FrontPage Explorer. In the FrontPage Explorer, select New Web from the File menu. This opens the New Web dialog box shown in Figure 4.24. You use this dialog box to create new webs.

Figure 4.24. Selecting a new web template.


NOTE

Although the Personal Web Server should run automatically at startup, the tested software did not run as advertised. You know the server is not running when you see errors.

You might need to start the Personal Web Server by hand from the FrontPage folder or directory. The directory path is usually



For now, create a web based on the normal web by double-clicking the words Normal Web. The Explorer prompts you with the dialog box shown in Figure 4.25. The server name entered in the Web Server field is probably the user name you used to log in to your Internet or commercial service provider's Web server. Delete the server name and enter the IP address 127.0.0.1. This IP address is for the local loopback, and it allows you to set up a pseudo-network on your system. All requests to the local loopback are served directly by the Personal Web Server.

Figure 4.25. Change the IP address so it points to the local host.


CAUTION

If you do not change the server name, it is possible that the only time you have access to your server is when you are connected to the Internet. Although it might seem that you are publishing files on the Internet or commercial service provider's Web server, you are actually using the local loopback. Because of this, it is better to use the local loopback directly. You can do this by specifying the IP address of 127.0.0.1. Keep in mind that when you use the local host, your files are only available on the local system, and you must transfer the files to a public server for the files to be available for others to access.


The next field you need to complete is the name of your web. After you enter the server and web information, FrontPage creates your web and loads the related pages into the FrontPage Explorer. If you have not identified yourself to FrontPage by entering your user name and password, the FrontPage Explorer displays a dialog box that asks you to enter your user name and password. Whenever you create webs, you probably want to use the account you created for the system administrator.

In the FrontPage Explorer, double-click the Normal Page icon shown in the Link View window. If your web is working normally, the FrontPage Explorer should contact the Personal Web Server, which in turn starts the FrontPage Editor with the normal page loaded for editing. If the FrontPage Editor does not start, re-read this section and ensure you followed the instructions. Remember, both the FrontPage Explorer and the Personal Web Server should have been running on your system before you attempted to access the normal page in your new web.

FrontPage Quick Tour


FrontPage publishing relies on three tools: the FrontPage Explorer, the FrontPage Editor, and the Personal Web Server. This section discusses these tools as they relate to two most basic FrontPage publishing concepts: pages and webs.

Creating and Manipulating Pages with the FrontPage Editor


Pages are HTML documents that can contain references to images, sound, and even video files. You view pages in the FrontPage Editor. Because the FrontPage Editor is a what-you-see-is-what-you-get (WYSIWYG) editor, your HTML documents look the same in the FrontPage Editor as they do in most Web browsers, which means all document formatting and inline images are displayed just as they should be. Most pages are a part of a specific Web. For detailed information on using pages, see Chapter 6, "Working with Pages and Files."

Figure 4.26 shows the FrontPage Editor with a page for editing. Just as you can open multiple documents in most word processors, you can open multiple documents in the FrontPage Editor. In fact, for all practical purposes, there is no limit on the number of documents you can have open at one time. You can find detailed information on the FrontPage Editor in Chapter 5, "The FrontPage Explorer and Editor Step by Step."

Figure 4.26. Viewing a page in the FrontPage Editor.

Creating and Manipulating Webs with the FrontPage Explorer


Webs are collections of pages and their related image, sound, and video files. You use the FrontPage Explorer to create new webs, access existing webs, and set the current web for editing. Setting the current web is important.

When you save a new page, it generally becomes part of the current web. When you open pages in the FrontPage Editor, you generally open them from the current web. At any given time, you can only have one open web, which is always considered to be the current web. For detailed information on using pages, see Chapter 7, "Working with Webs."

Figure 4.27 shows the FrontPage Explorer with a sample web. As you can see from the figure, the Explorer provides an overview of your web. You can use this information to quickly examine the layout of any web and access any pages for editing. You can find detailed information on the FrontPage Explorer in Chapter 5, "The FrontPage Explorer and Editor Step by Step."

Figure 4.27. Viewing a web in the FrontPage Explorer.

Personal Web Server


The Personal Web Server is the mechanism that retrieves pages from the current web and saves pages to the current web. Whenever you use FrontPage, you should start the Personal Web Server along with the FrontPage Explorer and the FrontPage Editor. Otherwise, when you use a FrontPage function that uses the Personal Web Server, you might see an error dialog box similar to the one shown in Figure 4.28. For detailed information on the Personal Web Server, see Part X, "Managing Your Web."


NOTE

Port 80 is the port usually used for the Hypertext Transfer Protocol (HTTP). You see the error depicted in Figure 4.28 if you incorrectly set up the server or changed the port setting to a port that cannot be used, or the server is not running. If the server is running and you get this error, check your server configuration.


Figure 4.28. This error indicates the server cannot be accessed.

FrontPage Features


Beyond pages and webs, you should learn about three additional FrontPage publishing concepts: templates, wizards, and WebBots. These are important concepts to understand, especially because you will find references to them throughout this book.

What Are Templates?


When you create a page or a web in FrontPage, you usually base the page or web on a template. FrontPage includes dozens of templates designed to make content creation a snap. You will find two types of templates in FrontPage: page templates and web templates.

A page template is an outline for a specific type of page, such as a home page or a customer survey page. A web template contains outlines for a specific set of pages, such as all the pages that relate to a business-oriented Web site. Usually, templates for webs and pages contain guidelines that make development easier. Just as there are very basic templates, such as the normal page template, there are also very advanced templates, such as the template for a customer support web. See Chapter 21, "Creating Web Pages with Templates," for more information on templates.

What Are Wizards?


Some pages and webs you create in FrontPage are very complex. To ensure that anyone can create these complex pages and webs without any problems, FrontPage includes powerful tools called wizards. Wizards help you automatically generate content. All you have to do is start the wizard and follow the prompts. As with templates, FrontPage includes two types of wizards: page wizards and web wizards.

You can use page wizards to create documents with forms and frames. Forms allow you to collect information from the reader. Frames allow you to display documents with multiple windows in a single viewing area. A page wizard also helps you create a home page.

You can use web wizards to create the entire webs with dozens of pages. FrontPage includes two powerful web wizards: the Corporate Presence Wizard and the Discussion Web Wizard. Using the Corporate Presence Wizard, you can create a site that is designed to help you establish a presence on the Web. Using the Discussion Web Wizard, you can create a web with multiple discussion groups that company employees and customers alike can use to discuss topics of interest. To learn more about wizards, see Chapter 22, "Instant Web Sites with Web Wizards."

What Are WebBots?


In FrontPage, you will find more than a dozen WebBots. Another name for a WebBot is simply a bot. You can think of each bot as a program that runs when needed. Bots automate complex administration processes and eliminate the need to write your own scripts or add complicated HTML commands. For detailed information on using WebBots, see Chapter 23, "Automation with FrontPage's WebBots."

Before FrontPage introduced WebBots, administration of world-class Web sites was the realm of those who earned the name Webmaster by being the best at what they did. Great Webmasters know how to create scripts that process the input of forms. They can also insert headers, footers, and images into documents at any time using programs they created and change colors used in backgrounds, links, and text using UNIX tools such as Sed and Auk—and much more. With a WebBot, you can collect the results from forms, automatically add navigation bars, create pages with full text searches, allow registered users to access key areas of your web, and do just about anything else that once only a skilled Webmaster could do.

WebBots are great for most publishing tasks. However, they cannot do advanced follow-on processing of input from forms, and they cannot help you generate content based on the type of the user's browser. In a some instances, you might have to use a custom script. For more information on using scripts, see Chapter 34, "Writing CGI Scripts."

Summary


After you read this chapter, FrontPage should be installed successfully on your system. This chapter teaches you about key FrontPage publishing tools and concepts. You use the FrontPage Explorer, the FrontPage Editor, and the Personal Web Server whenever you create and edit files in FrontPage.

Previous Page Page Top TOC Next Page