Create a custom home page
What is an custom home page ?
When building a application you got a default home page.
Example (Northwind application home page) :
Fortunately it is possible to customize this home page by defining your own UI view with a specific template.
Example (Neos Studio application home page) :
How to create an custom home page
Step 1: Creates a UI view with a template. The template of the custom home page UI view must contains a frame container with a specified identifier.
<frames-container container-id="HomePageContainer" />
Step 2: Specifies its name with the frame container identifier in the cluster configuration file.
MainUIViewName: HomePageUI
MainFramesContainerId: HomePageContainer
Using a single ViewContainer instead of tabs
If the application does not need FramesContainer's tabs (a classic, single-view application), the custom home page template can use a view-container instead:
<view-container container-id="MainView" />
MainUIViewName: HomePageUI
MainViewContainerId: MainView
Navigation still works the same way (menu items, NavigationOptions, URL and browser back/forward), but only one view is ever displayed at a time, with no tab strip.
Protecting unsaved changes when the view is replaced
With FramesContainer, navigating away from a tab does not lose anything: the tab simply stays open in the background. A view-container has only one slot, so replacing its content discards the previous view outright unless you opt in to the protect-unsaved-changes attribute:
<view-container container-id="MainView" protect-unsaved-changes="true" />
When enabled, replacing the displayed view goes through the same Closing/HasChanges confirmation a tab close already triggers, instead of silently discarding pending edits.
This defaults to false on every view-container (including the one used by MainViewContainerId) for backward compatibility: view-container already existed before this attribute, and any cluster using it today expects the current "always replace silently" behavior. Turning the guard on unconditionally would have changed that behavior for existing usages without their consent. Set it explicitly to true wherever the container can display an editable view.