Product Review: FrontPage 2000

Written by Richard Lowe


Several years ago (way back in 1994) I had to put together a heck of a lot of documentation to help me get my job done. I started with Microsoft Word, writing over a thousand pages in a couple of months. This was all documentation about how to manage our mainframe computer system and it's associated application programs.

After a while, I decided it would be better to maintain this set of documents on an intranet instead of as printed manuals. Why? Well, I was so fast at writing and changingrepparttar text thatrepparttar 134540 documents were out-of-date as soon as I printed them. I thought it would be good to store them as a local web site, thus allowing anyone accessing them to always getrepparttar 134541 most recent version.

I looked around briefly for a product which would allow me to create this intranet without too much bother. I rejected most products right away because they required me to learn HTML: I wanted to write documentation, not learn some obscure coding language (I already had learned too many of those and I knew exactly how long and difficult it can be).

Somehow I managed to stumble upon a nice, new (atrepparttar 134542 time) product called FrontPage. I likedrepparttar 134543 program right away, simply because it had a great WYSIWYG editor which made it extremely simple to create web pages. I especially likedrepparttar 134544 way that FrontPage implementedrepparttar 134545 creation and editing of tables.

Understand, I looked at a lot of programs and I've continued looking since that time. Virtually all ofrepparttar 134546 programs that I've seen didn't have a well defined way to create tables. FrontPage was different - tables were (and are) very well implemented.

That was an early version ofrepparttar 134547 program (I think it was FrontPage 97), and it's changed quite a bit inrepparttar 134548 intervening years. FrontPage 97 tended to crash a lot, and FrontPage 98 bombed out even more often. However, FrontPage 2000 turned out to be just about perfect for my needs (which, admittedly were very simple).

Update Your Entire Website Instantly Using Server Side Includes

Written by Vishal Rao


Imagine my plight... I have 100+ pages on my website and I have to change my e-mail address andrepparttar copyright info on allrepparttar 134539 pages. The reason...

My mail box is over-flown with junk mails.

My only option is to edit all my web pages offline and then upload each one of them again, not to mention countless errors I make inrepparttar 134540 process.

100+ pages is still a small website. Imagine what it will be like if my website had 1000+ pages?

Sounds scary right?

If you would like to avoidrepparttar 134541 kind of mess I'm in right now, you have one option. Start using "Server Side Includes (SSI)"

In technical jargon, Server Side Includes are directives which you can place into your HTML documents to execute other programs or output such data as environment variables and file statistics.

If your only intention is to manage your website more effectively and painlessly, it is more than enough if you learn one "Directive" of SSI -repparttar 134542 "Include" directive.

In simple terms, SSI Include is a line of code which you can use in your HTML documents to include contents from other documents. In other words, change just one file (the Include file), and your ENTIRE SITE is instantly updated!

The basic syntax of an Include directive is:

Where PATH_TO isrepparttar 134543 "VIRTUAL" path to include file on your server.

Here's how to include your copyright info and navigation links using SSI Includes...

First, you need to check with your server administrator whether your server supports SSI or not. Most servers support them.

Second, you need to rename all your HTML files with extension .shtml

Cont'd on page 2 ==>
 
ImproveHomeLife.com © 2005
Terms of Use