-
Notifications
You must be signed in to change notification settings - Fork 8
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
FTUE Dark-mode #636
FTUE Dark-mode #636
Conversation
@@ -19,7 +19,7 @@ services: | |||
build: ./frontend | |||
volumes: | |||
- './frontend:/app' | |||
- 'node_modules:/app/node_modules' | |||
- '/app/node_modules' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went back to anon volumes. You can do docker-compose up --build -V
to nuke the built node_modules when deps update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worked perfectly fine, thanks for the hint!
@@ -1,16 +1,14 @@ | |||
<!DOCTYPE html> | |||
<html lang=""> | |||
<html lang="" data-tbpro-service="apmt"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Used in the css to select the correct service colours. We could also use another solution but I had the .dark
class on the brain. Alternatively you can use "send" as the value to get send's colours.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @aaspinwall for the future where send has a ui and I've actually split this off into its own repo 😅
Looks great Mel! A few little things I spotted - not sure if you're only looking at colour atm and what I'm listing isn't of focus:
(I can't see active states with the input fields, but in case, they should have primary teal for the outline) |
Mel's keen eye caught one more item - the glow under the modal is missing on all screens. and I'm also wondering - is it possible to show the empty calendar interface / dashboard under a scrim during FTUE modals? |
Glow up! Thanks - looks beautiful! |
Is the active state green outline A3ECE3? (primary green (dark mode) looks like light mode primary atm And which red are you using for the required state outline? Is it we can use the dark mode text-critical colour for the outline: EF4444 |
and the dashboard behind the scrim looks AMAZING! Magic wizardy :) |
* Move up content on finish page * Checkbox tweaks for synccard.
Active outline is tailwind messery. I'll try to decouple it, but it might break the old-style elements. The sooner we re-design the entire app, the sooner I can remove a lot of css-hacks 😄 And for the error outline it's the text/icon critical |
Additionally there doesn't seem to be a way to adjust the checkbox in css without faking the checkmark. That's...an odd oversight. I can look into that in the future if that's alright! |
tailwind misery. No worries - I don't want these little things to block this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks awesome! Great work Mel!
Just some things I observed (might be out of scope here though):
- Google still has the earlier appointment logo when connecting an account:
- The input field for the schedule title "My schedule" looks a bit out of place without border radius and the placeholder without left padding:
- The "select all" buttons in calendar selection broke out to the bottom for some reason:
We might want to overwrite that inherited top attribute:
@@ -103,6 +109,36 @@ const onDateChange = (dateObj: TimeFormatted) => { | |||
|
|||
// initially load data when component gets remounted | |||
onMounted(async () => { | |||
// Don't actually load anything during the FTUE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch!
Thanks for the logo catch! I'll update that, and into the lack of padding. As for the placement of the Select all button, that's actually how it is designed. 😅 |
Oh haha, but in your initial screenshots the Select all button is positioned more on top 🤔 |
Ah yeah it somehow reverted its position, laurel caught it and commented on that button, so i moved it back to the correct split area position. |
Related: #297
The majority of work here was re-organizing the pro services colours. A lot of the components are using an older colour spec. There's some obvious differences from the design due to this, so matched the best I could.
I've also moved bubble-select to the tbpro subdirectory, since it's a pro component.
cc @laurelterlesky
Screenshots