This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Such spaces - Need much?

Below is the screenshot of the communities page that I see on my screen at work. At standard resolution, 1920x1080p, takeaway the titlebar/taskbar/statusbar, I've got about 1000px vertical height, and around 240px of the page is freezed for the head banner. I mean, 240px out 1000px = around a quarter of space most of the time useless. Do we really need that much of freeze space for headings?

Don't think so.

Parents
  • Hello Tuan,

    Thanks for the feedback. I made a small change to the Autoplant | AXSYS | OpenPlant | PlantWise community's header that should help a bit. There were some seemingly empty spaces between the bar at the top (containing the search bar, profile links, etc) and the navigation breadcrumb. This freed up about 40 pixels. Let me know what you think.

    I'm unsure if there was a specific reason why these extra spaces were included so I'll be checking with a few of my colleagues.


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

  • Hi Jesse,

    Thanks for the prompt action. I really appreciate that. However, the issue is across the board for most (if not all ) Communities pages, not just limited to the Plant Wiki area. If would be greatly appreciated if someone can perform an overall improvement the layout of this website and take your users' suggestions/recommendations into consideration.

    Below is what I think should be acceptable:

  • Thanks for the feedback - I've recorded this formally, for review and future consideration.

    Keeping the breadcrumb and navigation bars (blue area in your screenshot) always visible can help users quickly navigate to another place without having to scroll to the top, though I do agree on the importance of vertical real estate. It's a careful balance.

    Regarding the green area - we can look into that too, though I suspect there are mobile considerations.

    After further investigation, removal of that small blank area (40 pixels) could have other issues on the site, so we need to carefully assess.


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

  • Unknown said:
    Keeping the breadcrumb and navigation bars (blue area in your screenshot) always visible can help users quickly navigate to another place without having to scroll to the top, though I do agree on the importance of vertical real estate. It's a careful balance.

    Hi Jesse, not sure if anyone has actually tested out a real world use-case yet. Most of the times, people would want to "go back" rather than to "start again". The navigation bar/bread crumb area takes a user all the way back to the beginning of an area (Wiki/Forum/Blog etc.) and disregards where the user was before. Very much like the "sign-in takes me to home page" issue.

    And it doesn't take a lot of effort to scroll to top of page, a hit of "Home" key will do. So for the convenience of saving 1 keystroke/a few wheel scroll + some seconds of time, we have to scacrifice 25% of the visible area? Not a very balanced judgement in my opinion.

    Unknown said:
    Regarding the green area - we can look into that too, though I suspect there are mobile considerations.

    Has there been any analysis of what's the percentage between mobile access vs desktop access on the website? Again, this is another balancing act but in all honesty, I would have thought in this day and age, a capable layout can comfortably accomodate desktop users as well as mobile user without sacrificing too much of either type of user's experience. Surely different CSS styles can be set up and switched between different kind of interfaces.

Reply
  • Unknown said:
    Keeping the breadcrumb and navigation bars (blue area in your screenshot) always visible can help users quickly navigate to another place without having to scroll to the top, though I do agree on the importance of vertical real estate. It's a careful balance.

    Hi Jesse, not sure if anyone has actually tested out a real world use-case yet. Most of the times, people would want to "go back" rather than to "start again". The navigation bar/bread crumb area takes a user all the way back to the beginning of an area (Wiki/Forum/Blog etc.) and disregards where the user was before. Very much like the "sign-in takes me to home page" issue.

    And it doesn't take a lot of effort to scroll to top of page, a hit of "Home" key will do. So for the convenience of saving 1 keystroke/a few wheel scroll + some seconds of time, we have to scacrifice 25% of the visible area? Not a very balanced judgement in my opinion.

    Unknown said:
    Regarding the green area - we can look into that too, though I suspect there are mobile considerations.

    Has there been any analysis of what's the percentage between mobile access vs desktop access on the website? Again, this is another balancing act but in all honesty, I would have thought in this day and age, a capable layout can comfortably accomodate desktop users as well as mobile user without sacrificing too much of either type of user's experience. Surely different CSS styles can be set up and switched between different kind of interfaces.

Children
No Data