Better responsiveness #3
Loading…
Reference in New Issue
No description provided.
Delete Branch "responsiveness"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
[WIP] Better responsivenessto Better responsivenessNot a fan of the lighter background behind the icons. I rather choose a calm background image that doesn't disturb the readabilty. Using the Disroot icons in the circles will also seperate the icons from the background nicely.
I think it will be nice to change the grid on mobile view so icons are not so cramped togather. So 4 columns on wider screens and 3 colums on narrow screens. but super nice that it is now responsive!
With this PR, it is now 4 on wider screens, 3 on tablets, and 2 on mobile.
As for the logos, I thought about it. However, it means to change the role so that instead of using Font-Awesome, it uses logos. Are you fine with that? Or do we keep like two differents tasks, so that you can choose if you want to deploy with font-awesome or if you want to use your own logos?
That's a good point. You should leave the FA fonts as default and add an option to use custom icons, that would be nice.
I still think it looks better without the lighter box around and that icons on mobile devices are unnecessarily to big. I will commit my changes here, see what you think.
I don't like to much this hover link color, it makes things hard to read.
Yeah it does make things hard to read. Perhaps we could do something less invasive (just makeit darker grey or something). but for the new dashboard (when we use the same icons as on the webiste), the beetroot circle could on hover become grey?
@antilopa I've changed the role a bit to add icons as we decided. I've created a branch on host_vars so that you can test those.