If you open an .shtml file in a browser, you will not see the tags. You will only see the final, processed HTML. To view the actual raw include logic, you must open the file locally in a text editor (like VS Code or Notepad++) or view it via an FTP/SFTP connection to your server.
In SSI, it’s common to split pages into top.shtml , nav.shtml , footer.shtml , etc. “View shtml top” could mean: Display the contents of a file named top.shtml that is included in other pages.
To create a "Long Feature" using the (Server Side Includes) format for a "Top View" (often meaning a hero section or a prominent header layout), you can combine standard HTML5 structure with SSI directives. This approach allows you to keep your code modular and easily updateable across multiple pages. 1. Structural Overview view shtml top
: Unlike a standard static .html file that is sent directly to a user's browser, an .shtml file forces the webserver to scan (parse) the page for specific server commands before delivery.
If index.shtml includes top.shtml , and top.shtml tries to include index.shtml , you’ll create a loop. Your server might time out. Always examine the top of each file to ensure no circular references exist. If you open an
Options IncludesNOEXEC
When a user reports that they cannot content correctly, three common problems emerge. In SSI, it’s common to split pages into top
head top.shtml head index.shtml