Skip to content
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.

Sign up for GitHub

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

Jump to bottom

💻 Remove Parsons #5924

Open
jpelay opened this issue Nov 8, 2024 · 12 comments
Open

💻 Remove Parsons #5924

jpelay opened this issue Nov 8, 2024 · 12 comments
Assignees
@boryanagoncharenko @jpelay
Labels
frontend Issue with the web interface to_be_deleted

Comments

@jpelay
Copy link
Member

jpelay commented Nov 8, 2024

Commented by Marleen:

In the parsons problem it's not really clear that you can do 2 exercises and that you have to click the 2. (Same as the old design though).
@jpelay jpelay added the frontend Issue with the web interface label Nov 8, 2024
@jpelay jpelay mentioned this issue Nov 8, 2024
Merged
11 tasks
@AnneliesVlaar
Copy link
Collaborator

I think the easiest solution would be to separate the puzzles in different tabs/exercises. Puzzle 1; Puzzle 2

@Felienne
Copy link
Member

Parsons should be removed, they are not well integrated in the trajectory and not well-designed (very different from the quiz, for example) The idea of parsons might as well be done with paper sheets.

@Felienne Felienne changed the title 💻 Make it clearer that there are two parsons exercises 💻 Remove Parsons Nov 30, 2024
mergify bot pushed a commit that referenced this issue Dec 2, 2024
@jpelay @boryanagoncharenko
💻 Improvements to redesign of adventure page (#5926)
e6fe962 
- [x] The clear button is gonna create some very angry students who accidentally removed all their work. Solutions: Can we have an 'are you sure you want to remove all your code' pop-up? An 'undo' button would work too, or ctrl+Z? Or, last option: Do we even need the clear button? How many times does a student want to clear the whole field, and even if they do, it's not much effort to do so without having a clear button...?

- [ ] We need Dutch translations for some new buttons. => Maybe someone can add it here?  Or in Weblate?

- [ ] The button says 'show editor' while I think we have been using the term 'input screen'. I think editor might be better though, so maybe it doesn't need to change? => @Felienne I dont have preferences either way, do you agree?


- [x] There are nearly no margins at the sides (maybe because I don't have a very big screen) which makes it look a bit crowded. Can we add some margins? Same goes for the text of the adventures, I think it would look better if tehre was some white space on the sides of the text field.

- [x] I don't really like the underling of 'level 1 - introduction', I think it might look better without the underlining, but that might just be my taste. The underlining also makes it feel clickable, which it is not. => I made it a little thicker, but I'm keeping it to solve another point further down.

- [ ] I really love the 'see more adventures' menu! I do think it's slightly counter intuitive that the button is on the right, while the menu appears on the left. => I don't think it's that counterintuitive due to us reading from left to right, in the case of languages that read from right to left, it appears on that side. 

- [ ] Extra idea for the 'see more adventures' menu: Would it be possible to show in the menu which of the adventures you have completed? Like with a little tickmark or something behind the adventure? => This makes a lot of sense!! @Felienne I think we'd want here the tickmarks we are now using in the tabs? Shall we also add a tickmark next to the title? 

- [ ] (low priority) why is the 'e' in our font a smaller size? It looks kind of strange? => Haha, no way for me to fix this sorry! Maybe I can change the font!

- [x] (low priority) Before you could see if the adventure was just another adventure, or if you were learning a new command because of the tabs colours. We don't really have that anymore, exept for in the menu, but kids probably won't use that much. Maybe we can think of another way to show the students that they will learn a new command in this adventure. => This is why I didn't remove the underline, you can see now the type of adventure in the different colors of the underlining.

- [ ] In the parsons problem it's not really clear that you can do 2 exercises and that you have to click the 2. (Same as the old design though). => Opened #5924

- [ ] BUG: If you finish the level 1 quiz and click 'go to level 2' you'll be sent to the quiz of level 2, instead of the introduction. => Opened #5923


**How to test**

In regards of the margins, you can set the size of the screen in the responsive view mode to: 1077x524


Co-Authored-By: boryanagoncharenko <[email protected]>
@boryanagoncharenko
Copy link
Collaborator

The comment for this issue left from the meeting on 6 Dec is to check how often parsons are used.

Based on my research, users press the Run code button on a parson puzzle 190 times per day on average. This has been measured on the amount of calls to the /store_parsons_order endpoint which is called whenever the user attempts to execute a parson program.

@AnneliesVlaar @MarleenGilsing please let me know whether you need further information on the usage or you would like me to proceed with deleting parsons.

@MarleenGilsing
Copy link
Collaborator

190 seems like a big number at first, but i guess if we compare it to normal adventures it isn't much, right? Especially if 190 clicks is all the 34 parsons puzzles combined? And one child might click multiple times as well?

@boryanagoncharenko
Copy link
Collaborator

On average, users click the Run code button for non-parson programs 5820 times a day and only 190 times for parson programs.

It is expected that one user clicks on the Run code button multiple times when solving a problem regardless if it is a parson or not. I am afraid it is hard to provide a good estimate on the amount of unique users and the specifics of their interactions. To get a grasp, I examined a smaller subset of the logs and noticed that:

  • on weekdays we usually have about 50 different users who use parsons. On weekends the amount of users using parsons goes down to 10.
  • about 3/4 of the parson users click the Run code button up to 5 times. The rest of the users (1/4) click it 6 or more times, sometimes going up to 100 times in their active session.

Let me know if you need further information.

@MarleenGilsing
Copy link
Collaborator

Alright, seems like they are not that popular. The layout definitely needs an update if we would keep them, so maybe for now we can just remove them and think of ways to ingerate them into the workbooks.

@boryanagoncharenko
Copy link
Collaborator

Thanks! Just to ensure that we are on the same page about the scope of the current issue. With this task we want to:

  • remove parson puzzles from the the website
  • remove all parson-related endpoints from the backend
  • remove all parson content, including the parsons component in Weblate

Could you confirm the above is correct? If you need further information to confirm that this is the scope, please ping me on Discord.

@MarleenGilsing
Copy link
Collaborator

Yes, agree. @AnneliesVlaar Do you agree too?

I think we should also:

  • Check the teacher manual for mentioning of parsons puzzles and change content if nessecary.

I could do this too.

@AnneliesVlaar
Copy link
Collaborator

Let's indeed remove the Parsons problems. We want to schedule the removal at the same time as the release of the new adventure design "Improvements to redesign of adventure page #5926"

Then indeed everything related to Parsons (website, backend, Weblate) can be removed.

@MarleenGilsing will move the content of Parsons to the workbooks. So it will reappear.

@boryanagoncharenko
Copy link
Collaborator

Let's indeed remove the Parsons problems. We want to schedule the removal at the same time as the release of the new adventure design "Improvements to redesign of adventure page #5926"

Then indeed everything related to Parsons (website, backend, Weblate) can be removed.

@MarleenGilsing will move the content of Parsons to the workbooks. So it will reappear.

The changes in "Improvements to redesign of adventure page #5926" were deployed to hedy.org on Dec 6 at 9:49 PM.
Why should removing parsons be released with the changes of #5926? Are there issues that you foresee?

@MarleenGilsing please let me know when you are done with the migration of content from parsons to workbooks, so that I can combine our changes.

@jpelay
Copy link
Member Author

jpelay commented Dec 13, 2024

The changes in "Improvements to redesign of adventure page #5926" were deployed to hedy.org on Dec 6 at 9:49 PM

I think she means when we finally substitute the old design with the new one.

@AnneliesVlaar
Copy link
Collaborator

The changes in "Improvements to redesign of adventure page #5926" were deployed to hedy.org on Dec 6 at 9:49 PM

I think she means when we finally substitute the old design with the new one.

Yes correct, that's what I tried to say. Thank you @jpelay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@boryanagoncharenko boryanagoncharenko

@jpelay jpelay

Labels
frontend Issue with the web interface to_be_deleted
Projects
Hedy organization board
Status: No status
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Felienne @boryanagoncharenko @jpelay @AnneliesVlaar @MarleenGilsing