John,
I think I see what you are doing now, and why you are having some success in
just editing the html code in Publisher.
When you go to
http://johngriff.com/tmp2/ and compare the file sizes of the
three test sites, you get your first clue. Notice that the 2007 file is only
44kb, while the other two are much larger at 303 kb and 406 kb? I am betting
that when you produced the html code for the Pub 2007 site, you did a
"Publish to the Web", but when you used Pub 2007 you did a "Save As" a web
page? "Save As" a web page is the proper way of doing it in Pub 2000, and
"Export As" in Pub 2002. At least MSFT has been consistent between 2003 and
2007.
When you "Publish to the Web", the Publisher html coding engine produces
"filtered" html code, or the lightest cleanest code possible. When you do a
"Save As", Publisher produces "Rich" code or a "heavy page" that contains
Office tags and coding that allows you to open the .htm files in Pub and
edit them. You can't do the same thing with filtered pages, but the file
sizes are a lot smaller and load faster. You can see the difference in all
the lines of code if you View > Source.
I think it is these "Rich" pages with the heavy code that gives Publisher
web sites such a bad rep for code bloat. This is part of what Rob was
commenting on when he suggested that Publisher "excreted" its code. ;-). And
you can see the point. The difference between 44 and 303 kb is huge. I hope
Rob catches this thread so he can see an example of how Publisher can
produce code that isn't as bloated as it used to be.
I also suspect that you are using FireFox or some other browser as your
default, given your comment about the bottom navbar. The links work in IE,
but don't in FF, Opera and probably Safari. Tis a bug. One workaround is to
ungroup the bottom navbar from the side navbar. Just select it, Arrange,
ungroup. Now the links will work, but the navbar won't be updated if you add
a page...you will have to do it manually. You also have to do it on each
page if I remember correctly.
Anyway, if you want to continue doing it the way you are, then that is up to
you. The one big draw back I see might be that you can only work on one page
at a time, and the pages will be heavier. However, given that your web page
code is in "rich" code, it won't be hard for you to assemble a Pub file if
you choose, or break the pages up into separate Pub files and manage your
site that way. Anyway, if you want more details on that, let me know.
Thanks for taking the time to make and publish those example sites.
DavidF