Member Avatar for Pinchanzee
Pinchanzee 0 Light Poster

Nevermind, finally found something, SSI's seem to sum it up perfectly. Now I just need to get my head around these little buggers..

Thanks anyway :) Free for close/delete/whatever you like.

Edited by Pinchanzee because: n/a
  • 1 Contributor
  • 0 Replies
  • 78 Views

Dani AI

Generated

Good call, — SSIs are a lightweight way to keep repeating parts (sidebar, header, footer) DRY without moving to a full framework. They work well for small static sites or when the include content is purely markup.

Typical usage looks like this:

<!--#include virtual="/includes/sidebar.html" -->

Use virtual when you want a URL-like path (document-root relative). file is a filesystem-relative include and can behave differently with aliases. On Apache you usually need mod_include enabled and either use the .shtml extension or configure the server to parse .html (see Apache mod_include). If you host on nginx, its SSI module is documented at .

A few practical notes: SSIs are parsed per response, so many includes add CPU overhead — cache the output where possible. Avoid SSI exec or other execution features unless you fully trust the environment. If the site grows or needs logic, consider server-side templating (PHP, templating engines) or build-time includes (static site generators) instead of many SSIs. If an include "does not work", check file extensions, server options (Options +Includes), and hosting docs — many shared hosts disable SSI by default.

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.