Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

UI establish style guide / component-driven devel process

Description

To kick off post-3.0.0 work, we want the UI process to have a "slow down" moment, re-establish code reviews where Nick has an opportunity to be in the reviews, and further establish use of the style guide. We want the UI Style Guide to be the place for building components first before they are used elsewhere; we want the team to have a process of updating the Style Guide when they change components, and re-using the same components consistently throughout the application.

Acceptance Criteria:

  • UI Team Workshop or meeting to discuss these topics; possibly share back with the larger team anything we need to know

QAlity Plus - Test Management

Checklists

Activity

Nick Reid 
November 30, 2017 at 4:44 PM

I'm marking this ticket as dead, since its a little large and I'm not sure we are in the same place currently....

Brandon Bowersox-Johnson 
June 15, 2017 at 11:15 PM

I believe we have not yet achieved this. We need to talk and determine if switching our Style Guide generator tool is a blocker for adopting component-based development and using our style guide more OR whether we can promote and improve these practices even with our current tool.

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Components

Priority

Time Assistant

Created March 1, 2017 at 10:52 PM
Updated February 8, 2023 at 1:29 PM
Resolved November 30, 2017 at 4:44 PM