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

Small update to the UI's look and feel #395

Merged
merged 20 commits into from
May 18, 2017
Merged

Small update to the UI's look and feel #395

merged 20 commits into from
May 18, 2017

Conversation

rafaelconde
Copy link
Contributor

- Summary
This PR offers a very minor, pure visual update to the UI.
Take it as quick and dirty fixes to how it looks, and hopefully the plan is to fan this spark into a flame, and consider a more thoughtful effort to rethink the User Interface.

- Test plan

demo-2

- Description for the changelog

Updates typography, colors, and some UI visual tweaks

- A picture of a cute animal (not mandatory but encouraged)

sloth

@erquhart
Copy link
Contributor

erquhart commented May 1, 2017

@rafaelconde so fresh and so clean! Really happy to see this PR!

Things I love:

  • That typography!
  • Depth and motion
  • Improved consistency
  • No longer looks bad

I really only have one high level concern: contrast. We need it. Your mocks in #179 use gray for the header and sidebar, what do you think of pulling that into this change? Same for the form fields - at least for this iteration, we should have distinct borders for them. I think we can pull it off without hurting the look.

I mean you, you can pull it off. lol.

Copy link
Contributor

@erquhart erquhart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few basic code review points here, nothing major.

@@ -2,6 +2,8 @@

