"Empty" SSI built into design stage in anticipation of later additions
Is this workable? Anybody use it as a design strategy
Webwork
6:04 am on Nov 11, 2003 (gmt 0)
Anyone see any downside or problems coding "no content" SSIs into strategically placed cells &/or tables on formatted/templated pages that will be loaded with other information?
The pages will be static pages except for information that will be added by SSIs.
Initially only footers and headers will be filled by SSI.
I would like to reserve space for possible data feeds triggered by the SSIs, etc.
4eyes
8:38 am on Nov 11, 2003 (gmt 0)
I do this regularly.
There is no significant downside that I can see. As it is all done 'server side' There is no way that search engines or visitors can see anything different from usual.
divaone
1:45 pm on Nov 11, 2003 (gmt 0)
i also do this on a regular basis, although i do try to separate as much of my pages as possible without sacrificing anything. one page may have 5 parts. but adding empty includes, be they ssi or php includes, is a great way of anticipating growth of the website and imho signifies a web developer who thinks outside the box :o)