[yaozers]

I've been trying to figure out an easier way to update my navigation than re-hand-coding about 20 pages every time there're any changes.

After posting a question on this forum, I was able to get help and now I'm using a simple SSI one line code to attach my navigation to every page.

<!--#include virtual="pagename.html"-->

This has been great because I only need to change one file, instead of 20. Earlier this week I decided to also make my header and footer into separate html pages and include those.

My question is: What are the potential issues with including a separate html for commonly used blocks of code?

Is the load time slower? Will some browsers not include/execute? Compatibility, accessibility issues? Are there security issues?

It just seems almost too simple. Any insights would be helpful, as I know next to nothing about SSI.

[jamiecarruthers]

the name "server side includes" shows the including is done on the server side! This means no browser issues.

Sure, load time will be fractionally slower but not enough to cause a problem

[freelancr]

What you are doing is the best way of doing it, and probably faster as the files will be cached. The best way of doing this is with a server side language like PHP or using masterpages in ASP.NET.

Personally I chose the latter, but thats because the moon is made of cheese.</drunk>