From Microsoft:

FrontPage 2003 provides the features, flexibility, and functionality to help you build better Web sites. It includes the professional design, authoring, data, and publishing tools needed to create dynamic and sophisticated Web sites.

FrontPage 2003 advances your Web development in three key areas.

Designing:

• Use enhanced design tools to produce better looking Web sites. New layout and graphics tools make it easier to design exactly the site you want. 

Coding:

• Use design tools to generate better code, or expand your code skills. Use built-in scripting tools for interactive results. And with professional coding tools, you can write code faster, more efficiently, and with greater accuracy.

Extending:

• Connect with people and information in new ways by building Extensible Markup Language (XML) data-driven Web sites using the first commercially available, completely WYSIWYG ("what you see is what you get") Extensible Stylesheet Language Transformations (XSLT) editor. The enhanced publishing features and options help you get your Web pages online more quickly.

Design Better-looking Sites

• FrontPage 2003 includes tools and layout and graphics features to help you work faster and design professional Web sites.
• Work with graphics from other applications, giving you more control over how images are displayed and saved. 
• Use dynamic Web templates to modify entire sections of a Web site. By updating the master template, changes are automatically made to all pages linked to that template. 
• Target specific browser or screen resolutions by using browser and resolution reconciliation. See how your site will look in various combinations of browsers and resolutions. 
• Create and manipulate tables used for layout purposes, and provide pixel-precise control of your layout.
• Use manipulation tools to more easily work with multiple images and pieces of content that sit in the same space, and to create visual effects, such as pop-up menus.

Generate Code Faster and Easier

• The design tools in Frontpage 2003 generate efficient and clean Hypertext Markup Language (HTML), and give you more control over the code. Or, you can apply your coding knowledge by taking advantage of the professional coding tools. With the scripting tools you can create an interactive experience for your audience. And, because the coding tools are easy to work with, you can even use them to start learning HTML.

Coding Tools:

• Use a split view to see modifications made in the Design View automatically updated in the Code View. 
• Select, modify, and manipulate tags easily using the Quick Tag Selector and Quick Tag Editor.
• Simplify code writing and make it less prone to errors with Microsoft IntelliSense® technology. The technology is available for HTML, cascading style sheets, XSLT, Microsoft JScript®, and Microsoft ASP.NET. 
• Remove extraneous code generated by Microsoft Word or other Web authoring programs.

Scripting Tools:

• Enhance interactivity on your site without writing a line of code by using behaviors to author JScript.
• Take advantage of support for IntelliSense and scripting tools for authoring JScript and Microsoft Visual Basic® Scripting Edition (VBScript).
• Extend the Power and Reach of Your Web Site - With Microsoft Windows SharePoint Services and Windows Server 2003 connected to FrontPage 2003, you can modify and present live data from a range of sources, including XML, to build rich interactive data-driven Web sites in a WYSIWYG editor. Users can post to the Web using just their browsers, while choosing from a broad range of publishing options.
• Data-driven Web Sites Enabled by Windows SharePoint Services - Allow users to post to your Web site using just their browsers. Web logs, issue-tracking lists, and news and reviews sites can be built with just a couple of clicks. 
• Insert data views and configure data sources—including XML varieties, Windows® SharePointâ„¢ Services data, Web services, and OLE Database (OLEDB) data sources. 
• Handle XML data and authoring and XSLT formatting directly in the FrontPage WYSIWYG Design View to create XML data-driven Web sites. 
• Show or hide items or reformats based on data values or position in the data view by using Dynamic conditional formatting. 
• Build Web Parts Pages by creating Web Parts Zones and inserting and connecting to Web Parts in other products, including Microsoft Office SharePoint Portal Server 2003, Windows SharePoint Services, and FrontPage 2003.

Publishing Technologies

• Move files easily between local and remote locations and publish in both directions.
• Connect to remote sites easily with the Web import dialog, which simplifies connection types, and working with Secure Sockets Layer (SSL). 
• Publish to File Transfer Protocol (FTP) and Web Distributed Authoring and Versioning (WebDAV) servers from the new Remote Web Site tab.
  
  

Yes. However, you do need to follow some special instructions to Publish your FrontPage webs to your Angelfire account.

