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

Styling improvements for the Analysis results. #671

Closed
boblinthorst opened this issue Jul 25, 2018 · 8 comments
Closed

Styling improvements for the Analysis results. #671

boblinthorst opened this issue Jul 25, 2018 · 8 comments
Assignees

Comments

@boblinthorst
Copy link
Contributor

Split off from #492.

The PR became way too big, and addressing the styling comments in the PR would make it even bigger than it already is.

In the words of @maartenleenders:
The styling in the ContentAnalysis seems to be slightly below our standards, but that is my opinion. I think we'd do well to give everything a little more 'breathing room' with padding/margins. @hedgefield has offered to sit in on a little styling session to improve things. I would also be fine if you split this up into a new issue, as this PR has become quite big.

@hedgefield
Copy link

hedgefield commented Jul 27, 2018

I checked out the components standalone app and did some tweaking. Here are some improvements:

  • For each collapsible section, add margin-bottom: 8px
  • For each collapsible section header, set font-size: 1.1em and padding: 8px 16px
  • For each analysis result, set padding: 8px 16px

I assume the margin/padding around all the components is set globally on the sidebar element? Is it possible to remove it there and add it to each component individually? It's a little cumbersome, but it produces better results for the focus indicator. Update: Andrea mentions this is actually already the case in #653 and #654, so it should here too.

3

@afercia
Copy link
Contributor

afercia commented Jul 27, 2018

One important thing to consider is that the ContentAnalysis uses a custom implementation of the "collapsible header", duplicating great part of the code. I'd tend to think it shouldn't do this, and just reuse the Collapsible component which is going to be refactored in #653 and #654

@afercia
Copy link
Contributor

afercia commented Jul 27, 2018

For #653 and #654 I'm going to get rid of AnalysisCollapsible and use Collapsible directly, that implies adjusting various CSS so I'd like to take care of this, if no objections.

@afercia afercia assigned afercia and unassigned maartenleenders Jul 27, 2018
@afercia
Copy link
Contributor

afercia commented Jul 27, 2018

For each collapsible section header, set font-size: 1.1em

I'd need the value in pixels for this, as the em one varies depending on the context (standalone app or within the meta box) and i've also made other changes.

For each analysis result, set padding: 8px 16px

Do you mean each group of results or each single item in a group of results?

@hedgefield
Copy link

I'd need the value in pixels for this, as the em one varies depending on the context (standalone app or within the meta box) and i've also made other changes.

I'd say 14 then, just a tad bigger than the default 13px sidebar font size.

Do you mean each group of results or each single item in a group of results?

Each single item.

@afercia
Copy link
Contributor

afercia commented Jul 30, 2018

Each single item.

OK but I'd suggest to check it again once it's in the meta box. Right now, with the changes made on #676 the items already have a good spacing (see below). I'm afraid adding more padding will make them way too spaces, but again this needs to be checked in the meta box.

screen shot 2018-07-29 at 17 21 39

@hedgefield
Copy link

Ahh yes this looks very good, carry on.

@afercia
Copy link
Contributor

afercia commented Jul 30, 2018

We need to keep this open to adjust the left and right padding on the StyledSection in the meta box.

Now that the analysis has ben changed to have its own left and right paddings, the ones in the StyledSection add too much space. Moving to the queue.

@afercia afercia reopened this Jul 30, 2018
@abotteram abotteram assigned moorscode and unassigned afercia and hedgefield Aug 1, 2018
@abotteram abotteram removed the queue label Aug 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants