search

adam-grandt-tts / data-driven-acquisition

This system is a POC of a document management tool that will initiate acquisition document packages, and allow the acquisition work force to manage them as data. Handling some of the manual work of keeping the document up to date from an intuitive user interface.
Other
2 stars 1 forks source link

Support wider content when viewing and editing acquisition files. #13

Open adunkman opened 4 years ago

adunkman commented 4 years ago

The designs suggested in #2 do not support content which would benefit from navigator-width space, as demonstrated in #12:

Sheet editor Document editor
Screenshot of sheet editor Screenshot of document editor
adunkman commented 4 years ago

Potential paths forward:

  1. Remove the sidebar from these pages, which would open up 100% of the navigator width for these editors.

    I can see this being confusing if some acquisition pages have a sidebar, and some do not — so I’d suggest removing the sidebar design entirely to open up available space for the editors, instead moving to a top menu similar to the extended USWDS header (the Logout link would replace the search bar, and the menu beneath the project title would be what is now in the sidebar menu):

    Screenshot of the extended USWDS header

    The downside to this solution is that it reduces discoverability of the folders, and may be less familiar to users who are used to using file-based document explorers.

  2. Remove the maximum width of the layout, allowing the header’s title and logout buttons to expand to the edges of the screen, and the sidebar float along the left side of the window.

    Here’s a quick mockup of what that would look like on my screen:

    Screenshot of sheet editor with maximum width removed

    This gives additional space for the editors, but still is not enough space to prevent the sheet editor from overflowing off the screen.

  3. Change the editors. Moving to lighter weight document and sheet editors could reduce visual noise and the amount of space required to render them.

Some combination of these (and other) solutions may be appropriate as well.

adunkman commented 4 years ago

@adam-grandt-tts would love your thoughts here when you get a moment.