CloudSign

CloudSign's site: blue narrates and magenta presses — headings and links in blue, only the download CTA in magenta — with tracking written in em so the whole scale follows when bo…

Back to all styles

Preview

Every style on this site is applied to the same sample page — same headline, same three columns, same footer. Only the stylesheet changes, so every difference you see below belongs to CloudSign, not to the copy.

A live page, not a screenshot — the frame scrolls. Open full preview ↗

At a glance

9tokens
21type steps
2radius steps
2pxspacing base

CloudSign, in one page

Blue narrates, magenta presses. Headings, links and icons are #0d64c9; only the CTA is #f42859. Not painting buttons in the brand colour is the decision this design turns on.

Four things define this site.

  1. It stacks nine @font-face rules just for the circled numerals. NotoSansJP-circled-1 through -9, each with unicode-range narrowed to a single character (U+2460 to U+2468), placed at the head of the body stack. They fill a gap: the self-hosted NotoSansJP-Regular.woff2 subset does not carry circled numerals.
  2. All nine report unloaded, and that is correct. Font requests are zero on both measured pages, because neither page contains a circled numeral. Because unicode-range is narrowed, a page that shows one pulls exactly one file. Do not read unloaded as a load failure.
  3. Tracking is cut in em steps. 0.1em on body, 0.04em on headings, 0.06–0.08em on descriptions, 0.15–0.2em on catch copy. Nine real steps exist: 0.01 / 0.02 / 0.04 / 0.05 / 0.06 / 0.08 / 0.1 / 0.15 / 0.2em. When body drops to 14px at 375px, tracking falls to 1.4px on its own.
  4. The CTA colour is not the brand colour. Magenta #f42859 is reserved for download-type buttons (17 surfaces). Blue #0d64c9 carries headings, links and secondary buttons. The most prominent colour is mapped one-to-one onto the action they most want pressed.

Zero of the site's own CSS custom properties. The 60 detected are all WordPress or Gutenberg (--wp--preset--* 49, WordPress admin 11). Values are written straight into the CSS.

Do's and don'ts

Do

  • Magenta #f42859 for the CTA, blue #0d64c9 for secondary buttons — colour states the order of pressing
  • border-radius: 4px is the one choice, for cards, buttons and tables alike
  • Write tracking in em: 0.1em on body, 0.04em on headings, 0.06em on nav — never px
  • Apply font-feature-settings: "palt" everywhere; it pairs with em tracking
  • Body line-height 1.6, opening to 2.0 only for long passages meant to be read
  • Text #30363e, softening to #697482 then #8897a7
  • Build surface hierarchy in three steps: #fafcfd → #f4f7fa → #eaf0f6
  • Unify shadows on 0 3px 6px rgba(0,0,0,.1); rgba(48,54,62,.1) only for floating elements
  • For circled numerals, put unicode-range-narrowed @font-face rules at the head of the stack

Don't

  • Do not erase the focus ring with outline: none — write outline: 2px solid #0d64c9; outline-offset: 2px
  • Do not use font-weight: 600 — only 400/500/700 exist, so 600 paints at 700
  • Do not write tracking in px — it will not follow when body drops to 14px
  • Do not remove palt — it is on 1,070 elements
  • Do not use three CTA colours — stop at magenta and blue
  • Do not reuse the live font-family unchanged — the stack names no OS font; add "Hiragino Sans" and "Yu Gothic"
  • Do not copy border-radius: 4.8px or 6.112px — they come from an external banner
  • Do not treat NotoSansJP-circled-* as unloaded failures — narrowed unicode-range means they correctly load nothing
  • Do not use #000000 for text — this site uses #30363e

Copy this into your AI builder

Paste it as-is. Every value below was measured from the original site, not guessed.

Translated from the prompt block in the source document. Values unchanged.

Build a pricing plan comparison table following CloudSign's design system.
- Font: Inter, "Noto Sans JP", "Hiragino Sans", "Yu Gothic", sans-serif
- `font-feature-settings: "palt"` across the whole layout
- Tracking in em, never px: body `0.1em`, headings and cells `0.04em`, small labels `0.06em`
- Body 16px / line-height 1.6; section heading 40px / 700 / line-height 1.6
- Weights 400, 500 and 700 only — never 600
- Table header: surface `#eaf0f6`, 14px / 700. Body: surface `#fafcfd`, 14px / 400 / line-height 1.4
- Plan name 24px / 700 / `#0d64c9`; the "recommended" badge is `#49515a` in white 12px
- Under each plan, a "download the deck (free)" button: `#f42859` surface, white text, 16px / 700, padding `22px 0`, radius 4px
- "Talk to us about plans and pricing" is white with `#0d64c9` text and border, same 4px radius
- All radii 4px; shadow only on cards, `0 3px 6px rgba(0,0,0,.1)`
- Text `#30363e`, notes `#8897a7`
- Container 1000px, card gap 16px
- On focus: `outline: 2px solid #0d64c9; outline-offset: 2px`

