Make a virtual web normally.  Right click and choose "FrontPage 2002 Server
Extensions - Extend"

In the resulting managment web page, add or create the user as an
administrator of the web.

You do _NO_ modifications to file permissions in the root folder, and _NO_
configuration in the Users area on the server for this.  The FrontPage
(Sharepoint) administration web site does that for you.

No, they'll all be broken.  You need to treat DNS separately.  I'd suggest
setting up a second hostname www2.whatever.com and publishing to that.
Then, when you are satisfied the site has been moved and is operating
correctly, you switch DNS to send traffic to the new location.  That avoids
down time and gives you the luxury of figuring stuff out on your own time
without a webmaster complaining the site is broken.

Yes, you can do that, but you probably don't want your webmaster editing
later with it, so you need a site administrator account anyway.

None, you don't.  See above.

Patch patch patch patch and patch.  Other depends on exactly what you are
doing.

Yes.  Once you have the FP site configured completely you can let them do
it. (I would advise that, as they probably have more experience at it.)

Windows does cluster server for that, or there are third party apps to do
it.

Hi Joe,

I am going to differ a little on this.
I never give out FrontPage level "administrator" to web content owners,
instead at most giving "advanced author" role.  The "administrator" role
does enable them to do some things, like "server health", and defining
new machine local user accounts for use with their web/website.

All that you need to do, at a minimum, is to
a) define a new website, or a new web vdir in an existing site
b) extend that with the FP server extensions
c) define a normal, limited account for use by the owner
d) use the Sharepoint Admin pages, or via the Administer link
   on the page you are left on after extending, to grant Advanced
   Author to the account defined for use with the web or site root web
This can also take the form
a) define new website in IIS if this is new entire site, not just new
   web in existing site.
b) browse to the Sharepoint administration website
c) if this in new site, select to extend the site
else
c) if this is a new web in existing site, select to administer that site,
   and on the site's admin page click to add new web
d) access the Sharepoint admin page for the new site or web and
   set grant of Advanced Author role to Windows limited account
   that will be owner/publisher

Much depends on what you mean by a public internet webserver
If you are looking at hosting webs for diverse owners, be aware that
a standard install of FP server extensions will NOT help you to keep
one web/website owner from reading source of another, even if you
use different app pools configured to use different accounts.  Further,
if you go to the work of making sure there is such segmentation, which
is not easy to do, then a FP extended web owner with the FP role of
Administrator can destroy that separation by simply triggering some of
the server health functions.

Roger

Hi,

You can use MS Application Center 2000 for load balancing and other admin
functions such as application pool admin and monitoring. I can supply more
info if needed.