First of all, you'll need to "enable" your Angelfire account for the FrontPage extensions. To enable your directory for the use of Microsoft FrontPage, head to your "Website Details" page, within your "My Account" page.

Angelfire supports FrontPage 2003, FrontPage 2002, FrontPage 2000, and Office 2000, Office 2003, and Office XP are also supported. FrontPage versions prior to 2000 are not supported.

However, if you're having technical difficulties with any version of FrontPage, we suggest contacting Microsoft for technical support on the product.

Yes.

However, some functions of your site may not work properly, if you remove your FrontPage extentions from the site.

Certain aspects of your coding may rely on FrontPage features, to work. Removing those features may cause menus, applets, or other features to cease working.

Please use discretion in removing anything FrontPage related from your site, unless the site is built over from scratch, not using Front Page.

In order to publish to your Angelfire account with Microsoft FrontPage 2000, 2002 and 2003, you will need to make sure you have done the following:

1. In your FrontPage application, make sure the correct path is entered into the "Look in Box" when in the Web Publishing dialogue box, http://www.angelfire.com/dir/membername/ The last slash is the key. i.e. File -> Publish Site...
2. Within your Angelfire membership, navigate to the My Account page and click on Website Details.  Within the section titled Preferences, disable and then re-enable your site for FrontPage ® Server Extensions. FrontPage ® occasionally becomes confused about whether an account is enabled or not; this will fix that without harming the contents of your site.
3. Try deleting unneeded files from your local Webs before you publish. Your FrontPage ® client and our server sometimes won't be able to finish checking the files for updates before the client gives up and times out. You might need to republish multiple times before you've deleted enough files for the error to go away entirely.
4. If none of the above fixes eliminates the error, then try deleting all of the directories that start with "_" (underscores) in Web Shell. Re-enable FrontPage ® Server Extensions and you should be able to publish your FrontPage ® Web site completely from scratch.

Good luck with your FrontPage publishing.

When you try to publish your Microsoft FrontPage Web site you should not be prompted for the ftp server name and directory path. If you are, then Microsoft FrontPage has set "ftp publish" as the default and you will need to change it.

If you go to the file menu bar on Microsoft FrontPage choose "Publish FrontPage Web". If you are prompted,(and this does not always happen), choose FrontPage as the publish method, not ftp://ftp. You will then need to enter the location to publish to:

http://www.angelfire.com/dir/membername/, your directory, member name and password and you will be on your way.

No need to panic. Although the error message you're getting sounds scary, the problem is usually simple to correct.

This is a problem caused by either a slow connection to the Angelfire servers or the simple lack of a slash in the publish to address. Let's start with the simple solution.

The address that you want to publish to, especially if you have already published the site to your Angelfire directory is:

http://www.angelfire.com/state/yourmembername/
The last slash is key.

You can also try to "fool" FrontPage into not using the cached information by removing the last few letters that are automatically filled in for the publish to address, and then reentering them. This makes FrontPage think that you are publishing to a new address, bypassing the cached information.

The second cause of this problem is a slow connection to the Angelfire servers from your computer. We see this quite often with large ISP's, such as AOL, Mindspring, Prodigy and Earthlink to name a few. (Even your cable modem connection slows down when traffic increases.) What you need to do when this happens is close FrontPage completely, open the web again in FrontPage and attempt to connect again. Each time you receive that error message, FrontPage caches it and you need to close the program to start again.

If you have published your FrontPage webs and your old Angelfire index page still appears, what you should do is to open your site using FrontPage, by opening the web folder that you created when you enabled your directory for FrontPage.

Once the directory opens, you should right click on the index.html file, which is your old Angelfire page.

Choose delete and we are halfway there.

You then need to right click on the index.htm file, choose rename, and rename this file index.html, which is the default here at Angelfire.

The folders in your WebShell/Account that start with "vti", are the FrontPage extentions for your account.

You can only remove these if you're no longer using FrontPage to edit, maintain or create your site.

If you're not using FrontPage any longer, you can "Disable" these folders by disabling your Front Page extentions, from your "Website Details" page, which can be found under "My Account", when logged in.