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

Branding typography #139

Merged
merged 4 commits into from
Jul 2, 2019
Merged

Conversation

dpordomingo
Copy link
Contributor

@dpordomingo dpordomingo commented Jun 20, 2019

fix #134
fix #125
fix #124
fix #123
fix #122
fix #114

The new typography was introduced by #106, but some days later it was reverted by #128, so its changes were rollbacked.

Original changes made by #106 were: 555765c 450de62 43ba635 a20fde3 ec5d9ed 0414d65

After being reverted, an extra commit was applied on top of those ones: abb3431 to address the problems described by #125 #124 #123 #122

As requested by #134, I took the old work and applied on top of the current master in order to validate and merge it.

click to see more details of how the previous commits were rearranged on top of `master` 1. I took all the old six commits from above and rebase-squashed them into: d8b774b
2. And then applied abb3431c828320 on top, to fix the described problems.
3. Create this PR with the new two commits, containing the old and outdated commits.

Some screenshots testing it over the current sourced v0.14.0-beta.5

Old view:
image

New view:
image

New collaboration dashboard:
image

@dpordomingo dpordomingo added enhancement New feature or request product-design Visual, branding, typography labels Jun 20, 2019
@dpordomingo
Copy link
Contributor Author

Let me know if I should do any other testing, please.

@smacker
Copy link
Contributor

smacker commented Jun 20, 2019

plz this one as well #113
also try to click on dropdowns and other stuff on charts creation page to makes sure nothing is broken there

@smacker
Copy link
Contributor

smacker commented Jun 20, 2019

according to screenshot, #114 and #118 aren't fixed, right?

Copy link
Contributor

@ricardobaeta ricardobaeta left a comment

Choose a reason for hiding this comment

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

👍 Thank you David!

@ricardobaeta
Copy link
Contributor

ricardobaeta commented Jun 20, 2019

according to screenshot, #114 and #118 aren't fixed, right?

No they aren't @smacker , we talked about this and we agreed that chart fixing with be easily taken care by you. Can you confirm, please?

plz this one as well #113

Should I be the one to tackle this? Please confirm.

@smacker
Copy link
Contributor

smacker commented Jun 20, 2019

@ricardobaeta
as it is described in #114 apparently it isn't easily fixable on our side, my initial guess was wrong.

#113 is important. As I described in the comment it prevents modifying/creating a chart with a long title. And it's not always possible (for example on my laptop) to make the browser window bigger to workaround the problem. In pre-redesign, similar issue exists but much less bad. The chart also gets moved down but x-axis is still visible.

@ricardobaeta
Copy link
Contributor

@smacker please have in mind @dpordomingo comment on #113.

@smacker
Copy link
Contributor

smacker commented Jun 20, 2019

David said exactly the same what I did in the comment above but in more words:

  • bug exists in master too
  • solution is Long title s...

@dpordomingo
Copy link
Contributor Author

dpordomingo commented Jun 20, 2019

I think we should not block the typography redesign by issues that are already happening in current master or are not caused by that redesign itself.

Considering that:

My proposal for this PR:

  1. Test it deeply with the latest sourced-ce and our two available dashboards.
  2. Confirm that already known regressions are solved:
  3. Perform an extra sanity check
    • dropdowns, chart creation section, uast... and such
  4. Merge once (1), (2), (3) are ready
  5. Do not block this PR for non-regressions: Iterate later

@dpordomingo dpordomingo added product-design Visual, branding, typography and removed product-design Visual, branding, typography labels Jun 20, 2019
@marnovo
Copy link
Member

marnovo commented Jun 20, 2019

@dpordomingo agreed. cc: @smola

@smacker
Copy link
Contributor

smacker commented Jun 25, 2019

Let's rebase on master and check with new charts. For the rest looks like everybody agrees it's good to go already and we can merge.

@dpordomingo
Copy link
Contributor Author

dpordomingo commented Jun 27, 2019

  1. I rebased over current master,
  2. built a new image and tried it with new sourced,
  3. confirmed that all blockers described by (2) at Branding typography #139 (comment) are still solved,
  4. quick sanity check (3) confirming that there are not huge outages in:
    • our current 3 dashboards,
    • chart creation,
    • dashboard creation and reordering charts
    • running queries in SQL Lab
    • viewing UASTs

imo this is ready again to be considered as good to go.

@dpordomingo
Copy link
Contributor Author

Since #142 was made on top of this one, you might prefer to deeply test the other one, and approve this one if #142 pass your tests :D

Copy link
Contributor

@smacker smacker left a comment

Choose a reason for hiding this comment

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

Tested locally looks amazing.

Syntax highlighting in UAST tab doesn't work in Firefox though:
Screenshot 2019-06-27 at 11 55 26
Screenshot 2019-06-27 at 11 55 37

but we can fix it later

@dpordomingo
Copy link
Contributor Author

I leave here, per @smacker requirement, some screenshots showing how blocker issues were solved, and how the new UI looks like if this and #142 are merged.

#125 (Top menu looks incorrect)
#122 (Buttons looks like wrong)
image

