-
Notifications
You must be signed in to change notification settings - Fork 5
Redesign: concept finder improvements #1463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redesign: concept finder improvements #1463
Conversation
axlewin
commented
May 16, 2025
- Add stage filtering to main concept finder
- Don’t automatically deselect subject when fields are deselected (concept finder behaviour should match QF behaviour here)
- Move “these concepts have been filtered…” message out of sidebar
On subject-specific question finders and concept listings, move the "browse all" button out of the sidebar to the top of the page. Remove this option entirely for practice tests because we don't want to link to the main practice tests listing anywhere.
On the generic concept finder: if a subject and fields are selected, and the fields are then deselected, reselect the subject. This now matches the behaviour of the question finder.
Selecting other stages shouldn't change the stage count, but selecting subjects/topics should.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
On the generic concept finder: fixes and neatens the logic for calculating how many concepts match a stage filter by reusing the logic used for topic counts.
…-react-app into redesign/qf-concepts-improvements
Resolves an issue where selecting a stage with no results collapsed the field menu and made it impossible to deselect fields.
This also moves the sidebar up and is consistent with the question finder.
This is now consistent with the concepts/practice tests sidebars and the designs.
…-react-app into redesign/qf-concepts-improvements
@barna-isaac Thanks for looking at this! The latest batch of commits should address all of your comments, plus a few other inconsistencies I found; there's justification for some choices in the commit messages, but let me know if you have any more questions/suggestions. |
on my machine, it didnt work on Concepts: the button still used up three lines. it was fine on the QuestionFinder but I wanted to be consistent across the two pages. Even if I got it to work on my machine's particular settings, using fixed widths, I don't think it would have worked reliable across different font sizes.
@jacbn , can you please look at this? I've been trying to get these alginments right, but I just hate how unevenly and how much white space we waste. Does "Search and Filter" really need these huge margins? I'd be happiest just removing them, but this is what it looks like on every other page too, and I don't want to introduce inconsistencies. ![]() ![]() |
@barna-isaac : Whilst I agree the inline style wasn't the ideal solution, I'm not sure that this is either. It still looks strange on certain screen widths, just differently: |
@axlewin, do you mean it's looking weird because the text is now three lines? Maybe we keep encountering these issues because the button text is just too long? Maybe we could just change the button text so it's to just "All questions" and "All concepts"? |
This comment was marked as resolved.
This comment was marked as resolved.
Yeah - compared to before, where this was 2 lines of text & 2 lines for the button. I'm not sure it makes a big difference though, if you prefer it this way. I'm still not sure I understand your changes though. Does the |
@axlewin: no, I just put the |
However, I think this is a valid issue: if a selected filter becomes empty, it remains applied but disappears from the screen. This leads to invalid screens, where "Physics" is partially selected but doesn't actually show any selected descendants, or the final screen of the attached recording, where it looks like only the Biology filter is selected but we don't show any results. I think the easiest solution would be if we always showed empty filters. Screen.Recording.2025-05-23.at.10.55.45.mov |
It's not the neatest solution, but we could just remove the hardcoded style and then change the classes on the outermost This at least stops either element wrapping to 3 lines, and avoids complicating the DOM by adding another wrapper There are a handful of screen sizes where it will look strange either way though, so we can leave it as-is if you prefer. |
As discussed, always showing empty stage filters isn't ideal because it leads to cases where you can't deselect a field (try selecting physics > thermal > year 7 & 8). We could show empty field filters too, but this might be confusing for students (e.g. if they've selected year 7 & 8, and calculus is showing up as an option). I also worry that when only published content is shown, this problem would be worse, because there would be more stage/field combinations with no results. My proposal here is to always show selected stage filters, even if there are no results. From a quick test this seems to avoid any cases where users can get 'stuck' and unable to deselect a selected filter. It's worth noting that this is different from the implementation discussed on (As always, please see if you can find any more cases that still don't work!) |
@axlewin I like the idea of always showing selected stage filters, and propose that we extend it to always show selected field filters as well. |
I'm not concerned about the whitespace issues you mentioned (as you said, the spacing matches other pages). Up to you if you'd like to address those before merging. |