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

Rebrand profile page #1352

Merged
merged 17 commits into from
Apr 14, 2017
Merged

Rebrand profile page #1352

merged 17 commits into from
Apr 14, 2017

Conversation

el-mapache
Copy link
Contributor

Why: Better readability and a mobile first design

Screenshots:

screen shot 2017-04-10 at 4 44 16 pm

screen shot 2017-04-10 at 4 44 25 pm

screen shot 2017-04-10 at 4 44 47 pm

screen shot 2017-04-10 at 4 45 34 pm

@rtwell
Copy link

rtwell commented Apr 10, 2017

hey @el-mapache this is looking fantastic!

a couple things i spotted that should be addressed before we push this through:

  1. we're missing the Account information header on mobile

  2. the blue in the box-headers should be the same blue as the Welcome… background, #F2F9FF

@el-mapache el-mapache force-pushed the ab-profile-sections branch 3 times, most recently from bcc039b to a324eea Compare April 11, 2017 19:17
@el-mapache
Copy link
Contributor Author

@rtwell I changed the blue color, and added back the 'Your account' header on mobile!

screen shot 2017-04-11 at 5 03 01 pm

@el-mapache
Copy link
Contributor Author

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

rtwell commented Apr 11, 2017

This is how I imagined it:
image

@el-mapache
Copy link
Contributor Author

@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 homerjsimpson@hotmail.com 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.

@rtwell
Copy link

rtwell commented Apr 11, 2017 via email

@rtwell
Copy link

rtwell commented Apr 11, 2017

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)

@el-mapache
Copy link
Contributor Author

@rtwell understood, will do!

@el-mapache
Copy link
Contributor Author

@rtwell Here is the header for an unverified user:

screen shot 2017-04-12 at 9 00 12 am

and a verified one:

screen shot 2017-04-12 at 9 06 15 am

@el-mapache el-mapache force-pushed the ab-profile-sections branch 2 times, most recently from 0de4690 to f119a4c Compare April 13, 2017 16:27
@hursey013
Copy link
Member

I noticed on LOA1 the "Profile information" heading is still visible, is that expected?
screen shot 2017-04-13 at 3 30 12 pm

@el-mapache
Copy link
Contributor Author

No, that looks like a merge conflict issue, it wasn't there before 😞

@@ -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
Copy link
Member

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

@el-mapache
Copy link
Contributor Author

Looking at this again there are now a million problems with the visuals

@@ -0,0 +1,11 @@
.p2.clearfix
Copy link
Member

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

@el-mapache el-mapache force-pushed the ab-profile-sections branch 2 times, most recently from 1c72b96 to 6286c0a Compare April 13, 2017 19:52
content: current_user.email,
path: manage_email_path,
action: @view_model.edit_action_partial
.border-bottom.border-blue-light
Copy link
Member

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?

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 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)

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 went with a border-top to remove this duplication.

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

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

= 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
Copy link
Member

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

@@ -0,0 +1 @@
.bg-gray-lighter { background-color: $gray-lighter; }
Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

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; }
Copy link
Member

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.

Copy link
Contributor Author

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!

@hursey013
Copy link
Member

This is looking awesome, just noticed a few super small things when running locally then should be good to go.

LOA3 on mobile, Profile information looks like the rounded corners are still present and needs a bottom border:
screen shot 2017-04-14 at 10 13 31 am

Bottom border on this gray div ends just a tad bit short:
screen shot 2017-04-14 at 10 13 54 am

I think the values in login information and 2fa section need to move one column to the right so all of the values are in line:
screen shot 2017-04-14 at 10 25 39 am

.mt3.sm-mt2.mb4
.py-12p.border-top
.border.border-blue-lighter.rounded-md.mb3
.bg-light-blue.py2.px2.h6.caps.clearfix
Copy link
Member

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**: 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
@el-mapache
Copy link
Contributor Author

@hursey013 cleaned up!

screen shot 2017-04-14 at 11 13 07 am

screen shot 2017-04-14 at 11 12 56 am

@@ -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; }
Copy link
Member

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.

Copy link
Member

@hursey013 hursey013 left a 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
@el-mapache el-mapache merged commit 0b09dd3 into master Apr 14, 2017
@el-mapache el-mapache deleted the ab-profile-sections branch April 14, 2017 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants