Back Office tabs¶
Many elements of the Back Office interface, such as content view, dashboard or system information, are built using tabs.
You can extend existing tab groups with new tabs, or create your own tab groups.
A custom tab can extend one of the following classes:
Ibexa\Contracts\AdminUi\Tab\AbstractTab- base tab.
Ibexa\Contracts\AdminUi\Tab\AbstractControllerBasedTab- embeds the results of a controller action in the tab.
Ibexa\Contracts\AdminUi\Tab\AbstractRouteBasedTab- embeds the results of the selected route, passing applicable parameters.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
For a full example of creating a custom tab, see Add dashboard tab.
You need to register the tab as a service.
Tag it with
ibexa.admin_ui.tab and indicate the group in which it should appear:
1 2 3 4 5 6 7
The group can be one of the existing components, or your own custom tab group.
You can order the tabs by making the tab implement
The order depends on the numerical value returned by the
1 2 3 4
Tabs are displayed according to this value in ascending order.
It is good practice to reserve some distance between these values, for example to stagger them by step of 10. It may come useful if you later need to place something between the existing tabs.
You can also influence tab display (for example, order tabs, remove or modify them) by using the following event listeners:
You can create new tab groups by using the
To create a tab group, register it as a service:
1 2 3 4 5 6 7
Tag the group with
group indicates where the group is rendered.
For a list of possible rendering places, see Injecting custom components.