Forum Moderators: open
<code>
Home
Section 1
-subsection1
-subsection2
Section 2
-subsection1
-subsection2
</code>
Thank you for any suggestions.
These take a second (or third...) document and merge them together into one file before it is sent to the user.
So on your server you could have 4 separate files:
1) header.html
2) footer.html
3) navigation.html
4) index.shtml (shtml indicates it includes SSI)
From the index file you can get the server to put header at the top, the navigation down the side and the footer at the bottom. Now when you need to change the navigation, the header or the footer - you only have one file to change (as content.shtml and contactus.shtml will include the same header, footer and navigation files).
Regarding SSI, can you pass variable to SSI? For example, I want to highlight the current menu and pass a variable telling the server if the sidebar is called by a certain page, the menu for that page will use a different color. Is that possible?
Regarding FP, I have used FP2000, that's good they got rid of the dependence on extensions, so I should give it a try.
Thanks again.
Regarding FP, I have used FP2000, that's good they got rid of the dependence on extensions, so I should give it a try.
To reiterate what Bill said, FrontPage has never required the server extensions except for special features that many publishers don't use. I've been creating and maintaining sites with FrontPage since 1996, and I never had a Web hosting service that offered the FP server extensions until 2001.
Just to clarify things, FrontPage 2003 doesn't rely on the server extensions for basic Web publishing, but it does support the server extensions from earlier versions of FrontPage. For example, I've been using FrontPage's shared borders, included files, and the occasional form since FP2000, and my current version of FrontPage (2003) works with the FP2000 server extensions at my hosting service.
Finally, if you want to use *all* of the advanced bells and whistles in FP2003, you do need a hosting service that offers Windows Sharepoint Services. But that's only of academic interest unless you've purchased FP2003 for those specific features.
Make your navigation on one page, include it onto every page on your site, then when you want to update the navigation just update that one page. FP will propagate those changes throughout every page on your web. It's pretty powerful.