Our CMS ( Content Management System )
sets aside an area on the server for the application so that
the site can navigate the content of this area using
PHP view controllers. The main help files and content are rendered using the
general content files view controller browse.php
This presents PHP / HTML pages and any media files for view.
The URL indicates where browse looks for the content.
The first URL segment is first used to define which view controller is used to render the page content.
Some application directories are defined as content areas and will be displayed directly using browse.php
If the first URL segment is BOTH a view controller and a content file, such as a help file or a view,
the view controller will take priority.
Content is rendered by a set of view files public_html/biscuits-12y/views browse*.php
To build an audio podcast, all you need to do is collect your mp3 audio files int content directories.
If you are logged on this can be done by uploading. If not, then ftp access.
You can add track list and timed images to appear at certain points, all by uploading the files
when the relevant audio is active and the timer set to the correct time for the timed content.
EG: Upload an image while the timer is set to the time that the image should activate.
Underscore PHP CMS controlling files
Contains HTML to help navigate
Biscuits PHP code for CMS
There are two biscuits view files :
The first parses a content array
( This can be constructed prior to including book-content.php )
Each detail line is displayed using book-page-details.php
We also have a sitemap tool, which is a way of displaying nested lists.
But this does not relate directly to the filesystem and what's actually there.
This method of site navigation is being replaced by a system
that works more directly from the content files on the server's file system