Repository navigation
Reading: January reader profile prototype - #2748
Merged
Merged
Conversation
Contributor
Author
|
selfie |
This was referenced Jan 23, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Who is this PR for?
MTSS leaders, reading specialists, instructional coaches
What problem does this PR fix?
This is a prototype of the iteration called the "January reader profile." More design info available in the "12/13 reading sketches" internal doc.
What does this PR do?
This adds a new UI section on the reading tab. It re-purposes existing endpoints, so other than the new
enable_reader_profile_januarylabel, this is a JS-only change.For local dev and testing, this uses a grid of different test cases, with students of different grades at different time periods. The data generation isn't super realistic yet beyond the shape; that'll be something to improve iteratively after this frame is out and validated.
This also doesn't yet do any real visualization of the data, since a key aspect of the design was the hypothesis of how de-emphasizing this might shape problem solving conversations. That'll be another pass.
Screenshot (if adding a client-side feature)
story: example
story: click on an element
(images aren't loaded in the story)

story: examples across grades
story: full grid of (grades, time)
product: placement within page
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?