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

Proposal: mobile/responsive layout for admin UI #3803

Closed
josip opened this issue Nov 21, 2023 · 1 comment
Closed

Proposal: mobile/responsive layout for admin UI #3803

josip opened this issue Nov 21, 2023 · 1 comment

Comments

@josip
Copy link

josip commented Nov 21, 2023

I would like to propose inclusion of a more responsive layout for the admin UI. With a mobile-friendly layout, people would be able to make quick changes or check up on logs on the go. Additionally even on desktops, this would allow the admin UI to be used more comfortably in split-screen type of a setup.

I have a prototype working, but would like to consult if this is something you'd like to merge at all at this time, and if so, how would you like to approach it. Here's a quick demo:

CleanShot.2023-11-21.at.14.09.50.online-video-cutter.com.1.mp4

Approach I've taken was to keep changes CSS-only, at the cost hiding some functionalities, notably collection search and section headers in the sidebar.

The changes were relatively small and have focused only on the sidebar, the rest of the UI was already well adopted for small screens.

@josip josip changed the title Proposal: mobile/responsive layout for admin Proposal: mobile/responsive layout for admin UI Nov 21, 2023
@ganigeorgiev
Copy link
Member

Thank you for the prototype link.

Something similar was suggested in #19 and #1867, but until we reach a more stable release, this for now remains out of the roadmap as it will be difficult to maintain while still making UI updates and I personally think that it will require major code changes to make it actually usable on mobile.

Also note that the Admin UI most likely will be refactored anyway sometime in the future as part of the planned plugins support (#898), but for now stabilizing the exposed Go APIs and improving the docs are with higher priority.

I'll close the issue for now but later we can revisit this and the other proposals.

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

No branches or pull requests

2 participants