Internal design system

Font size playground

A restrained responsive type system for Help Center pages. Sizes remain readable without turning documentation into marketing-scale display typography.

Viewport system

Mobile0–767px
Tablet768–1023px
Desktop1024–1535px
Large screen1536px+

Responsive scale

Values are pixels. The rendered specimen automatically follows the current viewport.

Headings: Lato · Body/UI: Nunito Sans
RoleExampleMobileTabletDesktopLargeColorUsage
DisplayAa32px40px48px52pxPrimaryRare campaign or primary landing statement
Page titleAa28px32px36px40pxPrimaryOne H1 per page
Section titleAa22px24px26px28pxPrimaryMajor H2 content sections
Subsection titleAa18px19px20px21pxPrimaryH3 and card-group headings
FAQ questionAa17px18px18px19pxPrimaryExpandable questions and prominent prompts
Lead bodyAa17px18px18px19pxPrimary 85%Introductory copy beneath a page title
BodyAa16px17px17px18pxPrimary 80%Articles, lists, steps, and long-form explanations
DescriptionAa15px16px16px17pxSecondaryCards, summaries, excerpts, and supporting copy
BlockquoteAa17px18px19px19pxPrimaryQuoted guidance and editorial emphasis
UI textAa14px15px15px16pxPrimaryNavigation, buttons, inputs, and interface text
LabelAa12px13px13px14pxSecondaryCategory eyebrows, field labels, and compact grouping text
CodeAa14px15px15px15pxPrimaryInline code and technical examples
CaptionAa13px13px13px13pxSecondaryDates, captions, legal notes, and tertiary metadata

Live specimens

Review hierarchy, density, and wrapping at the current viewport—not size in isolation.

Display

.fxr-type-display

Test with clarity

Page title

.fxr-type-page-title

Product guides

Section title

.fxr-type-section-title

Available guides

Subsection title

.fxr-type-subsection-title

Account management

FAQ question

.fxr-type-question

How do I review a session?

Lead body

.fxr-type-body-lead

Replay historical markets and build confidence from evidence.

Body

.fxr-type-body

Use historical sessions to test decisions before risking live capital.

Description

.fxr-type-description

A concise explanation that adds context without competing with the title.

Blockquote

.fxr-type-blockquote

A repeatable process is more useful than a lucky result.

UI text

.fxr-type-ui

Search the Help Center

Label

.fxr-type-label

PRODUCT GUIDE

Code

.fxr-type-code

risk_per_trade = account_size * 0.01

Caption

.fxr-type-caption

Updated August 31, 2026

Rich-text flow

Product guide

Build a repeatable review process

Use one consistent workflow to compare sessions, identify recurring decisions, and refine the rules behind your strategy.

Review the evidence

Supporting context uses the secondary text color to stay distinct from the main reading flow.

Start with the same checkpoints after every test. This keeps the analysis focused and makes results easier to compare over time.

  • Confirm the market context and session.
  • Compare the planned setup with the executed trade.
  • Record one change to test in the next replay.
A useful review ends with a rule you can test again.

Use session_notes for concise observations, then link to the full journal entry.

Example content only · Internal typography review