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

feat: preferences help & feedback #596

Merged
merged 5 commits into from
Jul 8, 2021

Conversation

gorjan5sk
Copy link
Contributor

  • Implement "Help & feedback page" in Preferences
  • Implement reusable components for Preferences screen

@gorjan5sk gorjan5sk self-assigned this Jul 8, 2021
@gorjan5sk gorjan5sk marked this pull request as ready for review July 8, 2021 10:31
@gorjan5sk gorjan5sk force-pushed the feature/preferences-help-feedback branch from 49caf56 to f65072b Compare July 8, 2021 10:32
@gorjan5sk gorjan5sk requested a review from antsgar July 8, 2021 10:32
</a>{' '}
before advocating for a feature request.
</p>
<button
Copy link
Contributor

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

Copy link
Contributor Author

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
Copy link
Contributor

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
Copy link
Contributor

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;
}
}

Copy link
Contributor

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

Copy link
Contributor Author

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.

@gorjan5sk gorjan5sk merged commit f6b1b57 into develop Jul 8, 2021
@gorjan5sk gorjan5sk deleted the feature/preferences-help-feedback branch July 8, 2021 18:24
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.

2 participants