Overall structure
Open, HighPublic

Description

We need to restructure the HIG for its new format.

One of the reasons for that is to combine the Kirigami HIG with the classig HIG. To do this, we need to decide on the order and how to subdivision the HIG topics.

As an example the Material Guidelines sometimes distinguish between mobile and desktop usage on a granular level but do not on a higher level. Also they do not distinguish between apps and shell.

In general some abstract goals are for this new structure:

  • vision and design principles hold true for any toolkit and platform,
  • make it easy for the developer to find the right guideline pages for his project,
  • do no divide platforms unnecessarily but reuse design patterns on mobile and desktop, with and without touch and so on as much as possible.
romangg created this task.Mar 5 2018, 9:33 AM
romangg triaged this task as High priority.
fabianr added a subscriber: fabianr.Apr 9 2018, 9:20 AM

Maybe we should add a section about system integration, with information about how taskbar, launcher, system tray, ... should be used and what not to do.

Maybe we should add a section about system integration, with information about how taskbar, launcher, system tray, ... should be used and what not to do.

I created a list of common (visual) components a while ago that may help with this. I tried to define what visual elements are usually available on any device, with a description of its intended functionality. This description is a bit abstract but I also provide more concrete descriptions of what exactly is used for each component on a specific device type.

For example, the Application Launcher is described as a component where you can find an overview of your installed applications and start one. For a desktop, this is explained as being the Kickoff Menu in the taskbar.