SPIKE: Design Principles

[weiweishi]

Description

This is a spike to define design principles for DI web application development.

Scope

This will currently focus on the DI web application development, with the focus on ERA development. And we will develop the principles, patterns, guidelines in an incremental manner to expand to all DI web applications, and potentially to all library web presence.

Expected Outcome

• [ ] A list of principles (not limited to the following list) that all DI web application should adhere to:

  • [ ] Universal Design and Accessibility
  • [ ] Flexibility in use with choice of device
  • [ ] Clear navigation structure
  • [ ] Proper use of headers/forms/tags
  • [ ] Favicon
  • [ ] Validation of HTML/CSS/JS etc.

• [ ] Evaluation of requirements of WCAG 2.0 Level A and Level AA compliance, identifying the relevant guidelines

  • [ ] Creating a list of recommended design patterns that will satisfy above requirements.

• [ ] Documentation on these principles, guidelines, and patterns on Developer Handbook

• [ ] Automated tools that can be used to incorporate into our development practices.

[weiweishi]

@mbarnett @murny @nnunn @sfbetz @redlibrarian @pbinkley @leahvanderjagt For your review.

@redlibrarian and @nnunn We've discussed to take the opportunity of Jupiter #162 / HN interface rewrite in Hydra-Works to rectify some issues in our development/design process. And one thing we thought would be beneficial is to start developing our design principles that all DI projects and beyond could adhere to. We'd like to build that knowledge with the focus on ERA redevelopment, but expand it incrementally for other DI projects and potentially to the work you do. I wonder what you think about the approach? We are scoping out a spike to start pulling information together, and I wonder if this is something you'd be interested? We will definitely run the outcome by you for your feedback.