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

Utilize space more effectively in admin screen design #2536

Closed
austincondiff opened this issue Aug 13, 2019 · 3 comments
Closed

Utilize space more effectively in admin screen design #2536

austincondiff opened this issue Aug 13, 2019 · 3 comments

Comments

@austincondiff
Copy link
Collaborator

austincondiff commented Aug 13, 2019

I know this was mentioned in #1356 and #1122, but is there any progress made in allowing users to utilize their full viewport instead of constraining the editor and preview to a set pixel amount? It seems like it is as simple as removing max-width property from the container div.

That being said, it would be nice for the main collections area to be full width as well. I know there currently isn't a whole lot being displayed at the moment, however I would be in favor of adding more details such as the last modified date to both make these screens more useful and fill up the space.

Additionally, as I am editing an entry, especially regarding objects and lists, it seems to take up a large amount of space. I need to scroll a ways down and I can only see a few items at a time. I feel that we could do a little better here.

@austincondiff austincondiff changed the title Full-width collections and editor view Utilize space more effectively in admin screen design Aug 13, 2019
@erquhart
Copy link
Contributor

We're totally open to PR's for the improvements that folks want to see!

@stale
Copy link

stale bot commented Oct 29, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@martinjagodic
Copy link
Member

Closing as stale

@martinjagodic martinjagodic closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants