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.

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

Clearer faculty warning messages #676

Merged
merged 2 commits into from
Jun 18, 2024
Merged

Clearer faculty warning messages #676

merged 2 commits into from
Jun 18, 2024

Conversation

tymees
Copy link
Member

@tymees tymees commented Jun 12, 2024

This PR changes the faculty-warning texts to be more honest and nuanced. While the hotfix I deployed today should make this less important, I still think this changer is needed.

The faculty-known message variant is, mostly, the same. It adds a line stating that the portal is usable despite the warning.

The faculty-unknown message is now honest that we don't have that info, and also assures the portal is still usable.

New faculty known message:
image

New faculty unkown message:
image

(Ignore the colors, I have darkreader on)

@tymees tymees changed the base branch from develop to master June 12, 2024 10:09
@tymees tymees changed the base branch from master to acceptation June 12, 2024 10:09
@tymees tymees requested review from EdoStorm96 and miggol June 12, 2024 10:09
Copy link
Contributor

@miggol miggol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve. It's a lot clearer like this, and the different messages make it easier for us to tell what's going on based on user feedback.

The only change I might suggest is to not say "employed" but "associated with" to be more inclusive to students. With something like "aangesloten bent bij" in Dutch. But that's just a suggestion.

@tymees tymees merged commit 6bd5e1f into acceptation Jun 18, 2024
4 checks passed
@tymees tymees deleted the feat/clearer-warnings branch June 18, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants