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

Dev / design updates: typography, colours, button styles, etc. #322

Merged
merged 15 commits into from
Feb 18, 2020

Conversation

candu
Copy link

@candu candu commented Feb 18, 2020

This PR closes #318 , #319 , and #320 by cutting a broad swath through @shinechaudhuri 's excellent dev / design walkthrough on the Figma mocks.

In the process, we use theming and SASS variables to customize key parts of Vuetify across the entire application, plus a few targeted CSS overrides where needed. These CSS overrides lean on Vuetify's support for generating CSS3 variables based on theme colours.

Evan Savage added 14 commits February 6, 2020 18:30
Added `styles/variables.scss`, which `vuetify-loader` uses to override SCSS variable definitions in Vuetify.

We can use this as a starting point for implementing the MOVE Design System.
and move the user sign in / sign out button into its own component.
to get some further progress here.
Turns out that Vuetify theming has *excellent* integration with CSS variables, `color` attributes, and other methods of dynamic styling throughout the application - really makes a lot of these tasks easier.
This will allow us to apply button styling changes application-wide (in case these styles ever change).
and button / copy overhaul, plus a "Clear All" action for filters.
There's a bunch of intricate form element work here - this is just the start.
This allows us to accept text entry in the text box, which makes entering dates faster for power users (and also allows for easier keyboard entry).
Last few pieces - only remaining thing here is to restyle the toast.
as per designs.  (Still haven't switched over to white-on-black.)
as per mocks.  Still a couple of more complex things (e.g. Assign-To selector) that I haven't done yet, but we're getting there.
Finally had a chance to address a couple of bugs in `<FcButton type="secondary">` - we weren't adding the `.fc-button` class properly.
At this point, we've finished all the small bits and pieces, and can tackle some of the larger things (assign-to menu, reporting, etc.)
Copy link
Author

@candu candu left a comment

Choose a reason for hiding this comment

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

mostly good, a couple of smallish changes and we're there

bdit-flashcrow.code-workspace Show resolved Hide resolved
lib/time/DateTime.js Show resolved Hide resolved
styles/variables.scss Outdated Show resolved Hide resolved
web/App.vue Show resolved Hide resolved
web/components/FcDrawerRequestStudy.vue Show resolved Hide resolved
web/components/inputs/FcDatePicker.vue Show resolved Hide resolved
web/components/inputs/FcInputTextArray.vue Outdated Show resolved Hide resolved
web/components/nav/FcDashboardNavItem.vue Show resolved Hide resolved
web/main.js Show resolved Hide resolved
Switch `<v-btn>` for `<FcButton>`, use `map-get` instead of hardcoding SCSS variables, testing, and comments.
@candu candu merged commit 7921b5e into master Feb 18, 2020
@candu candu deleted the gh318-move-typography branch February 18, 2020 22:08
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.

MOVE Design System: typography
1 participant