-
Notifications
You must be signed in to change notification settings - Fork 144
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
🚀 Feature: Full-width container layout #998
Comments
Thanks @dokgu for raising this feature request. Will take this up with our team :) |
Hi @dokgu are you using Cloud? |
No I have a self-hosted instance in GCP. |
@dokgu Hey there! Just wanted to follow up on this. Currently, we're experimenting with a full-width layout for Databases. I think this is the main section where the limited width is causing issues. Let me know if the lack of space is causing issues anywhere else so I can take that into account. Thank you! |
@sara-k-48 Thanks for following up - for me the main issue is when I'm looking at documents. The databases page seems okay, collections page seems okay as well. I don't use functions or messaging so I don't really know what those look like but documents with lots of attributes is my main concern here. |
🔖 Feature description
Add an option to select which layout to use (fixed width vs full width). A way to implement this is similar to how you would select whether to use light/dark/system theme.
🎤 Pitch
Right now appwrite has a max width of
1260px
for its main content. On a wide screen monitor, lots of space is wasted - especially when I am looking at documents that have multiple attributes. I barely see any data at all without having to open each document in a separate tab. When I am debugging and want to look at the documents in a tabular manner to easily compare the values etc. It's really hard to do that. The table cells are too squished together.👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: