Member Avatar for gbgraphix

I need help please...When I change a link on a web page I have to go to every single page of the whole website to make the same change. For example, if I add a new link on one page, I have to go through all the pages of the entire site to add the new link to those pages as well. This could get pretty time consuming considering the site I am working on has over 50 web pages. Does someone know an easier way or is there a way to apply the change to the entire site??

Thanks for you help!!!

  • 2 Contributors
  • 2 Replies
  • 122 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by Dani

Dani AI

Generated

This is a common maintenance problem: the navigation/footer is duplicated across many static pages. already pointed to two good directions (server-side assembly and FrontPage shared borders). Below are practical options, clear next steps, and short troubleshooting notes so the change really is "one file, many pages."

If your host supports PHP, create a single partial (for example header.php) that contains the shared navigation, and include it from every page. Save pages as .php (or configure the server to parse .html as PHP) and use PHPsincludeto pull the partial into each page. This keeps one source of truth — editheader.php` and every page shows the update. See the official PHP include docs for details: PHP include.

If you must stay in FrontPage, use its Shared Borders feature so navigation is managed centrally and propagated when you publish. If the server supports Server Side Includes (SSI) that is another lightweight option — SSI lets the server insert a shared file into pages at request time. Both require server support; check hosting before committing.

When server-side options are not available, use a build or edit-time approach: keep a single nav file and use a simple script or your editor’s “replace in files” or a static site generator to assemble pages locally, then upload. This is safe and works on any host, but needs a small build step.

Quick troubleshooting tips: use consistent relative or absolute paths inside the included file (path mistakes are the most common issue), clear caches after changes, test pages from several directories (includes behave differently by path), and keep backups or version control so you can revert if an include breaks the site.

Recommended Answers

All 2 Replies

Member Avatar for Dani

There are two ways to do this. The first is to use a server side programming language such as PHP. A dynamic website, such as DaniWeb, allows for interaction (such as forums) and also allows for shared borders. However, you would need to learn a programming language to do this.

Another way to do it is with server side includes (SSI). You can basically put the header and footer into separate .html documents, and include them within your documents. Then, if you need to make changes to the header and footer, there is only that one file to change.

Here is an Apache tutorial on SSI:

Member Avatar for Dani

Oh I'm sorry. I didn't realize you were using Microsoft FrontaPage. If so, there is an option called Shared Borders, I believe.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.