Projects/Usability/HIG/Wording: Difference between revisions

    From KDE TechBase
    < Projects‎ | Usability‎ | HIG
    Line 6: Line 6:
    == Guidelines ==
    == Guidelines ==
    * Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.  
    * Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.  
    * Avoid contractions such as ''Don't'' and ''Won't'' etc.
    * Avoid [[Projects/Usability/HIG/Contractions|contractions]] such as ''Don't'' and ''Won't'' etc.
    * Avoid abbreviations, acronyms, and tech-babble.
    * Avoid abbreviations, acronyms, and tech-babble.
    * Use a tone that’s informal and friendly, but not too informal.
    * Use a tone that’s informal and friendly, but not too informal.

    Revision as of 12:21, 9 January 2014


    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.

    Guidelines

    • Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.
    • 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.
    • Keep information short and consistent; avoid redundancy or unnecessary words.
    • Don't abuse capitalization because it draws people’s attention.
    • In respect to chronological information consider that your app is potentially used for decades; don't use fix dates like this year.
    • Follow system-wide conventions for basic functions to keep wording consistent.