CFIUS logo

U.S. Department of the Treasury

Committee on Foreign Investment in the United States

Secure Investment, Strong America

CFIUS Design System

CFIUS/USWDS Style Guide

USWDS components and utility classes are required first. Homepage pattern classes can be reused where needed.

This page is the live visual reference for CFIUS USWDS patterns.

Use it when updating landing pages so component structure, spacing rhythm, and interaction states stay consistent across the site.

The style guide runs in a dedicated shell with its own header/footer and an expanded review container for component examples.

Pattern A: Official Government Banner

Shell-level component. Keep `grid-container` alignment on both banner header and expanded content so it tracks with site layout.

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website.

Pattern 0: Section Page Header

Use the shared section header wrapper and utility class stack. It now carries a subtle neutral gradient band to improve hierarchy against white content sections, and breadcrumb chrome stays transparent so the band reads cleanly.

Color Tokens

Current token set used by homepage and shared USWDS shell styles.

  • Primary Navy

    #162e51

  • Action Blue

    #005ea2

  • Focus Gold

    #ffbe2e

  • Canvas White

    #ffffff

  • Border Neutral

    #dfe1e2

  • Text Neutral

    #3d4551

Pattern 1: Hero With CTA + Seal

Section

Section Landing Title

One sentence that establishes purpose and user context.

CFIUS logo

Pattern 2: Informational Card Variations

Use shared USWDS card structures for primary tiles and a summary-box variant for supporting side-card treatment.

Variation A: At a Glance (Eyebrow + Text Link)

At a Glance

  • Scope

    Coverage area

    Short summary that helps users scan the section quickly.

  • Guidance

    Reference material

    Use equivalent structure for equivalent content intent.

  • Program

    Operational stream

    Keep card heading, body, and footer spacing consistent.

Variation B: Related Pages (Optional Eyebrow + Mixed CTA)

Variation C: Summary Box Card (Stay Informed)

Frontmatter hooks for landing child cards: card_eyebrow (optional label), card_cta (custom link text).

Pattern 3: Treasury Accent Card Band

Use the OFAC `treas-accent-card` treatment directly for high-priority task links: solid accent fill, Treasury seal background image, Merriweather headline, and the arrow-circle action link while keeping the four-card horizontal layout.

Get Started

Use this for task-first pages where users need a clear next step.

  • Submit a Filing

    Drive the most common primary action with a strong solid-color card and an internal ghost-button CTA.

    Filing Instructions

  • Submit a Tip

    Use the same structure for secondary priority actions without collapsing back into white generic cards.

    Submit a Tip

  • Review FAQs

    Keep typography, padding, and button treatment consistent even when the background color changes.

    Read FAQs

  • Preview a Transaction

    Maintain the same horizontal grid while giving each action enough visual weight to function as a destination card.

    Preview a Transaction

Pattern 4: Narrative + Summary Split

Our Mission

Use the primary column for long-form narrative and program context. Keep measure readable and avoid over-boxing narrative text when flow readability is the priority.

Pattern 5: Recent Actions Feed + Side Summary

Use cfius-home-updates__meta on the metadata row so date and tag stay aligned on a single line.

Recent Actions

Use for dated actions, releases, and notices. Show the latest 3 by default, with compact category tags for fast scanability.

Pattern 6: Feed Cards (Press/Speeches)

Pattern 7: Accordion Stack

Use for dense policy or guidance content where progressive disclosure improves scanability.

Use this panel for concise process expectations and key timing notes.

  • Keep heading labels clear and action-oriented.
  • Use plain language and short support bullets.

Use this panel for checklist-style requirements, linked references, and supporting notes.

Pattern 9: On This Page Rail

Use this component on long landing pages with anchored section headings. Keep rail labels concise and ordered to match reading flow.