Difference between revisions of "Projects/Usability/HIG/Wording"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(new content)
 
(Guidelines: Updated to integrate wording guidelines from VDG typography guideline (moved here).)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Delete, Move to Trash, Remove, and Uninstall ==
+
__NOTOC__
  
When a file or object is completely removed from the system, use '''Delete''' .
+
== Purpose ==
 +
Every word displayed in an application is part of a conversation with users. This conversation is an opportunity to provide clarity and to help people feel comfortable in the system.
  
When a file or object can be recovered, use '''Move to Trash''' for files and '''Remove''' for list objects etc.
+
== Guidelines ==
 +
* Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.
 +
* Put the most important thing first.
 +
* Short words, active verbs and common nouns.
 +
* Avoid [[Projects/Usability/HIG/Contractions|contractions]] such as ''Don't'' and ''Won't'' etc.
 +
* Avoid abbreviations, acronyms, and tech-babble.
 +
* Use a tone that’s informal and friendly, but not too informal; avoid popular, but transient, words and phrases.
 +
* Keep information short and consistent; avoid redundancy or unnecessary words. e.g. Do not repeat the dialog title in the dialog text.
 +
* Don't abuse [[Projects/Usability/HIG/Capitalization|capitalization]] because it draws people’s attention.
 +
* For date and time information, consider that your app may potentially be used for several years; do not use immutable date references like ''this year'' unless it is algorithmically determined.
 +
* Follow system-wide wording conventions for basic functions to keep wording consistent.
  
When a file or object can be removed and was originally installed, use '''Uninstall'''.
+
[[Category:Usability]][[Category: Presentation]]
 
+
== Settings, Options, and Properties ==
+
 
+
Use '''Settings''' for a configuration dialog which allows you to set specific properties or functionality. This usually applies to application configuration tools. For example, Konqueror Settings.
+
+
Use '''Options''' for a configuration dialog which provide. This usually applies to object configuration tools.
+
+
Use '''Properties''' for a list of metadata or details that are associated with a particular object which cannot be edited or interacted with in any way. For example, file "properties" dialog in Dolphin.
+

Latest revision as of 21:29, 28 March 2014


[edit] Purpose

Every word displayed in an application is part of a conversation with users. This conversation is an opportunity to provide clarity and to help people feel comfortable in the system.

[edit] Guidelines

  • Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.
  • Put the most important thing first.
  • Short words, active verbs and common nouns.
  • Avoid contractions such as Don't and Won't etc.
  • Avoid abbreviations, acronyms, and tech-babble.
  • Use a tone that’s informal and friendly, but not too informal; avoid popular, but transient, words and phrases.
  • Keep information short and consistent; avoid redundancy or unnecessary words. e.g. Do not repeat the dialog title in the dialog text.
  • Don't abuse capitalization because it draws people’s attention.
  • For date and time information, consider that your app may potentially be used for several years; do not use immutable date references like this year unless it is algorithmically determined.
  • Follow system-wide wording conventions for basic functions to keep wording consistent.

This page was last modified on 28 March 2014, at 21:29. This page has been accessed 2,966 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal