[Remove Vuetify from Studio] Buttons in Questions

[MisRob]

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

• Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
• Confirm that you’ve read the guidelines in your comment.

Sub-issue of #5060.

Complexity: Low

Summary

Migrate the following buttons in Edit resource > Questions tab from Vuetify to Kolibri Design System.

VBtn is currently used to show them. To remove this Vuetify dependency, replace the usage of VBtn in this specific location with the most suitable KDS button or link components. Ensure that all buttons work exactly as before. Do not refactor any other areas.

How to get there

• Login as a@a.com with password a
• Go to Channels > Published Channel
• Select Sample exercise
• Click Edit
• Go to Questions tab

Guidance

• Find detailed guidance with many code examples in KDS documentation
• Read the project for more useful references

Out of Scope

• Do not refactor any other areas of the codebase

Expected UI/UX changes

• Minor visual differences naturally stemming from the use of KDS

Acceptance criteria

General

• The specification above is followed.
• Except for "Expected UI/UX changes," there are no functional or visual differences in user experience.
• All user interactions are manually tested with no regressions.
• Pull request includes screenshots.

a11y and i18n

See the project's "Guidance" for useful references.

• Implementation meets a11y standards
• All components are LTR and RTL compliant (preview with pnpm run devserver since :hot doesn't render RTL properly)
• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. user-generated text)
• Mobile experience is reasonable

Unit tests

• If there is a unit test suite already, it is meaningfully updated (even if tests don't fail)
• If there is no unit test suite, a new one is created. Do not use obsolete @vue/test-utils approach. Instead, use @testing-library/vue (Vue Testing Library).

[Prashant-thakur77]

@marcellamaki Iwould like to work on this issue.

[marcellamaki]

Hi @Prashant-thakur77 thanks for your interest. I'll assign you.