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

Make backend responsive #474

Closed
bobdenotter opened this issue Jun 18, 2019 · 4 comments · Fixed by #567
Closed

Make backend responsive #474

bobdenotter opened this issue Jun 18, 2019 · 4 comments · Fixed by #567

Comments

@bobdenotter
Copy link
Member

The backend works OK-ish on Desktop formats. It looks crappy on mobile. Should be improved

@bobdenotter
Copy link
Member Author

Also: Check is how we use "Grid" is OK.. If not, either use Grid properly or refactor to Flexbox

@sbonardt
Copy link
Contributor

IMO we should rework this and start mobile first. @anketwokings, @sbonardt and anybody interested are thinking about streamlining this and getting this in properly

@sbonardt
Copy link
Contributor

Made changes for wide screens. Still WIP and under development, but already a usable solution

@sbonardt
Copy link
Contributor

The backend is now responsive, mobile first. I would still like to rewrite all classes as this isn't BEM, but I'll save that for another issue and PR.

The 'admin__body--container' is the main css Grid container for the content. It has 12 columns. The sub element 'admin_body--main' is by default 12 columns wide. If there is anything present in the sidebar region this container gets the additional class 'admin__body--container--has-sidebar' and a sub element 'admin_body--sidebar'. The 'admin__body--main' element will then be 9 columns wide and the 'admin__body--sidebar 3 columns'

Sub elements like content-listings or fields can inherit/work upon this grid.

There are still some tweaks and alignment improvements to be made in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants