Docs Workspace

Keep product docs, decisions, owners, freshness, and related projects visible in one shared workspace. The screen connects Home and Recent so product teams can find the “New doc” action while checking documents and updated 7d.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Q4 planning brief and Enterprise permissions spec, rather than an empty visual shell.

Docs Workspace
Use this template in Figr

Template facts

Screen

Workspace

Primary action

New doc

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “New doc” action without losing sight of documents, updated 7d and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New doc is clearly available where the task happens.
  • Main view: Home keeps the starting point obvious.
  • Connected view: Recent supplies nearby context.
  • Metric: Documents is visible with a meaningful value.
  • Another signal: Updated 7d helps people judge what to do next.
  • Representative record: Q4 planning brief makes the example specific.
  • Second record: Enterprise permissions spec shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading home without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for recent; clarify who can continue.
  • Success after choosing New doc; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Home → Recent → New doc → Review outcome

Patterns used

Workspace, Home, Recent, Projects, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Q4 planning brief with Enterprise permissions spec. Make documents clear, then use updated 7d to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New doc” action. The happy path alone is not enough.

Related UI examples: Team Calendar, Comments & Mentions, Product Roadmap.

Start from this in Figr

Design a docs workspace screen for our existing software product. Use our real design-system tokens, components and product language. Show Home and Recent, include believable records such as Q4 planning brief, and make new doc easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr