Reading: Update grouping page to include computations, cut points, and click to see more #2363
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?
K5 reading teams
What problem does this PR fix?
Builds forward on the work in #2360, enabling K5 reading teams to make use of benchmark reading data and data from other sources within A&R and instructional planning meetings.
What does this PR do?
Makes some improvements in navigation, but focuses mostly on the core grouping UX. This includes revising styling, adding in computations for reading groups, and enabling the "click to see more inline" interaction for an individual student.
One difference from previous mocks is that the "mentioned in notes" bit is cut here since it involves pushing that keyword-based search to the server to limit the notes shared across the whole team.
Note that most of this code is not generalized to all teams, grades, or reading benchmark assessments yet; the intention is still to pilot this tomorrow and then decide on the next iteration forward (either further revisions, or work towards generalizing for next pilot teams).
Screenshot (if adding a client-side feature)
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?