hi,
i've a question about where best to place some non-dynamic theme content, or, frankly, whether it should be considered part of my theme at all ...
i've created a custom frontpage for my theme (page-front.tpl.php).
on that themed fronpage, i've a PictureFlow4 ("PF4", a flash/swf Apple OSX CoverFlow clone, http://www.yaelle.com) object -- serving as a theme/site 'splash' page. i've configured PF4 so when i click on one of the presented PF4 objects, it opens -- still 'on' that themed frontpage -- a Shadowbox ("SB", http://shadowbox-js.com) iFrame with content (html, php, whatever) of my choosing.
the SB's iFrame content is NOT dynamic -- rather, it's some simply sytled HTML (NOT 'fully themed' like the rest of the site content), with two action links: (1) close the SB and return to the splash page, and (2) jump to a node in the drupal site, in a _self target.
so, my question is -- where should the content for those non-dynamic iFrames be placed?
iiuc, options seem to be:
(1) completely outside the Drupal site/theme tree. but, then i'm leaving-then-reentering Drupal-controlled space; not sure that's wise.
(2) as standalone tpl.php pages under my theme dir
(3) as nodes/pages/views/whatever controlled from within Drupal itself
any recommendations as how best to handle this scenario? comments are appreciated.
thanks!
Comments
[solved] where to create static content ...
an approach that works nicely, e.g.,
(1) create a new node type, 'test_panel' using CCK
(2) set up an pathauto "automated alias setting"
Pattern for all Test Panel paths:
'test_panel/[title-raw]'
(3) add the drupal6 snippet @
"Different page templates depending on URL aliases"
http://drupal.org/node/139766
to theme's template.php
(4) create & theme page-test_panel.tpl.php
(5) in SB, simply load http://.../test_panel/[title-raw] as the target page