David Woolf

Design engineer

Tempest
Platform

Software orchestration for
large engineering teams

Tempest Recipes planner for the Marketing Website recipe, arranging global resources and deployment environments
Tempest Deploy view showing a grid of deployable application cards with icons, details, and owning teams
Tempest project Deployments view listing recent deployments with their authors, branches, environments, and status
Tempest Resources catalog listing repositories with their teams, owners, types, projects, and tags
Tempest Variables screen for managing environment variables, secrets, and cryptographic assets

The Tempest Developer Platform helps engineering teams manage their growing catalog of deployed software, while also empowering teams without a dev-ops engineer to deploy code safely and effectively.

Table Navigation

Tables regularly display thousands of rows. A combination of structured columns, scannable service icons, tags, and profile pictures assist with taking in content quickly.

Tempest table navigation with structured columns, service icons, tags, and profile pictures

Classification

Large organizations require many signals for classifying both software and teams. In a developer platform, the use of these values in scheduled reporting makes keeping them up to date even more important. Color, iconography, and editing that supports 1 to 1000s of items makes this task realistic.

Tempest classification interface using color, iconography, and bulk editing

Design system

The design system starts with type, color, and iconography. These (along with design tokens) make spinning up high fidelity views in Figma easy, but are only a tiny percentage of the story. With software, it’s common that the “ideal” design system lives in design, while the real design system lives in code. Here, we explore how the design system exists between the two and how to scale a design to thousands of views.