The specification

Colour paletteRead the full spec

Primary (brand colours)

RoleImplemented valueMeasured
CloudSign Blue#0d64c926 elements of text (top) / 44 (lower), 6 surfaces. Headings, login and sign-up, body links, quote-type secondary buttons
Magenta (primary CTA)#f4285917 surfaces (top) / 8 (lower). Only "see the deck or a demo (free)" and "download the deck (free)"

Do not paint buttons in the service colour. Blue is for what you read (headings, links); magenta is for what you press (requesting the deck). Blue-surfaced buttons do exist, but they belong to contact and quotes — a weaker step on the funnel, always placed below the magenta one.

Do not add a third CTA colour. The ranking collapses.

Neutral

A six-step grey scale with a blue cast. No pure black, no pure grey.

RoleImplemented valueMeasured
Text Primary#30363ethe most common at 171 (top) / 134 (lower). Body and headings
Text Secondary#495158notes (such as the contract-term footnote), 3 elements
Text Tertiary#697482certification labels (19 elements)
Text Muted#8897a7asterisked caveats, REASON 01, running numbers (18 / 12 elements)
Text on Dark#bcc8d6footer links (12 / 13 elements)
Text Inverted Weak#dae3eddrawer headings in the header (42 elements)
Text on Colour#ffffffmagenta CTA and blue-band text (44 / 21 elements)

Surface

SurfaceImplemented valueUse
Surface#fafcfdthe most common, 56 elements. Feature lists and pricing table grounds
Surface Blue#eaf0f6table header rows (30 elements)
Surface Cool#f4f7facertification chips, the "what CloudSign makes possible" block (24 / 11 elements)
Surface Accent#f2f8ffbehind catch copy (2 elements). The bluest surface
Surface Dark#49515aindustry badges on case studies (18 elements), in white
Background#ffffffpageBackground.resolved = rgb(255,255,255), resolved against body

viewportTopByArea returns rgba(0,0,0,0.7) first (area 1,308,952px²), but that is a hidden modal overlay (an emotion-generated class, go1632949049). It is not the ground colour.

Gradients

