Difference between revisions of "User Interface / User Experience Process"

From PKP Wiki
Jump to: navigation, search
(Information)
 
Line 17: Line 17:
 
== Information ==
 
== Information ==
  
* [http://pkp.sfu.ca/wiki/index.php?title=OMP_UI/UX OMP UI/UX]
+
* [[OMP UI/UX]]
  
* [http://pkp.sfu.ca/wiki/index.php?title=OJS_UI/UX OJS UI/UX]
+
* [[OJS UI/UX]]
  
* PKPWAL_UI/UX PKP WAL UI/UX
+
* [[PKPWAL UI/UX]]
  
 
* OCS UI/UX (deferred until after OJS/OMP work)
 
* OCS UI/UX (deferred until after OJS/OMP work)
  
 
* OHS UI/UX (deferred until after OJS/OMP work)
 
* OHS UI/UX (deferred until after OJS/OMP work)

Latest revision as of 12:24, 8 May 2014

PKP has been developing user interfaces for over a decade, but is now implementing a more formal process that will involve greater user involvement. This page is the landing page for information on that evolving process, including an archive of past documents and discussions. Please make use of the "discussion" pages on this wiki to track concepts and decisions throughout the process.

Key Issues

Throughout the UI/UX process, there are a few key issues that need to be kept in mind:

  • Multilingual: Any UI changes need to work in a multilingual environment.
  • Workflow: the journal setup, editorial, review, etc. processes.
  • Themeable: PKP software has been designed to allow users to adopt their own "look and feel", and any UI changes need to accommodate this.
  • Common library: PKP software now makes use of an extensive web application library, meaning that changes in many UI elements for one application (i.e., OMP) will also impact all other applications (i.e., OJS, OCS, OHS).
  • Others?

Contacts

Information

  • OCS UI/UX (deferred until after OJS/OMP work)
  • OHS UI/UX (deferred until after OJS/OMP work)