Sublime Text — business-account sign-in

---
version: alpha
name: Sublime Text — business-account sign-in
colors:
  primary: '#3C78B4'
  surface: '#FFFFFF'
  text: '#444444'
  muted: '#777777'
typography:
  primaryRole:
    fontFamily: Lato, Arial, sans-serif
    fontSize: 34px
    fontWeight: 400
    lineHeight: 54px
  supporting:
    fontFamily: Lato, Arial, sans-serif
    fontSize: 16px
    fontWeight: 400
    lineHeight: 25.6px
omitted:
- section: spacing
  reason: Per-reference dimensions and observed composition are given in Layout; no
    global scale is inferred.
- section: rounded
  reason: Observed shape roles are described in Shapes without inventing a global
    radius scale.
- section: components
  reason: Reference-specific components are described in prose rather than an inferred
    implementation API.
---

## Overview

A restrained business-account sign-in page uses a gray brand header, a plain login heading, explanatory account guidance and labeled email/password fields in an outlined group.

Captured from https://www.sublimehq.com/store/login at 2026-10-16T06:08:52.652539+00:00. This is a full-page capture.

## Colors

primary: `#3C78B4`; surface: `#FFFFFF`; text: `#444444`; muted: `#777777`. These values describe observed interface roles, not a complete brand palette. Keep text and surfaces distinct; do not spread the primary accent across every element.

## Typography

- h1 “Login”: Lato, Arial, sans-serif, 34px, weight 400, line height 54px.
- p “Accounts are only used for business subscriptions. Personal licen”: Lato, Arial, sans-serif, 16px, weight 400, line height 25.6px.
- p “Forgot your password? Recover Account”: Lato, Arial, sans-serif, 13.6px, weight 400, line height 21.76px.
- p “Woollahra, Sydney.”: Lato, Arial, sans-serif, 16px, weight 400, line height 25.6px.
- a “”: Lato, Arial, sans-serif, 16px, weight 400, line height 25.6px.

The primary token describes a sampled heading or link, not an inferred global type scale. Use the accompanying composition to establish hierarchy rather than applying one size everywhere.

## Layout

Keep the Login heading and account-purpose explanation above a two-column label-and-input form. Place account recovery below the password row and a compact Login button below it. The source explicitly distinguishes business subscriptions from personal licenses; preserve that contextual guidance.

Desktop image: 1440 × 1000px at a 1440px viewport. Mobile evidence: 390 × 844px at a 390px viewport. Measured document widths were 1440px desktop and 480px mobile.

At 390px the source maintains a wide form and explanatory line, producing horizontal overflow. The full desktop form is captured cleanly; mobile limitations are evidence, not responsive recommendations. Stack labels and inputs in an adaptation.

## Elevation & Depth

Use nearly flat light-gray and white surfaces with thin borders. There is no prominent decorative illustration or floating authentication card.

## Shapes

Text fields and submit control are conventional rectangles. The heading sits on a small pale gray highlight, while header links use simple text.

## Components

A restrained business-account sign-in page uses a gray brand header, a plain login heading, explanatory account guidance and labeled email/password fields in an outlined group. Preserve the selected reference's hierarchy and reading order. This is one visible state: hover, focus, validation, menus, downloads and successful transactions are untested unless explicitly described. No credentials were entered, forms submitted, accounts created or purchases made. Any customer statements, pricing or performance claims visible in the source are source-owned copy, not independently verified facts.

## Do's and Don'ts

- Do preserve the specific spacing relationships, content grouping and type hierarchy described above.
- Do provide accessible focus indicators and responsive controls in a new implementation; this is a recommendation, not a claim that every source state passed testing.
- Do use original content and substantiated claims when adapting the pattern.
- Don't reproduce observed source overflow, clipping or ticker-spacing defects.
- Don't infer animation timing, validation behavior or completed transactions from a static frame.