Projects/Usability: Difference between revisions

From KDE TechBase
(add link to meetings)
mNo edit summary
 
(15 intermediate revisions by 9 users not shown)
Line 1: Line 1:
__NOTOC__
{{note|This page contains content from the year 2009. The KDE usability team's main action currently takes place on the mailing list mailto:[email protected]}}
{{note|The [[Projects/Usability/HIG |  KDE Human Interface Guidelines (HIG)]] are an up-to-date reference. A related project that deals with usability is the [https://community.kde.org/KDE_Visual_Design_Group KDE Visual Design Group]. }}
The KDE Usability Project aims to improve KDE usability and user experience through:
The KDE Usability Project aims to improve KDE usability and user experience through:


Line 4: Line 10:
* Conducting usability activities to help gather feedback from users
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces
* Working with projects and help design usable user interfaces
Learn more at the [http://usability.kde.org KDE Usability Project] website.


[[Projects/Usability/Meetings | KDE Usability Project Meetings]]
[[Projects/Usability/Meetings | KDE Usability Project Meetings]]
Line 11: Line 15:
= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =
= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =


If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page.  We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.
If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [[/HIG_Questions | HIG Questions]] page.   
The results of HIG compliance tests from Google Code-in can be found on the [[/CodeInResults | Code-in Results ]] page.


= User Research Profiles =  
= User Research Profiles =  
Line 27: Line 32:
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]
* [[Projects/Plasma/PURP|Plasma]]
* [[Projects/Amarok/MediaDevice_Sync_URP|Amarok: Media Device Synchronization]]
=== Plasma 5 Projects ===
* [[/Plasma5/System_Settings | System Settings]]


= Case Studies and Reports =  
= Case Studies and Reports =  
Line 35: Line 44:


[[Category:Usability]]
[[Category:Usability]]
= Unified experience =
[[/consistancy watchlist/]]

Latest revision as of 22:08, 2 December 2014


Note
This page contains content from the year 2009. The KDE usability team's main action currently takes place on the mailing list mailto:[email protected]


Note
The KDE Human Interface Guidelines (HIG) are an up-to-date reference. A related project that deals with usability is the KDE Visual Design Group.


The KDE Usability Project aims to improve KDE usability and user experience through:

  • Educating developers about usability practices
  • Conducting usability activities to help gather feedback from users
  • Working with projects and help design usable user interfaces

KDE Usability Project Meetings

KDE4 Human Interface Guidelines

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the HIG Questions page. The results of HIG compliance tests from Google Code-in can be found on the Code-in Results page.

User Research Profiles

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

Project User Research Template

Projects

These projects have been called to work on their user research profiles:

Plasma 5 Projects

Case Studies and Reports

Case Studies

Reports


Unified experience

consistancy watchlist