PC software

This style guide contains directives for digital platforms such as PC software and applications for mobile end devices. The specifications in this document are deliberately general in order to cover different applications and technologies. They have to be interpreted for each specific platform.


Designation of user interface elements

The glossary lists several alternative terms and defines the Phoenix Contact standard.

Designations for UI elements are primarily oriented to the HTML standard. Exceptions are:

  • In some cases, designations have to be adapted to ensure clarity and so that descriptive names can be used.
    • Example: The radio type input element becomes RadioButton.
    • Example: The text type input element becomes TextInput.
  • Individual elements are named in accordance with internal directives, as they exist in the respective development projects.
    • Example: the Switch element is standard in mobile runtime environments. An HTML element does not exist for this.

In this document, symbolic names contain uppercase letters within a name (known as CamelCase) to improve readability. If your coding directives specify other conventions, you must convert the name accordingly. If possible, however, the name itself should not be changed, just the syntax.


Figures and illustrations

In some cases, so-called wireframes are also used in this document to visualize UI elements. If it is helpful, these can be replaced by screenshots as soon as the material is available. In many cases, a wireframe is sufficient for explaining a situation.

With wireframes, please note:

  • The appearance of a wireframe is deliberately different to the final design.
  • Icons in wireframes are placeholders and not taken from the Phoenix Contact catalog.

Objectives and scope

The specifications ensure that all applications from Phoenix Contact are based on the same interaction principles and feature a uniform look and feel. This yields several advantages:

  • A uniform interface design makes the Phoenix Contact brand more recognizable. It strengthens the brand and promotes the positive perception of the applications.
  • Uniform interaction principles make Phoenix Contact applications recognizable. They make it easier for users to get to grips with new applications.
  • This style guide is based on established standards. This makes it easier to create user-friendly applications and therefore a positive experience of Phoenix Contact products.
  • The specifications cover functionality, orientation, and visual appearance. This reduces the need for customized solutions and therefore the overall workload.

Target groups

These specifications are aimed at the following target groups:

  • Interaction and screen designers who design new applications for Phoenix Contact
  • Developers who create, modify or maintain applications for Phoenix Contact
  • Technical publishers who write text for user interfaces or describe Phoenix Contact applications
  • Translators of user interfaces
  • Those interested in interaction and design rules for Phoenix Contact applications

GmbH & Co. KG

Flachsmarktstraße 8
32825 Blomberg, Germany
+49 5235 3-00