-
Notifications
You must be signed in to change notification settings - Fork 112
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
Rebrand profile page #1352
Rebrand profile page #1352
Conversation
hey @el-mapache this is looking fantastic! a couple things i spotted that should be addressed before we push this through:
|
bcc039b
to
a324eea
Compare
@rtwell I changed the blue color, and added back the 'Your account' header on mobile! |
Looking at it now, it seems like we will need a different header entirely for a non-verified account, since the spacing currently takes the presence of the verified badge as a given. |
@rtwell I just left a comment above re: the spacing, but the email currently only displays on a separate line in the case of a long email — like Should the email always display on a separate line, regardless of length? I'm assuming the name is going to always appear inline unless it is a very long first name. |
Ah sorry Adam—i should have specified: Yes, i imagined the email addy, in
bold, on its own line, on mobile.
…On Tue, Apr 11, 2017 at 4:16 PM, Adam B ***@***.***> wrote:
@rtwell <https://github.com/rtwell> I just left a comment above re: the
spacing, but the email currently only displays on a separate line in the
case of a long email — like the ***@***.*** that you have
in the comps.
Should the email always display on a separate line, regardless of length?
I'm assuming the name is going to always appear inline unless it is a very
long first name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1352 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL-58QyB2WkYXxdpaexoO8QVt09CMUUsks5ru-2ZgaJpZM4M5TP->
.
|
I realize that is different than the LOA3 instance 😱 but since there is no verified mark, it felt strange sitting by itself. Breaking it onto two lines will deal with the majority of lengthy government email addresses (and avoid truncating them) |
@rtwell understood, will do! |
@rtwell Here is the header for an unverified user: and a verified one: |
0de4690
to
f119a4c
Compare
No, that looks like a merge conflict issue, it wasn't there before 😞 |
app/views/profile/_header.html.slim
Outdated
@@ -1,11 +1,14 @@ | |||
.clearfix.pt2.pb3.sm-py0.bg-light-blue.sm-bg-none | |||
.clearfix.pt2.pb2.sm-py0.mb2.bg-light-blue.sm-bg-none |
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.
Small thing, .pt2.pb2
can be condensed to .py2
Looking at this again there are now a million problems with the visuals |
@@ -0,0 +1,11 @@ | |||
.p2.clearfix |
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.
A few unnecessary grid classes:
.p2.clearfix
.col.col-8.clearfix
.sm-col.sm-col-6.bold
= name
.sm-col.sm-col-6
= content if local_assigns.key? :content
.col.col-4.right-align
- if local_assigns.key? :path
= render action, path: path, name: name
- else
= render action
1c72b96
to
6286c0a
Compare
app/views/profile/index.html.slim
Outdated
content: current_user.email, | ||
path: manage_email_path, | ||
action: @view_model.edit_action_partial | ||
.border-bottom.border-blue-light |
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.
Could this line be added to the containing .p2.clearfix
of _profile_item.html.slim
instead of having the extra div?
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 don't think so, because we want to be able to define when we have a bottom border (e.g. not on the last item)
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 went with a border-top to remove this duplication.
app/views/shared/_nav_auth.html.slim
Outdated
nav.bg-white | ||
.container.px2.sm-py3.pt2.pb0 | ||
.clearfix | ||
.sm-col.mb1.sm-m0.col.col-8 | ||
.sm-col.mb1.sm-m0.col.col-7 |
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.
.sm-col
not necessary here
app/views/shared/_nav_auth.html.slim
Outdated
= link_to \ | ||
image_tag(asset_url('logo.svg'), | ||
alt: APP_NAME, | ||
class: 'align-bottom', | ||
width: 170), root_path | ||
.sm-col-right.right-align.col.col-4 | ||
.sm-col-right.right-align.col.col-5 |
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.
.sm-col-right
not necessary here
c1d2ae2
to
03e58d7
Compare
@@ -0,0 +1 @@ | |||
.bg-gray-lighter { background-color: $gray-lighter; } |
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.
We have bg-light-blue
and sm-bg-light-blue
in util.scss
so we might want to consolidate our custom background colors.
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.
Would you prefer to have those classes in util or in a background.scss file?
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'm guessing we may continue to add additional variations so I think having them all in background.scss
makes sense.
@@ -11,6 +11,8 @@ | |||
|
|||
.border-gray { border-color: $gray } | |||
|
|||
.border-blue-lighter { border-color: $blue-lighter; } |
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 think we should move this into our own border.scss
vs the vendor stylesheet just in case we ever update Basscss.
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.
yeah absolutely, I thought I moved this out already!
app/views/profile/_pii.html.slim
Outdated
.mt3.sm-mt2.mb4 | ||
.py-12p.border-top | ||
.border.border-blue-lighter.rounded-md.mb3 | ||
.bg-light-blue.py2.px2.h6.caps.clearfix |
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.
Switch the .py2
to .py1
to match the padding of the other panel headings.
**Why**: CLeaning up view/changing styles to match new designs
**Why**: Trying to keep the partials folder clean
**Why**: Necessary css tweaks, breaks out partial to keep with view model convention
**Why**: Code consistency
**Why**: Other locale files are alphabetized, this should be as well. Use a string to represent the password
**Why**: User shouldn't be able to generate a new personal key without a valid password
**Why**: It wasn't written correctly and would have needed a view context to work properly anyway
**Why**: Its in the comps!
**Why**: Seems like I accidentally revereted some files during a rebase
**Why**: The html stucture needed to change in a few different ways for verified vs non-verified users
**Why**: The code was in a weird state
**Why**: They were the same
**Why**: Codeclimate
**Why**: We need it for build, and we shouldnt have custom styles defined in a vendor stylesheet
**Why**: They were identical to other declarations and therefore not needed
**Why**: Reduces repetition, makes layout look correct
be8f679
to
028db9c
Compare
@hursey013 cleaned up! |
@@ -10,6 +10,9 @@ | |||
.rounded-xl { border-radius: $border-radius-xl; } | |||
.rounded-xxl { border-radius: $border-radius-xxl; } | |||
|
|||
.border-blue-lighter { border-color: $blue-lighter; } |
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 doesn't look like it's being used, and after talking it through with @rtwell this can also just fall back to using the default $border-color
.
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 looks good to me, nice work!
**Why**: The profile box tables looked weird. Also moved some files and css declarations around
028db9c
to
9490c93
Compare
Why: Better readability and a mobile first design
Screenshots: