Interface Overview

Last modified by Thiago Krieck on 2026/11/18 14:13

Warning
Draft

This page is a draft. The standards on it are proposals still under discussion, so they may change and should not be treated as final yet.

Every XWiki page is built from the same set of regions, and each region has one job. Getting to know them is the best first step: users always know where to look, and you always know where your feature belongs.

io-reference-view-page.png

The regions of a page in view mode: the wiki home page

The regions

Every page should use the same regions for the same purpose:

  • Top bar: Should hold only what every page needs: the logo, search, notifications, the user menu and the button that opens the drawer. Page-specific actions should not go here.
  • Drawer: Should hold wiki-wide navigation and tools, such as Administration, the applications, the page and user indexes and the language picker, grouped under the current wiki and Global.
  • Breadcrumbs: Should show where the page sits in the hierarchy, and nothing else.
  • Title and content menu: Should show the page title and its last change on the left, and the page actions (Edit, Create, More actions) on the right, never inside the content, so that actions are always found in one place. See Menus and dropdowns.
  • Content: Should hold the page itself, or the application sheet that displays it.
  • Panels: Should hold supporting content only, such as navigation on the left and tips or recent changes on the right. Nothing essential should live only in a panel, since panels can be hidden and move below the content on small screens.
  • Content footer: Should hold short page metadata, such as tags, authors and likes.
  • Docextra tabs: Should hold what is attached to the page: comments, annotations, attachments, history and information.
  • Footer: Should hold the license and the version only.
  • Edit mode: Should keep the top bar and breadcrumbs, show the editor in the content region and keep the save actions in the sticky bar at the bottom, so that users don't lose their bearings while editing. See Buttons.
  • Administration: Should use the view layout, with the administration menu on the left of the content. New sections should be added with a XWiki.ConfigurableClass object, not a UIX.

Reference example: any page in view mode, such as the wiki home page. Each region is a labelled landmark, a skip link jumps straight to the content, and most regions can be extended through a UIX point.

Adding to the interface

Most regions can be extended without touching the skin. Each one has a UI extension point (UIX): a named spot that an extension fills by adding a XWiki.UIExtensionClass object to a page, with the point's id in its extensionPointId field. To add something to a region, developers should use its UIX point rather than override a template, so that their addition keeps working when the skin changes. To learn how to write one, see the UI Extension Tutorial; Available Extension Points lists every point, not only the main ones below.

The images below show where the main points render. The numbers match the table.

io-uix-page.png

UIX points on a page, with the Edit and More actions menus open

io-uix-drawer.png

UIX points in the drawer

#To addUIX point
1A global item in the top bar, such as search, notifications or the user menuorg.xwiki.platform.topmenu.right
2A drawer entry, under the current wiki (category = local) or under Global (category = global)org.xwiki.plaftorm.drawer
3An editor in the Edit menuorg.xwiki.plaftorm.editactions
4A page action in More actions → Manageorg.xwiki.plaftorm.adminactions
5A page action in More actions → Actionsorg.xwiki.plaftorm.moreoptions
6A way of viewing the page in More actions → Viewersorg.xwiki.platform.template.menu.viewers
7Content between the page header and the content, such as a bannerorg.xwiki.platform.template.content.header.after
8An item in the content footerorg.xwiki.platform.template.contentFooter
9A docextra taborg.xwiki.plaftorm.template.docextra
10An entry in the Applications panelorg.xwiki.platform.panels.Applications
11A panela page with a Panels.PanelClass object (platform.panels), not a UIX
–Scripts or other code that doesn't show anythingorg.xwiki.platform.template.header.after

Notes

  • Several UIX point ids are spelled plaftorm. They are public API, so they should be copied exactly, not corrected.
  • Most top bar, drawer and content menu UIX points are only rendered when their author has admin rights on the wiki.
  • The Edit menu (3) only appears for advanced users; simple users get a single Edit button that opens the default editor.
  • Below 992px the panels stack under the content and the page header stacks title over actions. Each region should be checked at that width.

More

Get Connected