With much gratitude to Victor (thanks so much for your work and sharing spirit) ...I am sharing this integration of minishowcase embedded into a webpage containing the site header, footer and side menu -->

rush-creek.com/minishowcase/index.php

1) The main interesting/unique thing to point out (that anyone can freely inspect at the page posted) is I tweaked the css to allow for a fully fluid functionality. When you visit, be sure to resize the window, both manually and using zoom, to see the effects.
**The main benefit** of doing this is it allows for more amicable embedding of minishowcase into an already existing page design by diffusing the compromise it otherwise might impose to pre-existing site design with its natively "rigid" structure. I kind of went overboard ...to the point of making even the left side of the thumbnail-board flow around the minishowcase gallery menu (just to make it more 'completely' fluid).

2) Another thing worth mentioning.. for those noticing/questioning the use of relative paths (you know who you are, and why you are questioning this ;^), those are all code generated from a call to a single function (for the whole site), not hard coded. I have an unorthodox co-ssi+php environment utilizing nested includes that drove me to figure out a solution for not only allowing ssi and php to live together (a separate but intimately related story),

*but also allows placing any internal link using a single anchor syntax onto any page on the site (i.e. any nested directories I can use the same anchor) and have the server resolve them without undue load, without fussing over manually having to deal with relative pathways.

This is relevant to this project due to the site using nested ssi (and now php) includes.

Anyway, #1 is the main thing to see there that may benefit others ;^)
TwoHawks