Large Website vs Subwebs

[JCO]

I'm in contact, with the folks that handle the server, to see if the server
time-out can be made longer. Not sure what the results will be yet. My
debate is... do I break up a large website into subwebs?

My question to this group is this:
1. If I break this up into subwebs, what will be the disadvantages (other
than the fact that I will have to open different projects to make specific
updates)?
2. What are the advantages?
3. At what point does FrontPage 2003 begin to have issues with large
websites (number of pages, number of files)?
4. If I break it up into subwebs, should each have an Index.html? If so,
won't this mess up my Search capabilities ... which is set up for my
website.

Thanks

 

[Ratatooie]

I'm in contact, with the folks that handle the server, to see if the
server
time-out can be made longer. Not sure what the results will be yet. My
debate is... do I break up a large website into subwebs?

My question to this group is this:
1. If I break this up into subwebs, what will be the disadvantages (other
than the fact that I will have to open different projects to make specific
updates)?
2. What are the advantages?
3. At what point does FrontPage 2003 begin to have issues with large
websites (number of pages, number of files)?
4. If I break it up into subwebs, should each have an Index.html? If so,
won't this mess up my Search capabilities ... which is set up for my
website.

Thanks

Subwebs are folders, so you will have a new index.html

Subwebs also have individual search functions, you will not be able to
search from one to the other. Likewise for other components such as
includes and so on.

Have you tried just using folders to organize files? FrontPage lists the
files in the folders, and enumerating that can take a while if you hav more
than a couple hundred files in the folder. Organize organize organize and
it should get better. Also, there never has been a webmaster I have met
that adequately cleaned up the site as far as unlinked files and extra stuff
they were not using. Try using the "hyperlnks" view to find orphaned files
and get rid of them. It may speed things up a lot.

There is no fundamental limit, though if you are not on broadband or the
server is old or slow you could have problems.

Subwebs are nice if you have different "areas" that different people edit,
or if you move your site around occasionally it's easier to publish 6 sub
webs and a root web than one very large root web.

If you have lots of static, outside images or something of that nature, you
could remove them from the site and transfer them to the host via FTP in a
virtual folder so FrontPage does not "see" them.

It all depends on the nature of the site, and how many files you are talking
about....

 

[JCO]

I definitely have lots of folders and everything is very organized.
Looking at 117 MB of storage, 4395 Files and 353 Folders (that is using
explorer and doing the properties). Obviously that would include all the
folders that FP adds automatically.

The numbers above do not include the existing 4-subwebs on the server.. only
the main website.
I have no way of judging how big this is.
Not sure what you mean by enumerating them other than what FP does
automatically.

 

[WenJun Zhang[msft]]

Hi,

What Ratatooie meant is FrontPage may take long time to list large deal of
files in a directory. I agree subweb isn't required if all the contents are
belong to the same 'logical web site'(all of them are related). You just
need to separate the files into different directories as best practise.

Also if you do not have particluar large file, generally FrontPage will not
hit timeout problem during sync the data. If you do meet any problem on
this, consider to use some more reliable and resumable protocol/client to
upload the files(e.g: FTP).

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Thomas A. Rowe]

FYI: Do not use FTP is publishing to a server that has the FP extensions!

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[JCO]

Right!! I know that if I FTP, it will mess up the FP Extensions.
The folks, on the server end, will not change time out on the server.
However, for some reason, I am able to update now. I suspect they had some
issue and resolved it...although they don't want to admit it.

For now I will leave it as is... and not break it up into subwebs. Maybe
the problem won't come back
Thanks

FYI: Do not use FTP is publishing to a server that has the FP extensions!

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

Hi,

What Ratatooie meant is FrontPage may take long time to list large deal of
files in a directory. I agree subweb isn't required if all the contents are
belong to the same 'logical web site'(all of them are related). You just
need to separate the files into different directories as best practise.

Also if you do not have particluar large file, generally FrontPage will not
hit timeout problem during sync the data. If you do meet any problem on
this, consider to use some more reliable and resumable protocol/client to
upload the files(e.g: FTP).

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.