/* fade the bottom edge of the pricing card */
linear-gradient(#ffffff calc(100% - 16px), rgba(255, 255, 255, 0) 100%);
/* a thin band sitting under a heading */
linear-gradient(#ffffff 0%, #ffffff 117px, rgba(35, 81, 131, 0.2) 0%);

Both are there to erase an edge, not to divide a surface. There is no decorative gradient.

Type scaleRead the full spec

3.1 Japanese typefaces

  • Gothic: Noto Sans JP, self-hosted (/wp-content/themes/cloudsign/web_fonts/NotoSansJP-{Regular,Medium,Bold}.woff2). 400 / 500 / 700 report loaded.
  • Mincho is not used.
  • It carries nine subsets purely for circled numerals (see 3.3).

3.2 Latin typefaces

  • Inter, also self-hosted (Inter_24pt-Regular.woff2 / Inter_24pt-Bold.woff2 / Inter_18pt-Medium.woff2). 400 / 500 / 700 report loaded.
  • 15 visible elements (REASON 01, 5 and other Latin labels). Body copy uses the Japanese stack, with Inter inside it (ahead of "Noto Sans JP") to handle Latin glyphs.
  • Font Awesome 5 Free 900 is loaded (icons). Font Awesome 5 Brands is unloaded.
  • slick (carousel arrows) is loaded as well.

3.3 font-family declarations

The live site's body stack, as measured:

font-family:
  NotoSansJP-circled-1, NotoSansJP-circled-2, NotoSansJP-circled-3,
  NotoSansJP-circled-4, NotoSansJP-circled-5, NotoSansJP-circled-6,
  NotoSansJP-circled-7, NotoSansJP-circled-8, NotoSansJP-circled-9,
  Inter, "Noto Sans JP", sans-serif;

Those nine are declared like this:

@font-face {
  font-family: NotoSansJP-circled-1;
  src: url(https://fonts.gstatic.com/s/notosansjp/v55/…92.woff2) format("woff2");
  unicode-range: U+2460;   /* one character only */
}
@font-face { font-family: NotoSansJP-circled-2; src: url(…91.woff2); unicode-range: U+2461; }
/* … through -9 and U+2468, one character each */

These are not "nine unused files". Because unicode-range is narrowed to one character, a browser will not fetch a single byte if the page has no circled numeral. In measurement, font requests are NotoSansJP-*, Inter_*, fa-solid-900 and slick only — not one circled file.

That is why document.fonts reports unloaded. It is not a failure. The pattern is worth reusing wherever a subsetted body face is missing circled numerals: borrow the relevant Google Fonts subset file, one character at a time.

To take the same stance in new work:

/* self-host the Japanese body face; patch only the missing symbols via unicode-range */
font-family: NotoSansJP-circled-1, /* …-9 */, Inter, "Noto Sans JP",
             "Hiragino Sans", "Yu Gothic", sans-serif;

The live stack puts "Noto Sans JP" immediately before sans-serif, with not one named OS font. If the web font fails, rendering becomes environment-dependent, so add "Hiragino Sans" and "Yu Gothic" (see section 7).

An external widget brings its own stack. The floating deck-request banner (3 elements) is set in "Hiragino Kaku Gothic Pro", "ヒラギノ角ゴ Pro W3", "Hiragino Sans", Meiryo, "MS PGothic", sans-serif. That is not the site's own declaration — do not copy it.

3.4 Size and weight hierarchy

Both html and body are 16px (no 62.5% style shrink). Only at 375px does body drop to 14px.

RoleFontSizeWeightLine heightTrackingNotes
Hero H1Noto Sans JP60px7001.30 (78px)inherited 1.6px#0d64c9. 42px at 375px
Hero leadNoto Sans JP28px7001.401.6px#0d64c9
Heading 1 (lower pages)Noto Sans JP36px7001.007.2px (0.2em)white type inside the blue band
Heading 2 ★Noto Sans JP40px7001.60 (64px)0.04emsection headings (10–13 visible elements)
Heading 2 (tight)Noto Sans JP40px7001.10 (44px)0.04em"five reasons it gets chosen"
Heading 3Noto Sans JP32pxdeclared 600, painted 7001.50–1.601.92px (0.06em)feature headings on lower pages (34 elements)
Heading 4Noto Sans JP24px7001.60 (38.4px)1.6pxcost reduction, contract workflow efficiency
Card titleNoto Sans JP20px7001.60 (32px)0.8px (0.04em)#0d64c9
Long bodyNoto Sans JP18px4002.00 (36px)1.6px (0.089em)line-height 2.0 only on lower-page descriptions (27 elements)
Body ★Noto Sans JP16px4001.60 (25.6px)1.6px (0.1em)the most common, 104 elements
Sub bodyNoto Sans JP14px400 / 5001.60 (22.4px)0.56px (0.04em)the most common on lower pages (92 elements)
TaglineNoto Sans JP14px7001.600.28px (0.02em)catch copy
Nav / UI ★Noto Sans JP12px400 / 7001.000.72px (0.06em)87 elements. Small header links
Top bandNoto Sans JP12px4001.001.8px (0.15em)the thin band at the very top
CaptionNoto Sans JP10px4001.400.4px (0.04em)pricing table footnotes
Label (EN)Inter14px700——REASON 01, POINT 01

It carries only three weights: 400, 500 and 700.

Components and layoutRead the full spec

Buttons

Primary (deck download — the thing they most want pressed)

  • Background: #f42859
  • Text: #ffffff
  • Border radius: 4px
  • Font: 16px / 700 / letter-spacing: 1.6px
  • Padding: 22px 0 — 60px tall, full width of its parent
  • Header variant: 13px / 700 / padding: 0 32px / 38px tall

Secondary (contact, quotes)

  • Background: #0d64c9
  • Text: #ffffff
  • Border radius: 4px
  • Same dimensions. Place it below or beside the magenta one.

Tertiary (outline)

  • Background: #ffffff
  • Text and border: #0d64c9
  • Border radius: 4px (6px for the onboarding-support link alone)
  • The header's sign-up button is this one

Radius is 4px, full stop. 50 measured elements. The 4.8px and 6.112px readings come from the external floating banner and can be ignored. Neither pills nor 0px are used.

Badges

  • Case study industry badge: surface #49515a / white text / 12px / 700 / letter-spacing: 0.48px (0.04em)
  • Pricing plan "recommended": 12px / 700 / letter-spacing: 0.48px

Cards

  • Background: #ffffff or #fafcfd
  • Border radius: 4px (a top-only 4px 4px 0 0 on 18 elements — the upper half of cards split between image and text)
  • Shadow: 0 3px 6px rgba(0, 0, 0, 0.1) (see section 6)
  • Border: none

Tables (pricing, feature comparison)

  • Header row: surface #eaf0f6 / th 14px / 700 / letter-spacing: 0.04em / line-height 1.57
  • Body: surface #fafcfd / td 10–14px / 400 / line-height 1.40
  • Rules in pale grey; border-radius only on the outer corner, 4px

Inputs

Neither measured page has a normal text input (deck requests go through a form on another domain). What follows is recommended, derived from the site's own values.

  • Background: #ffffff
  • Border: 1px solid #dae3ed
  • Border on focus: outline: 2px solid #0d64c9
  • Border radius: 4px
  • Padding: 12px 16px
  • Font size: 16px, tracking inherited from body (1.6px)

Focus rings: the live site erases them with outline: none.

Do not copy that. Focusing an a returns outline-style: none, which leaves keyboard users unable to see where they are. New work must declare outline: 2px solid #0d64c9; outline-offset: 2px (see section 7).

Spacing scale

TokenValueMeasured
XS10px4 gaps
S16px4 gaps, the most common
M25px / 30px / 35px1–2 gaps each
L40px2 gaps
XL50px / 56px0 50px twice, 56px twice
XXL60px2 gaps

Multiples of 5 and multiples of 8 are mixed together (10 / 16 / 25 / 30 / 35 / 40 / 50 / 56 / 60). Since they do not line up, new work may as well settle on multiples of 8 (8 / 16 / 24 / 40 / 56).

Container

  • Max width 1000px (lower-page body column) / 1200px (lower-page wide blocks)
  • The top page is mostly full-width blocks, with inner columns at 454px (two-column), 520px and 390px (mobile equivalent)
  • Full bleed: 1429px (hero)
  • Horizontal padding: 16px (mobile) / 40px (desktop)
Responsive behaviourRead the full spec

Breakpoints

All written as min-width — mobile first. Not a single max-width.

NameWidthNotes
Small phone≥ 320pxthe smallest reference
Phone≥ 375pxthis is where body switches from 14px to 16px
Phone wide≥ 605px
Tablet≥ 767px / ≥ 768px / ≥ 798pxthree close values coexist
Desktop≥ 1230px / ≥ 1280pxthe main split
Wide≥ 1325px

There is a declaration left as screen and (min-width: 768px) and (min-width: 1280px) — nested, effectively 1280px. Untidy, but harmless.

Root size

  • html is fixed at 16px at all four widths
  • body is 16px at 1440 / 1200 / 834px and 14px at 375px. Line height stays 1.6 (25.6px → 22.4px), and because tracking is 0.1em it follows on its own from 1.6px to 1.4px
  • Headings follow too: h1 60px → 42px, h2 40px → 23px (tracking 1.6px → 0.92px, still 0.04em)

Dropping the body size alone makes tracking, line height and headings follow proportionally. That works because everything is written in em and ratios. Convert it to px and the whole cascade breaks.

Touch targets

  • The header CTA is 38px tall, under the WCAG 44px. Guarantee at least 44px in new work.
  • CTAs inside body copy are 60px tall — plenty.

Font size handling

  • The 40px desktop h2 becomes 23px at 375px (about 58%)
  • 16px body becomes 14px at 375px. Never let it go below 14px.

Drop-in CSS variables

The same values as a theme block. Add the class to <body> and the site repaints.

body.theme-cloudsign {--page-bg: #ffffff;
  --page-bg-gradient: none;
  --text-color: #30363e;
  --heading-color: #30363e;
  --link-color: #e80c40;
  --link-hover-color: #b80933;
  --border-color: #dadbdc;
  --card-bg: #ffffff;
  --card-shadow: 0 1px 2px rgba(48,54,62,0.06);
  --card-hover-shadow: 0 6px 18px rgba(48,54,62,0.12);
  --header-bg: #30363e;
  --header-text-color: #ffffff;
  --header-shadow: none;
  --footer-bg: #ffffff;
  --footer-text-color: #6e7277;
  --button-bg: #f42859;
  --button-text-color: #000000;
  --button-hover-bg: #de0b3e;
  --button-border: none;
  --button-border-radius: 4.8px;
  --button-secondary-bg: #f3f3f3;
  --button-secondary-text-color: #30363e;
  --button-secondary-hover-bg: #e6e7e8;
  --button-secondary-border: 1px solid #dadbdc;
  --prompt-bg: #f5f5f5;
  --prompt-text-color: #30363e;
  --base-font: var(--font-helvetica);
  --heading-font: var(--font-inter);
  --card-border-radius: 4.8px;
}

Download theme.css

Visually close to

Measured with a deterministic colour + geometry comparison across 958 styles. Not a hand-picked list.

Where this came from

Source document
jp/design-md/cloudsign/DESIGN.md · 15.8 KB
Repository
kzhrknt/awesome-design-md-jp
Licence
MIT
Translation
Translated from the original Japanese source document. Tokens, hex values and numbers are carried over unchanged.

Source text is reproduced under its original licence. Tokens, similarity scores and page structure are ours.