-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
feat: preferences help & feedback #596
Conversation
gorjan5sk
commented
Jul 8, 2021
- Implement "Help & feedback page" in Preferences
- Implement reusable components for Preferences screen
49caf56
to
f65072b
Compare
</a>{' '} | ||
before advocating for a feature request. | ||
</p> | ||
<button |
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.
Since this opens a different page, for accessibility and semantic HTML this should be an a element styled as a button
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.
Done, now all buttons are links :)
Want to share your feedback with us? Join the Standard Notes Slack | ||
group for discussions on security, themes, editors and more. | ||
</p> | ||
<button |
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.
Same as above comment
<PreferencesSegment> | ||
<h2>Account related issue?</h2> | ||
<p>Send an email to [email protected] and we’ll sort it out.</p> | ||
<button |
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 too
@@ -44,3 +45,38 @@ | |||
@extend .color-info; | |||
} | |||
} | |||
|
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.
If we continued with the zero-client-CSS approach of utility-first classes, all of these should either belong on StyleKit as more generic reusable classes or on the HTML markup, without using extend
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.
I've removed the component classes. Created separate components and used utility classes as an interim solution until we decide.