|
When you insert an image onto the Publisher document page (Insert > Picture...)
that image is then embedded into the pub file. When you compile the pub file
to web pages* the image is copied to a new image file generated and named
by Publisher. When Publisher does this it works its way down the page, top
to bottom, making it's own copies of your inserted images. Unfortunately,
publisher doesn't care if you inserted the same image 10 times throughout
your Publisher web document. If you used the same image 10 times, for example,
then you'll get 10 copies (they all need to be uploaded!), and that is a
redundancy issue on both the server and the client (your site visitor).
To avoid this issue, it is best to write a link to your image file; especially,
if you intend to use an image several times across the site. This way there
is only one file copy of your image on the web server, and only one copy
being sent to the client. You first need to decide where on the site you
will keep the image file. A typical convention is to create an "images" folder
and keep your image files there. So an example link to the image file would
be:
/mydomainname/images/mypicname.gif
You then use the HTML fragment dialog to insert the linkage code (Insert > Html...).
You simply draw the fragment dialog on the page where desired—the same as
you do for inserting a text box or a graphic—and then write the code into
the dialog box and click OK. The code you write and insert for this is very
simple:
<IMG SRC="YourLinkGoesHere">
For example, if I had a logo I wanted at the top of the page and this logo
was named logo.gif and I had it at the same folder level as
my index.html page, I would click Insert
HTML Fragment,
draw the outline of my logo at the top of the page and type <IMG SRC="logo.gif"> into
the dialog box and click OK. That's all there is to it.
When that example page is then saved and published Publisher does not have an
image to make copies of, but rather it codes my link and uses my original copy
I previously uploaded. That way when the page is viewed the visitors browser
(client) only has one image file to download. And if it's an image that is
used on other pages in my site then those pages will load faster in the client
browser, because that image is already cached by the browser.
The faster pages load in the client browser, the happier your visitor will
be during their stay. And you know how important that is.
* "Export as web page", or "Save as web page", or "Publish to the web" - depending on version.
Enter to win Office 2003 Professional - http://www.barvin.com/giveaway.aspx
Enter to win Publisher 2003 - http://www.davidbartosik.com/giveaway.aspx
© 2003 David
Bartosik. David is a Software Developer and Web Site Designer. He has been a Microsoft MVP for Publisher since 2001. You can learn more about Web design
and Publisher by visiting his site at davidbartosik.com.
David is also the Editor of BARVIN, an online magazine for motivation, insight, and helpful ideas. He invites you to visit at barvin.com. You can contact him at
dbtech@davidbartosik.com.
|