KDE Visual Design Group/KirigamiHIG: Difference between revisions
Added link to apidocs |
|||
Line 30: | Line 30: | ||
== Implementation == | == Implementation == | ||
For technical documentation, see the [https://api.kde.org | For technical documentation, see the [https://api.kde.org/kirigami/html/index.html API documentation] |
Revision as of 09:12, 18 March 2017
Kirigami Human Interface Guidelines
Welcome to the Kirigami Human Interface Guidelines (HIG)! The goal of this document is to help anybody who designs user interfaces for mobile or convergent mobile/desktop applications which will be implemented using the Kirigami Components.
They help you to make optimal use of the Kirigami Components, as they reflect the design ideas behind the components. If you have any questions, please contact the KDE VDG (vdesign [at] kde [dot] org)
These guidelines are for Kirigami-specific aspects of user interface design. For general recommendations on design concepts, see the concept page in the general KDE HIG. The Kirigami HIG are separated in three parts: Design Principles, UI Patterns and a Styleguide for KDE Applications.
Design Principles
These are the basic principles guiding Kirigami design:
- When creating convergent UIs, optimize the UI separately for each device class
- Optimize your application for use with one hand
- Make as much space available for the content as possible
- Allow for a clear and predictable navigation
UI Patterns
Here you find patterns for solving specific design problems with Kirigami Components:
- Navigation Patterns - Patterns for navigating through content or between different "Screens" of an application
- Command Patterns - Patterns for executing commands
Styleguide
This guide helps to create applications in line with the KDE user interface style
- Colors - Guidelines for use of color, incloding the Breeze color palette
- Icons - Guidelines for icon usage and design
- Typography - Guidelines for font usage and typography
- Animations - Guidelines for design and use of animations
- Text Guidelines for the written, language-based elements of the interface. Includes guidelines on wording, capitalization and localization.
Implementation
For technical documentation, see the API documentation