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

Width of the Collectives app (white space between page content and page list) #242

Closed
mejo- opened this issue Sep 8, 2021 · 8 comments · Fixed by #874
Closed

Width of the Collectives app (white space between page content and page list) #242

mejo- opened this issue Sep 8, 2021 · 8 comments · Fixed by #874
Assignees

Comments

@mejo-
Copy link
Member

mejo- commented Sep 8, 2021

On large screens, there's a lot of unusued white space between page content and page list.

We got the feedback a few times that this looks "wrong" and ugly.

@mejo-
Copy link
Member Author

mejo- commented Sep 8, 2021

In GitLab by @crobarcro on Sep 8, 2021, 13:40

I was actually planning to ask the same issue. In principle the default width is a 'good' or 'comfortable' reading width, or would be in a printed book. But in a wiki style format, usually you just want as much info on the page as possible.

@mejo-
Copy link
Member Author

mejo- commented Sep 9, 2021

In GitLab by @ya-d on Sep 9, 2021, 10:58

Oh, please don't. I honestly don't know who at Wikipedia thinks its a good idea to spread lines full width on a 27" monitor. Just think of any newspaper, magazine or text based site. None is doing this because it is an awful reading experience and every typography guide tells you lines of 90+ characters harm reading. Whitespace is not a bad thing.

Of course it's something different to more closely connect page content and page list. Maybe center text-container to app-content-wrapper instead of app-content-details or simply align it to the page list on the left with some margin. (Like rich workspaces in Files.)

image

@mejo-
Copy link
Member Author

mejo- commented Sep 9, 2021

In GitLab by @crobarcro on Sep 9, 2021, 11:24

Perhaps make it an admin or user-settable option then? I suspect there will be many opinions on this.

@mejo-
Copy link
Member Author

mejo- commented Oct 26, 2021

We discussed this in the design call and didn't come up with a good solution so far.

We agreed though that simply extending the editor width is not an option - as wide text is neither legible nor looking well.

@mejo-
Copy link
Member Author

mejo- commented Oct 27, 2021

In GitLab by @RCrozier on Oct 27, 2021, 11:01

Allowing at least images to be wider than the text would be a good option?

Allowing users to decide the text width seems like a good solution to me, since this is a personal preference. Some people hate wide text, others would prefer it.

@mejo-
Copy link
Member Author

mejo- commented Sep 26, 2022

In GitLab by @KopfKrieg on Sep 26, 2022, 20:33

Images and tables maybe? Text is fine for me, but especially tables are a problem because the width is simply too small for more than 3-4 columns.

@theron29
Copy link

theron29 commented Aug 28, 2023

We discussed this in the design call and didn't come up with a good solution so far.

We agreed though that simply extending the editor width is not an option - as wide text is neither legible nor looking well.

Please do not think about this problem only from the 'simple text' perspective. If e.g. tables, code snippets, pictures, graphs or diagrams are included, the current (very small) width of Collectives pages is borderline with unusable :-(

If I look at e.g. Atlassian Confluence, they resolved this issue by including a small icon somewhere in the corner to switch between small width and wide(r) width. That seems like a good compromise, which is very useful for us normal people working all day long with standard widescreen displays with a need to store complex readable information/documentation online.

Thank you.

@KaeTuuN
Copy link

KaeTuuN commented Sep 4, 2023

Today, on a modern PC or Laptop with at least a 16:9 screen, this App is rather useless as a Wiki. Looking at a table that is larger than 2x2 is just a pain in the ***.

My suggestions are:

  1. Increase the standard width at least by 25%!
  2. Implement a Button to switch between "Full Width" an "Standard width" (like @theron29 wrote)
  3. Think about a dynamic width based on the available Space (maybe width a min and max value)
    All of these points could be developed and implemented separatly but I think this will increase the usability of Collectives a lot!

Greetings,
Kae

@mejo- mejo- moved this to 🏗️ In progress in 📝 Office team Sep 12, 2023
@mejo- mejo- self-assigned this Sep 12, 2023
mejo- added a commit that referenced this issue Sep 12, 2023
Fixes: #242

Signed-off-by: Jonas <jonas@freesources.org>
mejo- added a commit that referenced this issue Sep 12, 2023
Fixes: #242

Signed-off-by: Jonas <jonas@freesources.org>
mejo- added a commit that referenced this issue Sep 13, 2023
Fixes: #242

Signed-off-by: Jonas <jonas@freesources.org>
mejo- added a commit that referenced this issue Sep 13, 2023
Fixes: #242

Signed-off-by: Jonas <jonas@freesources.org>
mejo- added a commit that referenced this issue Sep 14, 2023
Fixes: #242

Signed-off-by: Jonas <jonas@freesources.org>
@github-project-automation github-project-automation bot moved this from 🏗️ In progress to ☑️ Done in 📝 Office team Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants