1. Microsoft FrontPage 2003 Illustrated Complete Finalizing a Web Site

2. 2Finalizing a Web SiteUnit P  Test a Web site’s function  Report broken hyperlinks  Customize a Site Summary report  Report file status Objectives

3. 3Finalizing a Web SiteUnit P Objectives  Set publishing options  Publish a Web site to another server  Learn about your server configuration  Troubleshoot FrontPage problems

4. 4Finalizing a Web SiteUnit P Finalizing a Web Site  Once you’ve finished creating content in a Web site, you need to make sure that the Web site works as expected  FrontPage includes features that automate this task

5. 5Finalizing a Web SiteUnit P Finalizing a Web Site (cont.)  The Site Summary report provides information about every aspect of a Web site: –Broken hyperlinks –Unlinked files –Slow pages –Component errors in pages  After you resolve any problems, you can publish it

6. 6Finalizing a Web SiteUnit P Testing a Web Site’s Function  You should test a Web site using different: –Browsers –Browser version –Monitors –Monitor resolutions –Operating systems

7. 7Finalizing a Web SiteUnit P Testing a Web Site’s Function (cont.)  You should also address the following tasks:

8. 8Finalizing a Web SiteUnit P Testing a Web Site’s Function (cont.)  You can use Tasks view to keep a running list of problems to fix  Once your testing is complete, you can publish it to the WPP, and repeat testing  This process ensures the site functions and looks as expected  As you add new pages to a site and update pages, you should assess the Web site’s function and content

9. 9Finalizing a Web SiteUnit P Reporting Broken Hyperlinks  You can use Reports view to learn about your Web site’s files and usage, and to help you locate potential errors  A Site Summary report includes reports about a Web site’s files, hyperlinks, components, and tasks

10. 10Finalizing a Web SiteUnit P Reporting Broken Hyperlinks (cont.)  Usage reports will help you identify your site’s visitors, their browsers and operating systems, and which pages they viewed  Different usage reports might identify the domain names of the visitors of your site, such as aol.com

11. 11Finalizing a Web SiteUnit P Reporting Broken Hyperlinks (cont.)  Site Summary report

12. 12Finalizing a Web SiteUnit P Customizing a Site Summary Report  The Recently Added Files report uses a day or time value to list pages that were recently added to the Web site  The Older Files report finds files that were added to the Web site within a specific number of days  The Slow Pages report finds files that take a preset number of seconds to download  You can change the default value for these report settings using the Reports View tab in the Options dialog box

13. 13Finalizing a Web SiteUnit P Customizing a Site Summary Report (cont.)  Reports View tab in the Options dialog box

14. 14Finalizing a Web SiteUnit P Reporting File Status  You can use other reports in Reports view to list specific details about the Web site, such as: –Pages that aren’t linked to other pages in the site –Pages containing external hyperlinks –Pages containing components with errors

15. 15Finalizing a Web SiteUnit P Reporting File Status (cont.)  Unlinked Files report

16. 16Finalizing a Web SiteUnit P Setting Publishing Options  The default status for all Web pages is to publish them  You can set a page’s properties to “Don’t Publish”  You use the Publishing tab in the Remote Web Site Properties dialog box to select publish options

17. 17Finalizing a Web SiteUnit P Setting Publishing Options (cont.)  Publishing tab

18. 18Finalizing a Web SiteUnit P Publishing a Web Site to Another Server  You publish a Web site from IIS using the same steps that you use to publish a disk- based Web site to IIS  You are publishing to a server’s URL, and not to the server on your computer or local network  After publishing a site, you can open it from the WPP’s server by entering its URL in the site name text box in the Open Site dialog box

19. 19Finalizing a Web SiteUnit P Publishing a Web Site to Another Server (cont.)  You will be prompted for your username and password  If you have the proper permission for opening the site, it opens in FrontPage just like any other server- based Web site

20. 20Finalizing a Web SiteUnit P Publishing a Web Site to Another Server (cont.)  Remote Web Site view

21. 21Finalizing a Web SiteUnit P Learning about Your Server Configuration  It’s important to know how to determine which versions of software you have  FrontPage can run on different computers, operating systems, and servers with different versions of the FrontPage Server Extensions and SharePoint Services

22. 22Finalizing a Web SiteUnit P Learning about Your Server Configuration (cont.)  FrontPage identifies the following in the Site Settings dialog box: –The server name and version –Server Extensions or SharePoint Services version –FrontPage program version  You can learn about the computer you’re working on by using the Help menu

23. 23Finalizing a Web SiteUnit P Learning about Your Server Configuration (cont.)  System Information window

24. 24Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems  Keep in mind that you are really working simultaneously in several software programs: –FrontPage –The FrontPage Server Extensions or SharePoint Services –An operating system –A server  It’s also possible that the browser you’re using is causing the problem

25. 25Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems (cont.)  Problem: An older copy of a page is displayed in FrontPage or the browser  Possible Solution: Click the browser’s Refresh or Reload button  Possible Solution: Clear temporary files in a Web site  Possible Solution: Clear the browser’s cache file

26. 26Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems (cont.)  Problem: The FrontPage Server Extensions or SharePoint Service aren’t installed, aren’t working properly, or the server doesn’t support these programs  Possible Solution: Install the FrontPage Server Extensions from the MSDN Web site  Possible Solution: If the server on which you are publishing Web sites doesn’t support the Server Extensions or SharePoint Services, you won’t be able to use features requiring them

27. 27Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems (cont.)  Problem: The command for a FrontPage feature that I’m trying to use is dimmed  Possible Solution: Make sure your Web site is enabled for the technology required to display the feature in the Page Options dialog box  Possible Solution: Check the Browsers and Browser versions settings

28. 28Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems (cont.)  Problem: A FrontPage feature is displayed correctly in FrontPage but not in the browser  Possible Solution: Set your Web site to disable features not supported by your browse  Possible Solution: Upgrade your browser to a higher version  Possible Solution: Change the browser’s settings to disable certain technologies from running or being displayed

29. 29Finalizing a Web SiteUnit P Troubleshooting FrontPage Problems (cont.)  Problem: A FrontPage feature is displayed correctly in FrontPage but not in the browser  Set browser to display hyperlinks in certain colors and display text in different fonts and font sizes  Check and see if the browser’s default settings have been changed  Use your browser’s Help system to learn how to restore the browser’s default settings

30. 30Finalizing a Web SiteUnit P Summary  Testing a Web site’s function  Reporting broken hyperlinks  Customizing a Site Summary report  Reporting file status

31. 31Finalizing a Web SiteUnit P Summary  Setting publishing options  Publishing a Web site to another server  Learning about your server configuration  Troubleshooting FrontPage problems