Showcase enables you to pre-curate your content into an interactive 'app' that can be navigated on the touch screen. Such apps are usually configured and supplied to you, however extending the setup and managing the content is simple and flexible.
This guide covers content management for Showcase apps that are file system based. This means that the organisation of content in the app folder structure dictates how content is presented in the app.
This guide covers some of the basics of the folder structure to control how the tab bar is structured, referring to a sample app folder called Showcase-Example.capp. This sample can be supplied to you if you'd like to play around with the supported layouts.
Workspaces Folder
A Showcase app is configured to load all content from a folder structure, called the workspaces folder. Each sub-folder in this structure creates a tab in the tab navigation bar at the bottom of the screen.
You can drop your content into these folders, as well as configure the tab to display content in a particular way. For example, the screenshot below shows a tab with a single web site in fullscreen.
The Showcase-Example workspaces folder has a number of sub folders showing different ways of displaying content.
The Fullscreen Website tab and Layouts section use several of the standard content layouts (see Showcase tab layout options - you can put files in a layout folder to set how it should be displayed), while the Custom Layout section demonstrates use of an XML layout file for custom behaviour.
If you do not put content in a layout subfolder (e.g. called _fullscreen, _carousel etc) any files found in that folder (not beginning with a '_') will be displayed scattered in the middle of the screen.
Example Workspaces Structure
Showcase-Example.capp/workspaces:
01_Fullscreen Website
02_Layouts
03_Custom Layout
09_Email Tab
99_Splash
_background.jpg (The Default Background Image for the app)
Showcase-Example.capp/workspaces/01_Fullscreen Website:
_fullscreen/ (first item of this folder will be set to fill the screen)
Showcase-Example.capp/workspaces/01_Fullscreen Website/_fullscreen:
website.web.txt (A weblink text file with the site url)
Showcase-Example.capp/workspaces/02_Layouts:
<Folders>... (See next section for sample layouts)
Showcase-Example.capp/workspaces/03_Custom Layout:
_layout.hbs (the cutome layout)
<files>... (e.g. introduction.pdf, <images>.jpg)
Showcase-Example.capp/workspaces/09_Email Tab:
<empty> (This is a special tab for the email popup, may contain a _empty.txt)
Showcase-Example.capp/workspaces/99_Splash:
_splash/ (First file will be used for the splash screen)
The following table describes the role of the special files that may be added to the tab folders.
| Filename | Description | Required? |
| _background.* | Background image or video for the tab (e.g. a PNG, JPG or MP4 file). Overrides the default background image when selecting the tab. | Optional |
| _datawall.* | Image or other file type (e.g. video) that should be automatically 'flicked' to connected Viewer screens when selecting the tab. | Optional |
| _label.txt | A text label for tab button, overriding the label automatically derived from the folder name. | Optional |
| _layout.xml (or anything in the folder with .xml extension) | XML file describing which objects to display on the tab (for files/resources that haven't been laid out automatically). See the XML layout guide for more information. | Optional |
| _layout.hbs (or anything in the folder with .hbs extension) | Handlebars file describing which objects to display on the tab (for files/resources that haven't been laid out automatically). See the Handlebars layout guide for more information. | Optional |
You can also add sub-folders to create sub-tabs in a nested hierarchy on the tab bar.
Tab Ordering and Hidden Tabs
The ordering of tabs is based on the name of each folder. You can use a number prefix on each folder to easily control the order of the tabs. If you are using automatic labels, derived from the folder name, the number prefix will be ignored. For example, naming a folder 1_Home will result in the tab being labelled Home.
You can also prevent a tab from appearing in the navigation bar by giving it a prefix of 99_ - for example '99_Hidden Menu'. This is useful if your app defaults to a specific tab, or has custom buttons, so that you can switch to that tab without it being displayed in the tab bar.
Content Layouts on Tabs
Now that we've covered the basics of the folder structure, please refer to the tab layouts guide for details on how to control positioning of content.