-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Migrating navbar to tailwind and implementing mobile design #1060
Migrating navbar to tailwind and implementing mobile design #1060
Conversation
This reverts commit a996038. Linter updated all py files inadvertently
syncing changes
Syncing to upstream
Looks good! Slide out or down menu is good. As long as it’s fast / snappy. |
Nice!, Looks awesome |
Hey @co-decode. you can join BLT slack for better communication and further discussions. https://owasp.org/slack/invite |
Thank you, I have accepted your invitation!
Here's what it looks like above 640px. Things to mention:
|
Thank you! Looks great |
* updating main origin * Revert "updating main origin" This reverts commit a996038. Linter updated all py files inadvertently * wip: migrating navbar to tailwind * wip: nav layout done, needs functionality * navbar complete and functional * satisfy test: keep username under avatar
WIP: Would resolve #992
I am in the process of migrating the navbar styling to tailwind.
At the moment I'm just doing a translation of styles I see in our css files, so it's all a bit messy.
I am also trying to implement the mobile design mentioned in issue #992 for screen widths under 640px.
This is what I have so far:
Question: What should clicking the settings button on the left do?
Perhaps slide out a menu like in the design:
Other things to mention: