-
-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Improve notifications settings #12497
Conversation
config/locales/en.yml
Outdated
@@ -580,6 +580,10 @@ en: | |||
discovery: Discovery | |||
sensitive_content: Sensitive content | |||
toot_layout: Toot layout | |||
notifications: | |||
email_events: Events for e-mail notifications | |||
email_events_hint: Select events that you want to receive notifications for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one clearly missing a termination! If you are reviewing this, please tell: should I use colon (:
) here or just dot (.
) is okay?
I also missed to normalize localization files, that's why CI failed. Fixed. Previous question is still active though. Whenever it resolves, I will squash the commits (hope this is okay). UPD: (stares at CI status) “What is wrong with you? >_>” |
Currently notifications page seems a bit cluttered with no clear separation between e-mail and filtering settings. This commit tries to address them by adding clear separation with headers, hints and removing continuously reused texts for events checkboxes.
Motivation
Currently notifications page seems a bit cluttered with no clear separation between e-mail and filtering settings. This PR tries to address them by adding clear separation with headers, hints and removing continuously reused texts for events checkboxes.
Visual Comparison:
(click to see full sized pictures)
Warning about visuals
Please note, that due to my technical inability to set up Mastodon instance to test these changes, screenshots above were made with browser's developer tools, using the texts from files and placing new elements at expected places. If that does not satisfy you, you may set up your own instance and review changes manually.
A word about PR
I'm nowhere familiar with what “HAML” is and not explored it yet, because this commit is so small, the changes primarily were made by reviewing other files in project and guessing the syntax. I expect maintainers (or reviewers) to test it and suggest what to fix and how. Thanks!