Consistent actions between document and project layouts

[allanlasser]

Feedback:

It's a bit challenging to find the projects that have been shared with me, have to remember where to click each time. New version looking great, btw!

---

Fork of #840

Users are perceiving sidebars as application level UI, not view-specific UI, and changes to the sidebars disorient them.

We should have a consistent ordering, labelling, and positioning for elements in each sidebar on in Document, Project, and Add-On layouts. In other words, if a user is used to finding an action in a particular place, it should appear there.

We should be mindful that these sidebars are either appearing in the presence of a selectable list of documents, or in the presence of a document viewer. Sidebars aren't currently present when dispatching add-ons.

Actions Sidebar

The right-hand sidebar should provide groups of actions that are consistently placed in the presence of a document browser or document viewer.

Proposed order:

1. Upload Documents
2. Document Actions
   1. Share & Embed (Make name consistent)
   2. Edit Metadata
   3. Edit Tags & Data
   4. Edit Projects
   5. Reprocess
   6. Delete
3. Project Actions (when on a project)
   1. Share & Embed Project
   2. Edit Project Data
   3. Delete Project
   4. Collaborators (Group)

Navigation Sidebar

The left-hand sidebar should be globally consistent between documents, projects, and add-on routes. Each one should be a collapsable group, with a link to the top-level browser.

Proposed Order:

1. Documents (Explore Public Documents)
   1. Your Documents
   2. Your Public Documents
   3. Your Private Documents
   4. Org's Documents
   5. Pinned Documents…
2. Projects (Explore Public Projects)
   1. Your Projects
   2. Shared With You
   3. Pinned Projects…
3. Add-Ons
   1. Featured
   2. Pinned Add-Ons…

[allanlasser]

@morisy I want to flag a complication I encountered while working this. If we are moving towards a globally-consistent left sidebar, then users will lose this dependable navigation in the viewer. The viewer uses the left sidebar to present document-specific links (its projects, tags and notes). This was one of the reasons I thought a Figma pass might be useful here—these changes could have large impacts on several different page designs and it'd be good to be able to consider them "in whole". We may also want to consider alternative global navigation solutions.

[eyeseast]

We might prioritize adjusting language first and layouts second. The language changes here are pretty straightforward.

We can also standardize the search and project layouts without changing the viewer.

[allanlasser]

Yeah, I've decided to not touch the viewer in this pass and see if the changing sidebar still confuses people—then we can solve in a more targeted way.