.appBar {
background-color: var(--backgroundAltColor);
height: auto;
padding: 8px 2.4rem;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to see us stick to pixels for units, but open to discussion on it if you feel strongly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd love to see us move away from pixels across the board (better for accessibility), but that's a much longer discussion, and one I'll probably lose. :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm with @verythorough on using relative units instead of pixels. Any reason you prefer pixels, @erquhart?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imorente the reasons for using px are consistency with existing CSS and the fact that rems and ems can cause half-pixel boundaries, which are undesirable. I have mixed feelings - those are both significant issues, but the accessibility problem is a hard one to ignore. For now, I think we should stick with px for the simple reason that we shouldn't make a transition to relative units ad-hoc, even if we do end up using them at some point in the future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, the idea is:

  1. Use pixels everywhere for now - simple and declarative.
  2. When we get an actual design system in place and get rid of all the hodge podge, bring in the ems and rems. It's more complex, but the benefits are there if we implement properly.

@@ -56,7 +56,6 @@ export default class EntryListing extends React.Component {
<p>{entry.getIn(['data', inferedFields.descriptionField])}</p>
: inferedFields.remainingFields && inferedFields.remainingFields.map(f => (
<p key={f.get('name')} className={styles.cardList}>
<span className={styles.cardListLabel}>{f.get('label')}:</span>{' '}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that this is redundant when viewing all entries of a given type, but it's necessary for the editorial workflow and search, where multiple entry types are present at once. If we're removing this we should add it back in for those views.

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'll leave this to you, I'll revert it back 👍

@@ -3,31 +3,35 @@
.card {
composes: base container rounded depth;
overflow: hidden;
}

.card > *:not(iframe, video, img, header, footer) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At a glance I'm uncertain why these ungainly selectors were added - are you sure we don't need them?

}

.card > iframe,
.card > video,
.card > img {
max-width: 100%;
margin: -16px -24px 16px -24px;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick: you can drop the fourth value.

@cassandraoid
Copy link

I can't wait for the facelift.

My notes:

  • I agree we need more contrast. The cards with the same pattern as the background fades in a little bit too much for me.
  • The grid in the editor feels off to me. I like the contrast we have in it now, just wish it was a little prettier. (IE:Boxes feels shallow.)

@biilmann
Copy link
Contributor

biilmann commented May 1, 2017

Comparing this:

screen shot 2017-05-01 at 11 42 37 am

With the current editing screen:

screen shot 2017-05-01 at 11 42 43 am

I think the current version is much easier to use. We need to make the UI look better, but it should never be at the cost of clarity and familiarity and I would bet good money that the current version will perform much, much better in any user testing with content editors that have never tried the CMS before.

I think the steps @erquhart has been taking in the current version to move away from the more discrete UI elements I had in my initial mockups, and towards something that looks way more like traditional form elements from a Wordpress admin UI or the like, is the right approach. The #1 goal should be to make it really, really easy to see what is the preview, what is a form element, where you can click, where the different fields are separated, etc.

Copy link
Contributor

@Benaiah Benaiah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like the direction you've gone. I have a couple small nitpicks on the CSS changes, but those are trivial.

Some thoughts on the design changes:

  • While I think most of the entry draft fields such as single lines or images are pretty clear, the body is a bit confusing. It's not really clear where the textbox starts or ends, and the toolbar is a bit confusing since it looks almost identical to the contents of the body editor. It actually looks a little like I'm supposed to edit the text in the toolbar, since it has the same underline as the text fields above.

  • When the cards don't distribute evenly across the rows, extra cards at the bottom are stretched dramatically to fill the space. Is this intended?

  • The search box and the rest of the header have very similar background colors, which is kinda hard on my eyes. IDK if that's a real issue or just me.

margin-left: 15px;
margin-bottom: 16px;
margin-left: 16px;
/*max-width: 31%;*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be either uncommented or removed. We shouldn't have commented-out code committed to the repo.

letter-spacing: 0;
line-height: 24px;
padding: 0;
color: #8c8c8c;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this should be hardcoded - we should add it as a text color in theme.css.

Benaiah
Benaiah previously approved these changes May 3, 2017
Copy link
Contributor

@Benaiah Benaiah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Benaiah Benaiah dismissed their stale review May 3, 2017 19:31

Needs rebase to ensure scrolling issues are still fixed.

Copy link
Contributor

@Benaiah Benaiah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - this merges easily into @erquhart's upcoming text editor scrolling PR, and that fix still works correctly once that's done.

@erquhart erquhart force-pushed the visual-tweaks branch 2 times, most recently from a65173f to 9745ac2 Compare May 3, 2017 19:56
@erquhart
Copy link
Contributor

erquhart commented May 3, 2017

Rebased and added a commit to address the following:

  • Improved entry listing contrast by replacing shadow/border with input field border styling
  • Removed entry listing flex treatment - stretching cards can lead to wonky image presentation and degrade the overall appearance
  • Removed leftover toolbar bottom border
  • Slight code improvements

@rafaelconde let me know if you have thoughts on that last commit. I do think depth in the cards UI would be awesome, as well as a more elegant card grid presentation, but I think we need more polish when taking those steps. As it was, they were detracting from your stellar improvements.

@biilmann
Copy link
Contributor

biilmann commented May 3, 2017

There's still some contract issues for some widgets - the image and date widget for examlple:

screen shot 2017-05-03 at 2 17 39 pm

And the bottom bar also needs some clearer definition imo - right now it floats together with the forms panel.

@erquhart
Copy link
Contributor

erquhart commented May 3, 2017

@biilmann I was thinking we could settle a bit on this PR, and fix the remaining contrast issues in a subsequent PR. Widgets and the editor footer are both on my radar.

Copy link
Contributor

@erquhart erquhart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hold off on merging, fixing the sticky toolbar appearance.

@calavera
Copy link
Contributor

calavera commented May 5, 2017

The contrast of the image widget is still a little bit off, it's very easy to miss. Can we make the border at least slightly more visible? Why are we using such a light grey in every border?
screenshot from 2017-05-05 10-58-14

@erquhart
Copy link
Contributor

erquhart commented May 9, 2017

@rafaelconde if you can improve the contrast issues that David and Matt pointed out, we should be good to merge.

@rafaelconde
Copy link
Contributor Author

I addressed the contrast of popover and borders.

  • I don't believe that removing the drop-shadow on the cards is the best way to address the contrast issue (now some cards have depth, some don't 🙃).
  • I also don't think that removing the adaptive grid on the card layout is the best way to address the super wide orphan elements — this way we effectively will never have the grid taking advantage of the available space, it looks odd IMO.

I also think that this could and should be addressed on a separate PR 🙏

@erquhart
Copy link
Contributor

erquhart commented May 10, 2017

@rafaelconde thanks, and yeah there's plenty to improve, and there will be more opportunity to do so. Just want to get this thing merged right now!

@biilmann @calavera I'm good with Rafa's changes, and I'm planning to merge this at EOD if there are no objections.

@calavera
Copy link
Contributor

My main issue is that I can barely see the border in the image widget. That has not been addressed.

@rafaelconde
Copy link
Contributor Author

screenshot 2017-05-10 14 01 12

Assuming @calavera is talking about this — I literally don't know how to change the border on that.

@imorente
Copy link
Contributor

@rafaelconde
Copy link
Contributor Author

Thanks @imorente !

@erquhart
Copy link
Contributor

erquhart commented May 12, 2017

screen shot 2017-05-12 at 12 00 45 pm

@calavera good?

Copy link
Contributor

@erquhart erquhart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rafa just mentioned something I think we all forgot - the editorial workflow. He's planning to update for that soon, adding this as a requested change so we don't merge.

@calavera
Copy link
Contributor

@calavera good?

yes

Copy link
Contributor

@erquhart erquhart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked out the list and object widgets too, looks fine.

LGTM

@erquhart erquhart merged commit 2a1e9b4 into master May 18, 2017
@erquhart erquhart deleted the visual-tweaks branch May 18, 2017 20:12
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.

8 participants