Microsoft FrontPage 2003 Illustrated Complete

1. Microsoft FrontPage 2003 Illustrated Complete Working in a Published Web Site

2. Objectives • Publish a Web site • Open a Web site from a server • Recalculate and verify hyperlinks • Test a page that contains a form component Working in a Published Web Site Unit H

3. Objectives • Test a page that contains a search component • Set permissions in a Web site • Create a hit counter • Maintain a published Web site Working in a Published Web Site Unit H

4. Working in a Published Web Site • Windows 2000/XP lets you install a Web server on your computer so you can test a Web site before publishing it on an Internet Web server • Most developers use a local Web server to test pages and make changes before publishing a site Working in a Published Web Site Unit H

5. Publishing a Web Site • After creating a Web site, you must publish it to a Web server • Internet Information Services (IIS) is a Web server that you can install on your computer using your Windows 2000/XP Professional CD • IIS provides the services necessary to make your desktop computer function as a Web server Working in a Published Web Site Unit H

6. Publishing a Web Site (cont.) • You can use IIS to publish your FrontPage Web site on your computer, without needing a network connection to an Internet Web server • The default configuration for IIS is for it to start when you start Windows • IIS runs in the background Working in a Published Web Site Unit H

7. Publishing a Web Site (cont.) • Remote Web Site view Working in a Published Web Site Unit H

8. Opening a Web Site from a Server • Once you publish a Web site, you have two copies of it - one stored on a disk drive and another stored on a server • The server-based Web site contains the same files as the disk-based Web site, but it is stored in a location that has the FrontPage 2002 Server Extensions or SharePoint Services installed • You can open a Web site directly from the server using FrontPage Working in a Published Web Site Unit H

9. Opening a Web Site from a Server (cont.) • When you make changes to a server_based Web site, your changes are updated immediately in the Web site stored on the server • Changes you make to your server-based Web site are not automatically saved to your disk-based Web site • To keep your disk-based Web site current, you must make changes to it, then use Remote Web Site view either to publish your remote Web site back to your local Web site or to synchronize the two copies of the Web sites Working in a Published Web Site Unit H

10. Opening a Web Site from a Server (cont.) • It is not usually important to maintain consistency between the original disk-based Web site and the new server-based Web site, but it is good practice to keep a backup copy of the “live” Web site on your hard drive Working in a Published Web Site Unit H

11. Opening a Web Site from a Server (cont.) • Open Site dialog box Working in a Published Web Site Unit H

12. Recalculating and Verifying Hyperlinks • After publishing a Web site, it’s a good idea to: • Repair any broken hyperlinks • Update the shared border and link bar files • Update all FrontPage components • Update data on the server • Delete any unused theme files • This process is called recalculating hyperlinks Working in a Published Web Site Unit H

13. Recalculating and Verifying Hyperlinks (cont.) • You can also verify hyperlinks, which causes FrontPage to check the validity of each hyperlink in a Web site to look for broken links • Recalculating hyperlinks ensures that the Web site’s links exist • Verifying hyperlinks ensures that the Web site’s links are valid Working in a Published Web Site Unit H

14. Recalculating and Verifying Hyperlinks (cont.) • Recalculate Hyperlinks dialog box Working in a Published Web Site Unit H

15. Recalculating and Verifying Hyperlinks (cont.) • Verify Hyperlinks dialog box Working in a Published Web Site Unit H

16. Recalculating and Verifying Hyperlinks (cont.) • Reports available in a Site Summary report Working in a Published Web Site Unit H

17. Testing a Page That Contains a Form Component • After publishing a Web site, you must test pages that contain components to ensure that they work correctly • When testing a Web page that contains a form component, you need to verify that the form collects and stores data in the correct format • You can also view the results file on the server to confirm that the data is being stored in the correct format Working in a Published Web Site Unit H

18. Testing a Page That Contains a Search Component • When testing a Web page that contains a search component, you need to verify that the search function works properly by searching for words you know exist in your Web site Working in a Published Web Site Unit H

19. Setting Permissions in a Web Site • You can use FrontPage to secure a published Web site based on the level of access you want to provide other users • A Web site’s administrator assigns different types of permission to users who access a Web site • Browsing permission lets a user open a Web site in FrontPage and view it after it has been published Working in a Published Web Site Unit H

20. Setting Permissions in a Web Site (cont.) • Authoring permission lets a user create and edit pages in the Web site • Administering permission lets a user create new Web sites and set permissions for other users • Usually, only the Web site’s administrator has administering permission Working in a Published Web Site Unit H

21. Setting Permissions in a Web Site (cont.) • Edit Permissions page Working in a Published Web Site Unit H

22. Creating a Hit Counter • A hit counter is a Web component that counts the number of times a page in a Web site has been opened or refreshed using a Web browser • Hit counters usually appear on a Web site’s home page • A hit counter requires a server and the FrontPage 2002 Server Extensions or SharePoint Services for processing, so you can test it only in a server-based Web site Working in a Published Web Site Unit H

23. Creating a Hit Counter (cont.) • FrontPage will create the code to display and increment the counter when you insert it • You can accept the default settings for the hit counter, or change the counter style and other properties if desired • The counter style is implemented using a default or custom-designed GIF picture that displays the digits zero through nine Working in a Published Web Site Unit H

24. Creating a Hit Counter (cont.) • Hit Counter Properties dialog box Working in a Published Web Site Unit H

25. Maintaining a Published Web Site • Some ISPs create a stats, logs, data, or similarly named folder that stores Web page created by the server • This folder contains data about the Web site’s usage and files Working in a Published Web Site Unit H

26. Maintaining a Published Web Site (cont.) • An ISP might create a usage log, which is a page containing information about the number of times your home page has been opened, the number of times various pages were opened each day or each hour during the day, or the total number of times a Web page was refreshed during a single session Working in a Published Web Site Unit H

27. Maintaining a Published Web Site (cont.) • The information provided about a Web site varies based on the ISP that hosts it • Depending on your ISP, you can open your logs either from Reports view or by using a browser • Check with your ISP to locate its usage logs for your site Working in a Published Web Site Unit H

28. Maintaining a Published Web Site (cont.) • Traffic reports provide data about the number of visitors to your Web site, page view, hits, and the total number of bytes transferred from the server to a browser • Page reports provide data about the number of page views for each page in the Web site Working in a Published Web Site Unit H

29. Maintaining a Published Web Site (cont.) • Domain reports provide data about the number of visitors from each domain name (such as aol.com) that used a browser to access the site • Browser reports identify the different browsers used to access your site and the number of visitors using each browser Working in a Published Web Site Unit H

30. Summary • After publishing a Web site, you can open if from the server • You should recalculate and verify hyperlinks in published Web sites • You should test pages that contain form or search components • You can set permissions in a Web site Working in a Published Web Site Unit H

31. Summary • You can create a hit counter for a Web site • Use the logs that your ISP provides to aid in maintaining a published Web site Working in a Published Web Site Unit H