Template Gallery

Browse reusable templates by category, team, popularity, and last updated date before creating a new document or project. This example brings Featured and Product together so content and product teams can find the next task without losing context.

It includes representative records such as Product requirements doc and Launch checklist. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Template Gallery
Use this template in Figr

Template facts

Screen

Table

Primary action

Create template

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to create template while keeping templates, featured and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Featured gives users an obvious place to start.
  • Supporting view: Product keeps the related context close.
  • Primary action: Create template stays visible when people need it.
  • First signal: Templates shows a useful value (186).
  • Second signal: Featured gives additional context (12).
  • Sample record: Product requirements doc.
  • Next record: Launch checklist.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Featured → Product → Create template → Review outcome

Patterns used

Table, Featured, Product, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to featured and product. People need to distinguish Product requirements doc from Launch checklist. Keep templates visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create template”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Editorial Review, Folder Permissions, Publishing Workflow.

Start from this in Figr

Design a template gallery screen inside our existing product. Use our current components, tokens and content language. Include Featured and Product views, credible records like Product requirements doc, and a clear “Create template” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr