attestation: constructed — the only constructed record in the corpus. It names something assembled here, not a movement anyone declared. This announcement bar is the register’s own furniture.
Visual language · Market convention
Modern SaaS
The commercial default of contemporary B2B software marketing. Measurement finds no characteristic hue, radius or ground — what recurs is one restrained accent and a page that shows the product.
One saturated accent, reserved for the primary action — the one structural habit every measured site shares. Sources 3 artefacts · 3 documents — as occurrence Confidence high A yellow primary accent, rgb(255,224,27). Refutes "indigo or violet" as characteristic. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.A green primary accent, rgb(0,98,57). A second hue family, in a second sector. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.An indigo accent, rgb(94,106,210) — the hue the v1.1 text names. Recorded so the deletion is visibly a NARROWING and not a reversal: indigo occurs, it is simply not required. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization. No hue is characteristic; this page’s amber was chosen against both the falsified indigo and Aesthetary’s own violet. Both targets clear 24×24 px. Sources No evidence recorded yet
The hero screenshot shows the buyer the product, so it shows ours: this record, in the corpus browser. The convention it performs is conversion practice, not grammar, and was demoted from canonical on Mailchimp’s counter-example. Sources 1 artefact · 1 document — as occurrence Confidence high An illustration-led hero on an unquestionably SaaS product. This is the observation that demoted the record's last canonical constraint. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
The logo-bar slot — carrying, instead of customers, the 8 sites measured on 2026-09-20
- Linear
- Stripe
- Notion
- Salesforce
- Mailchimp
- Supabase
- Atlassian
- Ramp
A falsification sample: it can refute a universal — one yellow accent refutes “the accent is indigo” — and it cannot establish prevalence. Nothing on this page says most SaaS sites do anything. The names are typeset, not their logos. Sources No evidence recorded yet
Build with it
A starting grammar for a Modern SaaS marketing page: a neutral ground, one saturated accent kept for the primary action, sans-serif in two weights, one radius, one elevation step, an 8px rhythm, and a hero that shows the product. None of it is required; all of it is recognisable.
Web translation marks our choices for the screen. Not specified by the source marks what the sources leave open. Everything else is a rule from the record below.
The same system is in the brief (Build → Brief) and in the structured data.
Colour
- ground#FFFFFF
- band#F7F7F8
- ink#0F1115
- muted#5B6270
- line#E6E7EB
- accent#F5A524
- accent-ink#1A1204
Neutral everywhere; the accent only where the primary action is. Any hue will do.
The rules behind it
- Seen in the workOne saturated accent, reserved for the primary action. No hue is characteristic: choose freely. From the work itself (colour)
- Our readingMost often a near-white ground; dark-first also occurs, and neither is required. From our reading (colour)
- Not part of the aestheticSecondary text must still meet 4.5:1. From standard practice (colour)
- Not part of the aestheticA gradient field is background only and never the contrast source for text. From standard practice (colour)
- Web translationUse amber as the accent. The hue is free; this page’s amber was chosen against the falsified indigo and against Aesthetary’s own violet. From the work itself (colour)
Typography
Ship faster.
Sans-serif, two weights, tight tracking at display size.
The rules behind it
- Our readingSans-serif throughout, two weights, tight tracking on display sizes. From our reading (typography)
- Web translationSet it in Geist at 400 and 600. Sans-serif identifies nothing on its own; the measured sites mostly use their own faces, so the face is ours to choose. From our reading (typography)
Layout
8 · 16 · 24 · 48 · 88. Marketing pages get the large steps.
The rules behind it
- Our readingSection rhythm from a consistent base unit, commonly 4 or 8 px. From our reading (layout)
- Seen in the workSpacing comes from a scale on a fixed base unit (8 px at Atlassian), smaller steps kept for compact UI. From the work itself (density)
- DocumentedDensity belongs to product; marketing pages are the spacious ones. From a documented finding (density)
- Web translationCentre a 1140px container and space sections 88px apart. Both are multiples of the 8px unit; the large section step is the marketing side of the density pair. From our reading (layout), a documented finding (density)
Shape
One radius, one elevation step.
The rules behind it
- Our reading · disputedOne consistent corner radius across components; no magnitude is characteristic. From our reading (interface)
- Our reading · disputedExactly one elevation step. From our reading (interface)
- Web translationUse 10px. Any single radius satisfies the rule; 10px is the room’s. From our reading (interface)
Imagery
YOUR PRODUCT’S REAL INTERFACE GOES HERE.
The hero shows the product. A logo bar carries real customers or nothing.
The rules behind it
- Our reading · disputedPut the product interface in the hero, not photography or illustration. From our reading (imagery)
- Web translationShow your own product as it is, and put only real customers in a logo bar. The screenshot and the logo bar are proof devices; a staged interface or an invented logo is a false claim, not a style. From how you recognise it, our reading (imagery)
- Not specified by the sourceThe sources do not specify illustration or photography outside the hero. Use them only if the product needs them; do not treat them as part of the register.
Components
For marketing pages only: product and dashboard UI are outside the record until studied. The accent is used once here, on the one primary action.
The rules behind it
- Seen in the workReserve the one saturated accent for the primary action. From the work itself (colour)
- Seen in the workOne primary call to action per page or area. From the work itself (hierarchy)
- Not part of the aestheticInteractive targets at least 24 by 24 CSS px. From standard practice (interface)
- Web translationSet every other action as a white outline button. With the accent reserved, a secondary action needs a shape that is clearly a button and clearly not the primary one. From the work itself (colour), the work itself (hierarchy)
- Our reading · disputedOne consistent corner radius across components. From our reading (interface)
- Our reading · disputedExactly one elevation step: large blur, low opacity, small downward offset. From our reading (interface)
- Seen in the workRaised elevation used for emphasis is limited to one section or focal point. From the work itself (hierarchy)
- Our reading · disputedOne consistent corner radius across components. From our reading (interface)
- Not part of the aestheticSecondary text must still meet 4.5:1. From standard practice (colour)
- Web translationKeep the field’s line darker than the card hairline. A field has to be found without a shadow: the muted grey line is 6.1:1 on white, where the card hairline is too faint for a control. From standard practice (colour), our reading (interface)
- Seen in the workOne primary call to action per page or area. From the work itself (hierarchy)
- Web translationPut the area’s one accent button at the right of the bar. The bar is an area; its primary action takes the accent and nothing else in it does. From the work itself (colour), the work itself (hierarchy)
Motion
Colour changes in 150 ms, the toolchain default. Nothing fades in on scroll: the record leaves that open, and open is not permission.
The rules behind it
- DocumentedMotion identifies nothing: transitions and animations are near-universal on the web. From a documented finding (motion)
- Seen in the workUse motion for clarity in core components; branded experiences may be richer. From the work itself (motion)
- Seen in the work150 ms is Tailwind’s default transition, a toolchain default rather than a stylistic choice. From the work itself (motion)
- DocumentedHandle prefers-reduced-motion; about a third of pages do. From a documented finding (motion)
- Not specified by the sourceScroll reveals and entrance animation are left open by the record. Add none by default; left open is not permission. From motion area
Marketing, not product
Spacious here; compact behind the login.
The rules behind it
- DocumentedThe record covers the marketing-site presentation of business-software vendors; product and dashboard UI are outside it. From a documented finding
- DocumentedProduct pages aim for compact density; marketing pages for spaciousness. From a documented finding (density)
01 — Learn
What is this register, and why does it look like everything else?
canonical constraints, after adjudication
There is no rule here whose breach puts a page outside the category. That is the finding, not a gap — and it is exactly what the argument below predicts.
The argument it makes
Signals category membership and operational competence by looking like the other credible products in the category. Legibility of the offer matters more than distinction from competitors.
It assumes a buyer who is comparing several vendors and reads unfamiliarity as risk.
Sources No evidence recorded yet
What it pays
- Distinctiveness
- Memorability
- Any claim to authorship
How you recognise it
A neutral ground — most often near-white, sometimes near-black — carrying one saturated accent reserved almost exclusively for the primary action, rounded cards under soft low-opacity elevation, and a hero usually occupied by a screenshot of the product itself. The screenshot hero plus the customer logo bar places a page in B2B software within a second, but that is a MARKETING signature rather than a visual grammar, and neither element is required: Mailchimp leads with illustration and is unquestionably SaaS. Sans-serif type and rounded corners are far too common to identify anything, and direct measurement finds no characteristic accent hue and no characteristic radius.
Sources No evidence recorded yet
Three rounded cards under exactly one elevation step, on one radius, on an 8px rhythm: the register’s grid, performed and annotated as convention. The radius and the rhythm recur partly because the dominant toolchain ships them, which the record states rather than hides. Sources No evidence recorded yet Sources 2 artefacts · 4 documents — as occurrence, as generalisation Confidence high, medium Modal radius 4px then 6px, below the deleted 8–16px range — on the reconnaissance's most-cited reference pole. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.Modal radius 4px alongside 20px. A second independent refutation, at an ordinary large vendor rather than a design-press favourite. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.GENERALIZATION ABOUT THE TOOLCHAIN, NOT ABOUT THE REGISTER. Two pieces of primary vendor documentation establish that a radius scale and a dark block are shipped defaults. That licenses the confound statement in the rule note; it does NOT license any claim about what SaaS sites look like. Confidence medium because a shipped default constrains what is easy, not what is chosen — and shadcn's own 10px default appears in none of the eight measured sites. Sources No evidence recorded yet
Motion · left open
The section that refused to fade in
This is where a scroll-triggered fade-and-rise would go, and it would identify nothing. Documented: transitions and animations appear on 85% and 77% of mobile web pages (2022), so a page that moves is not thereby this register. The motion area here is left open, and that is not permission. So this page refuses the scroll reveal: you scrolled to this sentence and nothing moved. Sources No evidence recorded yet
3 Elements linked
What carries the look
| Typography | Page set in Geist + Geist Mono. |
|---|---|
| Colorcarries the look |
as built |
| Compositioncarries the look | |
| Imagery | Nothing linked yet |
| Surfaces | |
| Motion | Nothing linked yet |
| Motifs & Symbols | Nothing linked yet |
| Techniques | Nothing linked yet |
02 — Build
The accent, falsified
The earlier record said “indigo or violet accent”. The measurement did not support it, and the freedom is now its own rule. The 8 measured sites, as named hue categories: the chips illustrate a category, not a sampled value. Sources 3 artefacts · 3 documents — as occurrence Confidence high A yellow primary accent, rgb(255,224,27). Refutes "indigo or violet" as characteristic. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.A green primary accent, rgb(0,98,57). A second hue family, in a second sector. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.An indigo accent, rgb(94,106,210) — the hue the v1.1 text names. Recorded so the deletion is visibly a NARROWING and not a reversal: indigo occurs, it is simply not required. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Lineardark groundindigo/violet accent
- Stripelight groundindigo/violet accent
- Notionlight groundblue accent
- Salesforcelight groundno saturated accent
- Mailchimplight groundyellow accent
- Supabasedark groundgreen accent
- Atlassianlight groundblue accent
- Ramplight groundyellow accent
Rules 18 · none canonical
What it can hand a designer
By area, each labelled with what kind of claim it is. Nothing below is a canonical constraint: the record holds none. The contrast rules are the ones this page is graded against: its secondary text runs at 6.1:1 on white, where the register’s characteristic grey-on-white routinely fails.
Layout · Our reading
Section rhythm from a consistent base unit, commonly 4 or 8 px.
Sources No evidence recorded yet
Typography · Our reading
Sans-serif throughout, two weights, tight tracking on display sizes.
No grade recorded
Sources No evidence recorded yet
Color · Our reading
Most often a near-white ground. The register also occurs dark-first, and neither ground is required.
Sources 1 artefact · 1 document — as occurrence Confidence high Computed body background rgb(8,9,10). Refutes the near-white ground as a property. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Color · Not part of the aesthetic
Secondary text must still meet 4.5:1. The characteristic grey-on-white secondary text is the register's most common accessibility failure.
Sources No evidence recorded yet
Color · Not part of the aesthetic
Aurora field is background only and may never be the contrast source for text.
No grade recorded
Sources No evidence recorded yet
Color · Seen in the work
One saturated accent, reserved for the primary action rather than for decoration. NO HUE IS CHARACTERISTIC — choose freely.
Sources 3 artefacts · 3 documents — as occurrence Confidence high A yellow primary accent, rgb(255,224,27). Refutes "indigo or violet" as characteristic. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.A green primary accent, rgb(0,98,57). A second hue family, in a second sector. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.An indigo accent, rgb(94,106,210) — the hue the v1.1 text names. Recorded so the deletion is visibly a NARROWING and not a reversal: indigo occurs, it is simply not required. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Imagery · Our reading · disputed
The hero is usually occupied by the product interface itself rather than by photography or illustration.
No grade recorded
Sources 1 artefact · 1 document — as occurrence Confidence high An illustration-led hero on an unquestionably SaaS product. This is the observation that demoted the record's last canonical constraint. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Interface · Not part of the aesthetic
Interactive targets at least 24 by 24 CSS px.
Sources No evidence recorded yet
Interface · Our reading · disputed
One consistent corner radius across components. No magnitude is characteristic.
Sources 2 artefacts · 4 documents — as occurrence, as generalisation Confidence high, medium Modal radius 4px then 6px, below the deleted 8–16px range — on the reconnaissance's most-cited reference pole. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.Modal radius 4px alongside 20px. A second independent refutation, at an ordinary large vendor rather than a design-press favourite. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.GENERALIZATION ABOUT THE TOOLCHAIN, NOT ABOUT THE REGISTER. Two pieces of primary vendor documentation establish that a radius scale and a dark block are shipped defaults. That licenses the confound statement in the rule note; it does NOT license any claim about what SaaS sites look like. Confidence medium because a shipped default constrains what is easy, not what is chosen — and shadcn's own 10px default appears in none of the eight measured sites.
Interface · Our reading · disputed
Exactly one elevation step. Large blur, low opacity, small downward offset.
No grade recorded
Sources No evidence recorded yet
Motion · Seen in the work
Atlassian's design system asks core components to use motion for clarity, while branded experiences can use richer, more expressive motion.
Sources 1 document Overview — Motion — Atlassian Design
Motion · Seen in the work
Tailwind's default transition duration is 150 ms; treating that value as a toolchain default rather than a stylistic choice is Aesthetary's reading.
Sources 1 document transition-property — Tailwind CSS
Motion · Documented · Source attached
Transitions and animations are near-universal on the web (85% and 77% of mobile pages in 2022), so their presence does not identify this register.
Sources 1 document CSS | 2022 | The Web Almanac by HTTP Archive
Motion · Documented · Source attached
Reduced-motion handling is common: prefers-reduced-motion appears on about a third of pages.
Sources 1 document CSS | 2022 | The Web Almanac by HTTP Archive
Hierarchy · Seen in the work
One primary call to action per page or area marks the most important action.
Sources 1 document Button — Usage — Atlassian Design
Hierarchy · Seen in the work
Raised elevation used for emphasis is limited to one section or focal point.
Sources 1 document Overview — Elevation — Atlassian Design
Density · Seen in the work
Spacing comes from a scale on a fixed base unit (8 px at Atlassian), with smaller steps reserved for compact UI.
Sources 2 documents Overview — Spacing — Atlassian DesignTheme variables — Tailwind CSS
Density · Documented · Source attached
GitHub's Primer aims for a fast, compact product experience, and a draft Primer guideline outline pairs density on product with spaciousness on marketing pages.
Sources 2 documents Interface Guidelines: proposed IA (primer/design docs/content.md)Getting started — Primer Product UI
Ruled out, or left open by the sources
Surface · Supporting · Not specified by the source
No characteristic surface treatment. Flat fills and occasional subtle noise both occur; neither identifies the register, so an agent may choose.
Motif · Outside this language
The register has no motif vocabulary.
Technique · Outside this language
Screen-native; no production technique is implicated.
Form · Outside this language
No three-dimensional organisation.
03 — Evidence
What stands behind it
3 live sites and 20 documents stand behind 18 of this record’s 42 claims. The evidence problem here is not rights but drift: the artefacts are websites that change under measurement, and each is recorded as it stood on the measurement date.
Partly sourced. 22 sources attached.
Build guidance: 25 rules recorded. It says what usable material is recorded, never how well it is evidenced.
Not researched yet: Typeface guidance, Moving it to screen. Unresearched is not permission.
Neither is a free hand: an area research has not reached is not permission to decide on the language’s behalf.
Scope: The marketing-site presentation of contemporary business-software vendors. GitHub keeps a separate Primer Brand system for marketing sites and aims for compact product UI, and a draft Primer guideline pairs density on product with spaciousness on marketing; Atlassian keeps separate brand guidance for marketing. The record is therefore scoped to marketing pages; product and dashboard UI are outside it until studied. The name and the grouping into one register are Aesthetary's construction, not an attested movement.
The measured sites
Atlassian marketing site 2026
Not shown here — visit the live site
What it supports · 1 claim
- Occurrence · Counter example — A radius rule — our reading · disputed
Modal radius 4px alongside 20px. A second independent refutation, at an ordinary large vendor rather than a design-press favourite. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Occurrence · Counter example — A radius rule — our reading · disputed
Linear marketing site 2026
Not shown here — visit the live site
What it supports · 2 claims
- Occurrence · Exemplar — A colour rule — seen in the work
An indigo accent, rgb(94,106,210) — the hue the v1.1 text names. Recorded so the deletion is visibly a NARROWING and not a reversal: indigo occurs, it is simply not required. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization. - Occurrence · Counter example — A colour rule — our reading
Computed body background rgb(8,9,10). Refutes the near-white ground as a property. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Occurrence · Exemplar — A colour rule — seen in the work
Mailchimp marketing site 2026
Not shown here — visit the live site
What it supports · 2 claims
- Occurrence · Counter example — A colour rule — seen in the work
A yellow primary accent, rgb(255,224,27). Refutes "indigo or violet" as characteristic. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization. - Occurrence · Counter example — An imagery rule — our reading · disputed
An illustration-led hero on an unquestionably SaaS product. This is the observation that demoted the record's last canonical constraint. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Occurrence · Counter example — A colour rule — seen in the work
Stripe marketing site 2026
Not shown here — visit the live site
What it supports · 1 claim
- Occurrence · Counter example — A radius rule — our reading · disputed
Modal radius 4px then 6px, below the deleted 8–16px range — on the reconnaissance's most-cited reference pole. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Occurrence · Counter example — A radius rule — our reading · disputed
Supabase marketing site 2026
Not shown here — visit the live site
What it supports · 1 claim
- Occurrence · Counter example — A colour rule — seen in the work
A green primary accent, rgb(0,98,57). A second hue family, in a second sector. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
- Occurrence · Counter example — A colour rule — seen in the work
Frequently asked questions
The bottom-of-page FAQ is the register’s furniture, performed: every answer is one of the measurement’s corrections, with its provenance attached.
Is the accent indigo or violet?
No hue is characteristic — choose freely. The structure is what survives: every measured site reserves one saturated colour for the primary action. Indigo/violet appeared on two of eight sites; blue, yellow, green and none-at-all covered the rest. Sources 3 artefacts · 3 documents — as occurrence Confidence high A yellow primary accent, rgb(255,224,27). Refutes "indigo or violet" as characteristic. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.A green primary accent, rgb(0,98,57). A second hue family, in a second sector. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.An indigo accent, rgb(94,106,210) — the hue the v1.1 text names. Recorded so the deletion is visibly a NARROWING and not a reversal: indigo occurs, it is simply not required. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Must the ground be near-white?
It is the most common case, not a requirement: six of eight measured sites are light, two are dark — and the 2026 reconnaissance asserts the opposite ratio, which is itself information about how stable this register is. Sources 1 artefact · 1 document — as occurrence Confidence high Computed body background rgb(8,9,10). Refutes the near-white ground as a property. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Is the product-screenshot hero required?
No — and this was the most consequential demotion in the record. Mailchimp leads with illustration and is unquestionably SaaS, so the screenshot hero is conversion practice, not visual grammar. Sources 1 artefact · 1 document — as occurrence Confidence high An illustration-led hero on an unquestionably SaaS product. This is the observation that demoted the record's last canonical constraint. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.
Is there a characteristic corner radius?
No magnitude is characteristic — the once-recorded 8-to-16px span was a slice of a toolchain default scale, and three of eight measured sites sit at or below 4px. What survives is internal consistency: one radius per site. Sources 2 artefacts · 4 documents — as occurrence, as generalisation Confidence high, medium Modal radius 4px then 6px, below the deleted 8–16px range — on the reconnaissance's most-cited reference pole. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.Modal radius 4px alongside 20px. A second independent refutation, at an ordinary large vendor rather than a design-press favourite. OCCURRENCE, AND IT STAYS OCCURRENCE. One site shows what one site does. Eight sites cannot establish prevalence, and no link in this record claims generalization.GENERALIZATION ABOUT THE TOOLCHAIN, NOT ABOUT THE REGISTER. Two pieces of primary vendor documentation establish that a radius scale and a dark block are shipped defaults. That licenses the confound statement in the rule note; it does NOT license any claim about what SaaS sites look like. Confidence medium because a shipped default constrains what is easy, not what is chosen — and shadcn's own 10px default appears in none of the eight measured sites.
Does Inter dominate the register?
No. Six of the eight measured sites use a proprietary or commissioned face; only two use Inter. Sans-serif throughout is true everywhere and identifies nothing. Sources No evidence recorded yet
Often confused with
Aesthetic
Flat Design
Seen from Flat Design: zero depth versus soft elevation and rounded cards.
Aesthetic
Utilitarian
Seen from Utilitarian: both neutral; SaaS spends to look credible, this spends nothing.
Element
Glassmorphism
Requires something behind the glass, so the palette constraint runs page-wide
Use it
See where its rules collide with another Aesthetic’s, or take every rule with a checklist for grading the result.
For machines: data/v1/modern-saas.json · prompt/modern-saas.md · Request deeper research
Contribute
Contributing and commenting need JavaScript. Nothing else on this page does.
Work made in this style: a poster, a page, a type setting. Every submission is reviewed before it appears.
Nothing here yet.
Comments
No comments yet.