#124 (popups with not clickable close button)
image

#123 (Incorrect table headers)
image

Collaborative dashboard
collaborative

Overview dashboard
#114 (Tables overflow the chart container)
overview

Welcome dashboard
welcome

Chart creation
image

Bblfsh tab
image

SQL Lab
image

@carlosms
Copy link
Contributor

I see the UAST tab changes some of the global styles. I have only noticed it in the top-right "New" button, it gets bigger. But there might be other places:

a

b

@carlosms
Copy link
Contributor

Why don't we fix #118 in this PR too @dpordomingo? I mean editing the chart height in the dashboard json.

@carlosms
Copy link
Contributor

I've noticed the sql lab results table now has an extra outer scrollbar. See before:
b-scroll

And after:
a-scroll

@carlosms
Copy link
Contributor

I've found a missing change in button height. In this case it's a minor thing, but it means there might be other places where buttons are not consistent.

Before:
Peek 2019-06-28 10-39

After:
Peek 2019-06-28 10-38

@marnovo
Copy link
Member

marnovo commented Jun 28, 2019

Looking great. :)

Regarding the inconsistencies at @carlosms has shown… @dpordomingo @ricardobaeta would this be something that we would fix/avoid by figuring out the puzzle with the "global variables" (i.e. being able to properly set/propagate styles top-down) first?

@smacker
Copy link
Contributor

smacker commented Jun 28, 2019

jfyi

extra outer scrollbar

I experienced this before (not sure if with current sourced-ui or the one based on previous superset 0.32)

@carlosms
Copy link
Contributor

Also as can be seen in the previous comment #139 (comment), the UAST button inside the results table now overlaps one row with the next one, and does not look as neat.

@dpordomingo
Copy link
Contributor Author

dpordomingo commented Jun 29, 2019

Do we want to release the branding once we can guarantee that it has 0 errors? or do we assume that there can be small issues to be solved in an iterative process?

I understood that it was accepted that some parts could be addressed separately as long as it would not impact heavily in the UX. I assume that we considered it because it was agreed that the benefits of having a rebranded site, are higher than the costs of having some dangling elements, pending to be adapted.

Do the arisen issues cause more damage, than the benefit of the rebranding as this PR and #142 propose?

For sure I'm not saying that we should not fix any small problem we find, nor they're not important, nor we should not deeply review the design. What I think is that we should consider if those issues impact more to the user than the benefit of merging and then continue improving in shorter iterations.

Once said that, let's consider each reported issue:

Should we block this PR until we deeply review this redesign to ensure there is no other issue like the ones reported above? Are we going to exhaustively review all the PRs addressing the rebranding? Or are we only doing sanity checks before merging, and considering the rebranding as something that will be done iteratively?

This initial commit conveys the font-family, weight, size, spacing, hierarchy and overall combination of these typography characteristics across the entire UI.
1) "fonts" directory containing Source Sans Pro & Source Code Pro font files was created. (not sure if we need to have the entire family files)
2) I'm having troubles yet with variables on custom-brand.less, becasue they don't seem to overwrite default ones. (would be great to really get the most out of it)
3) We'll need to address the typography on UI elements that are not covered in the typography section "less structure" given by superset by default. (will add rules to convey every typography need)
4) We need to create a new less file "codemirror_override.less" to brand the uast code & uast view.

Typography outliers elements
This commit conveys item 3) from the initial commit: We'll need to address the typography on UI elements that are not covered in the typography section "less structure" given by superset by default.
1) There are still elements that are brand outliers, but will be taken care of on the next commit.
2) Will focus now on the codemirrror less

Applies brand typography to outliner elements
This commit continues to address the outlier elements that are on the UI that are not covered by the typography less section variables & rules that supertset has by default.

Adds file & rules to override codemirror styles
In this commit a file was added "codemirror_override.less" that enables us to change the font of the left panel to Source Code Pro.
1) Colour scheme will be tackled later

Replaces Typography .ttf files for .woff2

Signed-off-by: Ricardo Baeta <[email protected]>
Signed-off-by: Maxim Sukharev <[email protected]>

Signed-off-by: David Pordomingo <[email protected]>
This commit contains typography fixes that solve:

1) src-d#125
2) src-d#124
3) src-d#123
4) src-d#122

It also contains the initial code for the Navbar + Navbar Links & Icons + Navbar CTA, and Navbar Dropdown branding.

Signed-off-by: Ricardo Baeta <[email protected]>

Signed-off-by: David Pordomingo <[email protected]>
This commit will solve issue src-d#114.

Signed-off-by: Ricardo Baeta <[email protected]>
This commit removes the bottom dash from the dashboard header.

Signed-off-by: Ricardo Baeta <[email protected]>
@dpordomingo dpordomingo merged commit f8359b3 into src-d:master Jul 2, 2019
@dpordomingo dpordomingo deleted the branding-typography branch July 2, 2019 12:10
@carlosms carlosms mentioned this pull request Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request product-design Visual, branding, typography
Projects
None yet
5 participants