Oxwall Interface Design

All about developing user interfaces for Oxwall.

According to Oxwall design principles user interfaces are implemented in plugins (not themes) that is why this is the document for plugin developers rather than theme designers. You should build your functionality consistent with established Oxwall interface paradigms. This will result in integrated user experience which is ultimately our goal.

A standalone piece of content, including but not limited to widgets, may be displayed using boxes. Box as design element.

Box has optional parts such as:

Usually has title of widget or content and icon for better understanding.

Shows different display variants of content.

Shows actions for the content.

Used for main form actions, standalone actions and should be prominently displayed with unambiguous captions. Has characteristically big size.

Used for group actions upon one object (or a group of those). Color coding may apply to emphasize action meaning. Has characteristically modest size.

If used as a button often appears on mouse over. Can be used in groups. Has characteristically small size.

The form should have main action button (submit) be right-aligned and implemented as the standard button. Any secondary actions (like “Cancel”) shouldn't be implemented using standard button. A link or a smaller button should be used instead.

If you see any type of confirmation in Oxwall it will be Facebox with confirmation text and one button. There shouldn't be “Cancel” button or link to prevent clicking accidental clicking. It should be enough to click “X” or hitting “Esc” to cancel the action.

Use this if you need to sort some content by several options. The first one should be default. You should make options labels as short as possible and preferrably not to have more than 4-5 options to prevent them from dividing into 2 strings. Sort control should take the whole content width and be placed right before the content it sorts.