If you've read through the book to this point, you've learned just about everything you need to know to use Internet Explorer to surf the Web. You've learned all the basics, and you should be merrily wandering the Web with abandon. But one thing that
hasn't been covered in detail is how you make that transition from Web surfer to webmaster. Although you learned about many of the details of the languages of the Web in the last section, you really haven't been shown how to put it all together and
"hang your shingle" on the Web. You might actually have been a little put off by the cryptic nature of HTTP, Java, and so on, and wondered if there really was some other way to get on the Web without becoming a programmer. Microsoft FrontPage is
for you!
Of all the HTML editors that are available on the Internet, Microsoft FrontPage is simply the best. Starting with the release of its original 1.0 version, FrontPage has won industry accolades as one of the easiest and most complete Web publishing tools
available. And it is Web publishing rather than simply HTML editing that sets FrontPage apart from so many other tools for the Web. Although many tools for the Web enable you to edit HTML files and then rely on another means to post
these files to the Web, FrontPage is a unique client/server application that not only facilitates WYSIWYG HTML editing using the FrontPage Editor, but also manages updating the data on the Web server with its companion FrontPage Explorer.
You will not need to learn HTML to use FrontPage because the HTML engine in FrontPage supports the latest extensions to HTML and includes wizards to assist you in using some of the more difficult formats to implement. Whether you want to format your
pages using TABLE or add support for frames on your Web site, FrontPage will make these easier to implement than you might have thought possible. With FrontPage, you will quickly be creating exciting Web pages and even entire sites that are as good as any
of those you've seen on the Web. And with the Personal Web Server that is part of FrontPage, you can very easily set up an intranet or even an Internet site with a minimum of trouble. I know that you are really looking forward to learning about FrontPage,
so dig in and see what you can do with this exciting tool!
NOTE
If you really want to learn all there is to know about FrontPage, look for FrontPage Unleashed (Sams.net Publishing, ISBN 1-57521-140-8) at your bookstore!
You might also want to look for the latest information on the Microsoft FrontPage home page at http://www.microsoft.com/frontpage/, shown in Figure 26.1.
Figure 26.1. Microsoft FrontPage on the Web.
This chapter serves as a high-level look at FrontPage, while the following chapters give a detailed hands-on look. Some of the information that you will learn about in this chapter includes
As already mentioned, FrontPage is a Web Publishing tool that facilitates the creation, development, and maintenance of Web content. Whether you're working on a small personal home page or building an extensive corporate site, FrontPage will make all
your tasks easier. Many Internet Service Providers (ISPs) now support Web publishing using FrontPage, so you might already be thinking about using it to manage your data. Because FrontPage includes extensions that enable it to connect directly to the Web
server software, managing data is both easy and secure. The extensions operate as an integrated piece of the server and use the built-in security of the server itself so that you can safely manage the data on the server without compromising security.
Before you install FrontPage, you might want to look over the requirements to make sure that you have the necessary configuration to use the product. The current configuration that Microsoft recommends for running FrontPage is as follows:
TIP
Although not listed specifically on the Web or in the preceding list, the server components require a 32-bit TCP/IP stack; 16-bit stacks like many of the ones available from third-party Windows vendors will not enable the FrontPage server to run.
If you are not going to be using the Personal Web Server, the entire installation will take only about 8MB of disk space. This includes the FrontPage Editor as well as all the sample template files. If you want to use the full potential of FrontPage
with your server software, you will need the server extensions for the Web server that you need to access. Server extensions are available for most NT and UNIX servers, including the most popular servers from Netscape, O'Reilly, and of course, Microsoft.
Before you get into many more details about the components that make up FrontPage, the next section offers a look at a typical installation of the entire product. Subsequent sections continue with the details of each component of FrontPage.
FrontPage 1.1 is delivered on five 1.44 diskettes, and like other Microsoft products, is easily installed using the SETUP.EXE program on the first disk.
When you run Setup for the first time, you will be presented with a dialog box similar to the one in Figure 26.2.
NOTE
Because Microsoft has standardized all product installations using the InstallShield installation tool, the product is easier to install than the 1.0 version, which was still using the older Windows setup program. As shown in Figures 26.3 and 26.4, the installation follows a familiar Windows 95 wizard format that makes it easy to install the product.
Figure 26.3. The Destination Path dialog box showing the default installation directory.
The default installation directory for FrontPage is in the C:\Program Files\Microsoft FrontPage directory unless you are installing the product on Windows NT. When installed on Windows NT, the installation defaults to C:\Microsoft FrontPage. Unless you
have a specific reason to install FrontPage in another directory, the default location should be fine. As shown in Figure 26.4, if you choose the Typical installation, the client utilities, the Personal Web Server, and server extensions will be installed
to your computer. If you don't want all the components, you should choose the Custom option to select only those components that you really need to install, as shown in Figure 26.5.
Figure 26.4. The Setup Type dialog box details the components that comprise a Typical installation.
If you choose to install the Personal Web Server, the default installation directory for the Web server is C:\FrontPage Webs. Any webs that you build will normally reside under this directory as well. Figure 26.6 shows the typical directory choice, but
notice that you can easily choose another location using the Browse button.
Figure 26.6. You can easily change the default installation directory using the Browse button.
You will be prompted for the name of the Program Group or Start Menu Folder to create, and then be given a summary screen detailing the current choices that you have made. If these choices aren't correct, you can easily go back to the previous screens
to change any of them. Figure 26.7 shows the summary results of the Typical choices before any files are copied to your machine.
If you install the Personal Web Server, the installation program will run the server administration program and you will be prompted with a dialog box requesting the initial administrator logon and password for access to the server, as shown in Figure
26.8. When this is completed, you are given the option of running the FrontPage Explorer to begin the creation of your ultimate Web site.
When you are ready to run FrontPage, you just need to open the Microsoft FrontPage group or, if you are in Windows 95, use the Start Menu button to navigate to the Microsoft FrontPage folder. Figure 26.9 shows the contents of the Microsoft FrontPage
group or folder.
Figure 26.9. The Microsoft FrontPage folder showing the shortcuts for all of the components.
Microsoft refers to FrontPage as a workplace—specifically, the FrontPage Workplace. The tools that you will use in this workplace are the Editor, the Explorer, and the To Do List. The interfaces that you work with and the interfaces that exist
between these tools comprise the workplace. The product is an integrated whole with tight integration between the separate components.
The client portion of FrontPage includes the Editor, the Explorer, and the wizards and WebBots. The FrontPage Editor can be used without a server, but the Explorer requires a running Web server with server extensions installed to operate. The wizards
enable you to step through the creation of an entire site with a minimum of difficulty. Though the WebBots are primarily targeted toward the server, a couple of the bots can help you edit your Web documents. You can use the HTML Markup Bot and the
Annotation Bot to create either HTML code not specifically supported by FrontPage or comments in your code to help you comment your Web pages. You'll see how useful these two bots can be in the "Wizards and WebBots" section later in this
chapter.
NOTE
You will find that WebBots are referred to simply as bots in the product documentation and the help file. I also use the short name when referring to a single instance of this tool, and I use WebBots when referring to the tools in general.
Remember that the FrontPage Editor, wizards, and WebBots comprise the portion of the product that can be used without a server. The Explorer is the client tool that enables you to manage the Web dynamically. The remainder of this introductory chapter
discusses each of the components of FrontPage, but each is also covered in greater detail in the remaining chapters of this section.
The FrontPage Editor is the tool you'll use to create your Web documents. As a WYSIWYG editor, it is not unlike Microsoft Word or other word processors that you might be familiar with. This tool enables you to create impressive documents using the
latest HTML constructs such as tables and frames without learning a single line of HTML. Note that I don't suggest you never learn HTML, just that there is no longer the need to learn HTML when you have FrontPage to write it for you! The only time
that you might need to know HTML is when you use the HTML markup bot to insert specialized HTML code into your document. Other than cases like that, FrontPage makes it easy for you to concentrate on the information rather than the mechanics of how to
present that information.
TIP
Because understanding the underlying HTML source will only increase your knowledge, make sure you read Section V, "Web Publishing for Internet Explorer 3.0," especially Chapter 21, "Composing and Editing HTML Pages," and Chapter 22, "HTML 3.0 and Internet Explorer Extensions." You won't be sorry that you took the time!
As you can see in Figure 27.10, the FrontPage Editor looks a lot like Word for Windows and gives you a rich set of tools to edit your documents. The example shown is a blank page ready to begin editing. When you are managing a web with FrontPage, you
can set default settings for the entire web for such details as background image or color as well as other important features.
NOTE
When the term web is used by FrontPage, as in "opening a web," it is referring to a unique set of documents comprising a single related whole. FrontPage has the capability to manage these interconnected documents individually or as a single unit. Your Web site might have only a single web, or it can be comprised of many webs with discrete characteristics. This makes it easy for a group of people to collaborate on a Web site, with each one having responsibility for only a section of the whole.
Because you probably already know how to use a word processor, I won't bore you with those details. To start, you just start typing as you would in another word processor. Or to find out how FrontPage can save you a whole lot of time, you can begin by
using one of the many supplied page templates. If you choose File | New from the menu, a dialog box with the supplied templates to aid in creation of the page, as shown in Figure 26.11, appears.
When you select one of these templates, FrontPage loads the file so that you can begin creating your documents. One of the best features of FrontPage is that if you already have a set of standards for your Web publishing, you can easily save files as
templates for your own use or those of your associates. Because templates are really nothing more than simple HTML files, you can take your existing HTML files and open them in FrontPage. Use the File | Save As dialog box to save your files as a new
template. Then, when you need to create a file based on this template, you can easily do so. A look at one of the delivered templates will show you how this magic is accomplished.
One template that you are likely to use often is the What's New template. Every Web site has a What's New page, so why shouldn't yours? The What's New page is the first page that I visit on sites that I frequently visit. This is the place where the
webmaster keeps all the details about the changes on the Web site. It's a nice feature to add to your site as long as you decide to begin with that you will keep it up to date. There's nothing more indicative of a stale site than a What's New page
with the last update made six months earlier! Figure 26.12 shows the What's New template loaded for first-time creation.
TIP
If you need to easily track changes to a server's What's New page, use URL Minder, a free service that will send you an e-mail message when a site changes. URL Minder is at
http://www.netmind.com/cgi-bin/uncgi/url-mind
Figure 26.12. A What's New? page is easily created using this simple template.
You'll note that the cursor in Figure 26.12 resembles a robot. This image indicates that the section of the file that you are viewing is created using one of FrontPage's bots. If you look at one of these pages in the Editor, the section created by the
bot—in this case, the Annotation bot—displays in purple text to make it stand out from the rest of the text. If you are creating templates for others to use to maintain a standard look and feel to your pages, the Annotation bot is the tool
you'll
want to use. But, the secret to bots becomes apparent when you view the HTML source for this same file, shown in Figure 26.13.
When you insert a bot in your Web page, FrontPage uses the standard HTML construct for comments to hide the bot code in the text of the file. These comments will not be seen by the Internet Explorer or other browser, but are used by FrontPage as
placeholders for the special instructions that bots add to the file. This bot is revisited in the next section of this chapter, and in much more detail later in the book. Just note that FrontPage uses existing HTML code to enable it to create the apparent
magic that it is able to do. Look again at the HTML code snippet from Figure 26.13 as listed in Listing 26.1.
Listing 26.1. HTML code from FrontPage What's New template.
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>Untitled What's New</title>
<meta name="GENERATOR" content="Microsoft FrontPage 1.1">
</head>
<body bgcolor="#FFFFFF">
<p><!--VERMEER
BOT=PurpleText
PREVIEW="INSTRUCTIONS: Once you create this page, keep it up to date by *
making an entry here every time you make a significant change to *
your web site. Clear out old entries every month so it appears *
fresh and up-to-date for frequent visitors."
--></p>
<h1>What's New?</h1>
As you can see, the code is straight HTML. You have the standard elements you'd expect to see in well-formed HTML such as the <html>, <head>, and <body> elements. The only peculiar thing might be the word VERMEER after the beginning
comment tag. Vermeer is the name of the company that originally created FrontPage. The VERMEER tag tells FrontPage to look in the comment for bots or other special formatting instructions to perform on the text or the file as a whole. This is one of the
great beauties of FrontPage; it advances the art of Web publishing while conforming to the standards that helped make the Web so ubiquitous.
In this brief tour of the FrontPage Editor, you have seen a couple of features that you'll use constantly. But as you'll see, as good as the Editor is, the other pieces of the FrontPage really make it shine as the one Web tool you won't want to be
without.
You've already seen one of the bots delivered with the product. The Annotation bot is used to add comments to a Web document that will allow visible comments while another person is using the template. I believe that you'll find that the wizards and
bots make FrontPage extremely easy to use. But before I show you some of these cool tools, I first need to tell you what they are and why you should be interested.
The HTML wizards in Microsoft FrontPage are similar to the one used to install the product, and range from the simple Personal Home Page Wizard shown in Figure 26.14 to a detailed one for creating a corporate Web site. Figure 26.15 gives a quick look
at
some of the wizards that are available when using the Explorer, including the Corporate Presence Wizard, which will help you set up an entire corporate Web site from scratch.
You will find that the wizards are very useful for these kind of repetitive functions. When you step through the creation of the corporate web, you'll see exactly how useful these wizards can be!
The WebBots that are part of FrontPage are equally useful. The Annotation bot is a simple one to assist in active commenting of your source documents to help in collaborative web efforts. Bots really become useful when you use the server-side bots such
as the Discussion Group bot or the Table of Contents bot. Respectively, these tools enable you to maintain a threaded online bulletin board or forum or create and constantly maintain a complete table of contents for your entire Web.
Bots can be server-side or client-side. If a bot is a client-side bot, it generates its intended function when the file is saved to the web. If the bot is a server-side bot, it acts in a manner similar to a CGI process. It dynamically serves its
information when the file is accessed by a browser. An example of a client-side bot is the HTML Markup bot, which saves the embedded HTML code when it is saved to the web. A good example of a server-side bot is the Search bot, which dynamically searches
your web for text entered by the user when the page is accessed. The Search bot uses the detailed index of the web that the server extensions maintain to enable accurate searches of your web content. Although I have only touched on wizards and WebBots
here, the following chapters will help you see their real usefulness.
The Explorer is a tool like no other. Although it is a client tool, it is an integral part of the server side of FrontPage. It is the tool that manages the transactions between the Editor and the server. It is a powerful tool in its own right, though,
and when you use it to manage your web, it can be a powerful tool indeed. With Explorer you have the ability to
You can see from this short list that Explorer is a powerful tool. If you only added the ability to move or rename resources with the automatic updates that Explorer offers, you would be seeing a "must have" tool. But the additional
management
tools that Explorer brings to the table are impressive. A team using FrontPage to manage a web's content would be hard pressed to find a better tool.
When you load Explorer for the first time, you will see something like the view illustrated in Figure 26.16. As you can see from this view, the interface is spartan, with a minimum of buttons on the toolbar. But don't let this interface fool you. After
you begin to manage your server, these panes will fill with meaningful information that will assist you in managing your entire web.
Figure 26.16. FrontPage Explorer is the tool you will use to manage your web's content.
Explorer's interface enables you to view your web in a number of fashions. The default view is as shown in Figure 26.16, with the Outline view in the left pane and the Link view in the right pane. The Outline view shows you a hierarchical view of the
structure of your web. The Link view shows you all the many interconnections in your web. As you build your web content, you will get a graphic picture of one reason that you might need a tool like FrontPage; the interconnected information can be daunting
to track without such a tool. When you have several levels of information each with appropriate links to other areas of content, even a moderate Web site becomes a virtual spider's web of traps for the webmaster.
Suppose you decide to restructure your site or remove a page of information that is no longer accurate? If you are managing your Web site manually, how do you keep up with these kinds of changes? Are you sure that you know every link that you've placed
on a given page that might now point to missing information? FrontPage Explorer knows! Even if you move an entire subtree of information to another location in the directory structure, Explorer will fix any links in the documents when you move them and
even fix any links that would otherwise be broken by this change. If you have been managing a corporate Web site manually, you know the kinds of calls you get when you inadvertently break a link by necessary maintenance of information.
Just deleting a single file or moving it to another location can have a cascading effect on the entire web. Another way for you to view your information is the Summary view. This view, shown in Figure 26.17, presents a list of every file in your web.
Each of these views is more than just static snapshots of information. Each of the documents in Explorer is viewed as an object that can easily be manipulated. Whether you need to edit the HTML source document for the information or any other element, if
you double-click on any of the elements, the Explorer will open the file or image in the appropriate tool for the media. If you need to edit your main home page, simply double-click on the image of the file in the Link view or the filename in the Summary
view, make any required edits, and save the file back into your web knowing that Explorer will adjust the Web to reflect any changes you've made. You could also use Edit | Open or Edit | Open With from the menus to open the file in its default application
or a different application, as illustrated in Figure 26.18.
A couple of other tools that you will use frequently are the Verify Links and Recalculate Links commands from the Tools menu. The Verify Links tool will check all the links in your web and find any problems that exist. You should use this tool
regularly, especially if you make extensive edits to your content. Because the tool actually checks to see if can access any link exactly as listed in your HTML file, it can help you locate simple problems like using a relative reference where you should
have used an absolute reference. It will also tell you if a link external to your server is broken. How many times have you visited a site on the Web and been frustrated by a link that ended with the dreaded 404 Object not Found? You've hit a broken link.
The file could unexpectedly disappear, or a section of the server simply be down for maintenance.
If you have external links on your pages, Explorer can check to see if these links are live so that you can fix the link(s). Did I say links? Explorer can easily fix similar broken links on all pages in your Web. If you have repeated an external
link in many places in your web and you find out later it's broken, Explorer can correct every link after you determine the correct URL information. When Explorer finds broken links, it will show you a summary screen (see Figure 26.19) where you see a
broken link listed. When you choose to edit the broken link, the Edit Link dialog box will list every file that this link is in and enable you to correct the link in a single file, all files, or selected files, as shown in Figure 26.20.
Figure 26.19. The Verify Links dialog box will show you any broken internal or external links.
You'd use the Recalculate Links tool any time you need Explorer to update its link information. If the content of your web changes, the Recalculate Link tool can update information like the indices used by the Search bot or other bots that change
content by their action.
TIP
Recalculating links on a large Web can be a time-consuming process. It will not affect those browsing your web, but until you either stop the process or it completes normally, you will be unable to perform any other action in the session. You might want to schedule a recalculation after hours, especially if you have a search bot that needs to index the content of your web.
One other feature that you should be aware of is that FrontPage keeps detailed information on each file that you can access using the Edit | Properties dialog box or by right-clicking on the file icon in the Link view. (See Figures 26.21 and 26.22.)
Figure 26.21. You can access detailed information about a file using the pop-up menu.
This brief tour of FrontPage Explorer has pointed out some of the features that make it an indispensable tool that you'll use regularly as you manage your web. Another essential management tool is the To Do List. This tool can assist you in quantifying
or tracking the status of your Web site.
When you build a web, there are many interrelated tasks that you need to be able to quantify and track. These tasks can be as simple as Write What's New Page or Create banner GIF image, or as complicated as Write all HTML docs for Customer Support
Section of Web. If you are part of a team of webmasters and content providers, there needs to be a way to track who "owns" the task and when to expect the task to be completed. This tracking is especially important when a task has dependencies.
The To Do List shows these dependencies and because the task information is kept with the files, this information is available to any of the approved authors so that the status at any given time is available to all. New tasks can be created, tasks
completed, and all within the allotted time period when the whole team uses the To Do List. Figure 26.23 shows a view of the To Do List with two tasks assigned.
Figure 26.23. The details in the To Do List dialog box shows the current status of assigned tasks.
As you can see, the To Do List will enable you to track each file on the site as it is being created. This tool alone is a great addition to a collaborative Web publishing effort .
The next section presents the additional components of FrontPage that comprise the server portion of the package. It is these tools that make FrontPage a complete solution for an intranet or public Web site on the Internet, especially when multiple
authors or locations are involved in the creation of content.
FrontPage is more than a fine web editor and an excellent web management tool. FrontPage also includes a Personal Web Server—a complete HTTP server with some very important features that enable the server to impersonate the servers that it is able
to manage. The server is a native WIN32 application capable of running under Windows NT or Windows 95. If you install the server when you install the other pieces, you will have a complete Web publishing system and need not buy anything else to begin
publishing.
The FrontPage server can operate much like the NCSA, CERN, Apache, or Netscape UNIX servers, using similar configuration files, image map methods, and access validation schemes. Thus, when you have the server extensions installed for one of the UNIX
servers, you can easily duplicate the exact structure of the data on the UNIX machine. This removes another headache that webmasters face in maintaining a Web server. Because you can get hits at any time of the day or night, it's hard to pick a good time
for needed housecleaning or other maintenance work on a server that is on the Internet. But when you have the Personal Web Server and the extensions installed, you can easily test a mirror site for any problems before you post the new data to the
master site. With FrontPage, you can reasonably maintain a complete staging system so that you can build your content offline and then transfer the information to the real server, which might not even be an NT server at all.
NOTE
At the time of this writing, Microsoft has announced intentions to replace the existing Personal Web Server in FrontPage with the new Peer Web Services, which the company intends to make available on Windows 95 and Windows NT 4.0. Some configuration may be different when this is done.
The three pieces that comprise the server component of FrontPage are the Web server, the extensions, and the Server Administrator. These three tools are your interface to your working server and if needed, to your staging server as well. And because
Microsoft has pledged continued support for these servers, you will be able to use FrontPage with any server software that is currently running, and probably with others as time goes by. A look at these three pieces will help you to better understand how
they fit together. The first piece of the puzzle is the Web server proper.
The Personal Web Server that ships with FrontPage is based on the NCSA HTTPD server. Ported as a true WIN32 application, it is capable of being run on Windows NT or Windows 95. It is lightweight and highly configurable. It can run CGI programs as well
as server-side bots, and it is tightly integrated with the other components of FrontPage. Although it is an NCSA port, it can reasonably duplicate the configuration of the other supported servers. A good indication of this is in image map support for
either NCSA or CERN style servers. Look at Figure 26.24.
See the designation of CERN Image Map Dispatcher and NCSA Imagemap Dispatcher in Figure 26.24? These are executables that closely mimic the required method of servicing image maps on those platforms. If you are configured to publish to a CERN server,
any image maps you might need have to be configured to run on that server. If you access the properties dialog box for the CERN htimage.exe file, you will notice that the URL to access the executable is as it would be if you were publishing on a CERN
server, as shown in Figure 26.25. The same is true for NCSA-type image maps. This way you can easily duplicate the format for these servers before you test and then post to your UNIX server. The next section presents a look at the server
extensions—exactly what they are and how they interface with the server.
The server extensions are the "glue" that holds the whole thing together. Platform-specific versions of the three extension executables reside in the CGI-BIN directory of the supported server on UNIX. When the Explorer needs to publish
information to the server, it runs a dedicated CGI program on the server to facilitate access. The extensions utilize the server's own authentication mechanism, so there usually is no reason to worry about a security risk. These extensions add needed
functionality to enable the Explorer to communicate and manage the different servers that FrontPage supports. The functions that they add to FrontPage are capabilities to store documents, track the To Do List, and maintain the relation information for all
the documents. In addition, the extensions add a common API for setting permissions, configuration information, and image map processing. This API is especially important as it enables the FrontPage client to support a wide range of servers without
sacrificing functionality. Finally, if WebBots are used on the server side, the extensions can be used as replacements for common CGI processes such as implementing text searches.
On UNIX servers, CGI processes are usually implemented as executable scripts or binaries. On some NT servers, these functions may instead be implemented using a Dynamic Link Library (DLL). The major portion of the server extension code is the same on
each of the supported servers. The only differences are those required by the platform and server software. This base similarity in the structure means that the extensions operate in the same manner on Web servers based on UNIX, Windows NT, or even
Windows
95. If you are a Web content provider or Web design house, this feature enables you to prepare client content and directly deliver to any server supported by the extensions. You can, of course, create content for any server, even those without extension
support, as long as you have some access to the server via FTP or NFS or other directory-mounting services. The installation method for the server extensions is covered in the next section.
The Server Administrator is the tool you use to install, upgrade, or uninstall server extensions, check the current configuration, enable or disable authoring, and add or change administrative users. You encounter the Server Administrator for the first
time during the initial installation of FrontPage. Most of its functions are also accessible in the Explorer, so you might not need to use it on a regular basis. Installing or upgrading server extensions is the most common use of the Server Administrator,
and as shown in Figure 26.26, the details of the current installation are shown in the application dialog box.
Notice that this dialog box records the most important details of the server extensions currently installed:
The dialog box includes the port number for the supported server as well as detailed version information for the extensions, important for tracking updates when they become available. Use the Install button to install and configure a specific
extension,
and choose your server from the pull-down list as shown in Figure 26.27.
Figure 26.27. The Configure Server Type dialog box is used to install new server extensions.
If you need to disable authoring, as during required maintenance, click the Authoring button and either enable or disable authoring. A feature that you might really find important is the Security button, which enables you to add administrator names and
passwords for access to the webs you are serving. As seen in Figure 26.28, this dialog box enables you to add authorized administrators for a given web. If you need to further restrict access, you can use the Advanced button to restrict access to a
certain
IP address or addresses, as shown in Figure 26.29.
Figure 26.28. You can add new administrative user information for a given web.
Figure 26.29. You can restrict access to a single IP address or addresses.
The Server Administrator gives you the necessary control of your configuration to assure smooth operation of the FrontPage authoring environment.
This chapter has covered the details of Microsoft FrontPage and each major component in the package. In the next chapter, you will begin to build a web site using one of these components: the FrontPage Editor. The remaining chapters in this section
detail each of the components that make FrontPage the excellent package it is.
