@adobe/spectrum-design-data 3.3.0-beta.0 → 3.3.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (81) hide show
  1. package/components/accordion.json +15 -54
  2. package/components/action-bar.json +9 -23
  3. package/components/action-button.json +39 -79
  4. package/components/action-group.json +18 -129
  5. package/components/alert-banner.json +8 -27
  6. package/components/alert-dialog.json +34 -48
  7. package/components/avatar-group.json +9 -28
  8. package/components/avatar.json +29 -92
  9. package/components/badge.json +56 -150
  10. package/components/breadcrumbs.json +26 -100
  11. package/components/button-group.json +19 -50
  12. package/components/button.json +61 -92
  13. package/components/calendar.json +8 -67
  14. package/components/cards.json +31 -46
  15. package/components/checkbox-group.json +16 -78
  16. package/components/checkbox.json +27 -90
  17. package/components/close-button.json +20 -62
  18. package/components/coach-indicator.json +14 -44
  19. package/components/coach-mark.json +8 -26
  20. package/components/color-area.json +20 -93
  21. package/components/color-handle.json +25 -38
  22. package/components/color-loupe.json +2 -6
  23. package/components/color-slider.json +26 -122
  24. package/components/color-wheel.json +17 -84
  25. package/components/combo-box.json +50 -182
  26. package/components/contextual-help.json +80 -119
  27. package/components/date-picker.json +24 -120
  28. package/components/divider.json +12 -25
  29. package/components/drop-zone.json +18 -30
  30. package/components/field-label.json +21 -62
  31. package/components/help-text.json +16 -53
  32. package/components/illustrated-message.json +21 -72
  33. package/components/in-line-alert.json +13 -53
  34. package/components/link.json +24 -56
  35. package/components/list-view.json +15 -73
  36. package/components/menu.json +45 -174
  37. package/components/meter.json +24 -65
  38. package/components/number-field.json +34 -168
  39. package/components/picker.json +42 -181
  40. package/components/popover.json +37 -113
  41. package/components/progress-bar.json +23 -95
  42. package/components/progress-circle.json +12 -42
  43. package/components/radio-button.json +14 -67
  44. package/components/radio-group.json +28 -125
  45. package/components/rating.json +9 -38
  46. package/components/search-field.json +34 -119
  47. package/components/segmented-control.json +21 -63
  48. package/components/select-box.json +29 -96
  49. package/components/side-navigation.json +28 -69
  50. package/components/slider.json +39 -148
  51. package/components/standard-dialog.json +16 -88
  52. package/components/status-light.json +41 -123
  53. package/components/steplist.json +5 -24
  54. package/components/swatch-group.json +19 -55
  55. package/components/swatch.json +24 -79
  56. package/components/switch.json +31 -72
  57. package/components/table.json +26 -73
  58. package/components/tabs.json +22 -39
  59. package/components/tag-field.json +14 -60
  60. package/components/tag-group.json +16 -49
  61. package/components/tag.json +21 -71
  62. package/components/takeover-dialog.json +10 -61
  63. package/components/text-area.json +49 -198
  64. package/components/text-field.json +42 -163
  65. package/components/thumbnail.json +22 -63
  66. package/components/toast.json +29 -50
  67. package/components/tooltip.json +27 -74
  68. package/components/tree-view.json +45 -140
  69. package/guidelines/introduction.json +2 -2
  70. package/guidelines/manifest.json +2 -74
  71. package/guidelines/principles.json +2 -2
  72. package/package.json +1 -1
  73. package/guidelines/app-frame-content-area.json +0 -81
  74. package/guidelines/app-frame-creating-bluelines.json +0 -58
  75. package/guidelines/app-frame-header.json +0 -72
  76. package/guidelines/app-frame-side-navigation.json +0 -138
  77. package/guidelines/containers.json +0 -62
  78. package/guidelines/illustrations.json +0 -111
  79. package/guidelines/object-styles.json +0 -102
  80. package/guidelines/spacing.json +0 -25
  81. package/guidelines/typography-fundamentals.json +0 -142
@@ -1,111 +0,0 @@
1
- {
2
- "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
3
- "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/illustrations.json",
4
- "name": "illustrations",
5
- "title": "Illustrations",
6
- "category": "designing",
7
- "documentBlocks": [
8
- { "type": "purpose", "content": "Illustrations" },
9
- {
10
- "type": "guideline",
11
- "content": "The illustrations and graphics in Spectrum 2 have been completely reworked to reflect the significant update of our design system."
12
- },
13
- {
14
- "type": "guideline",
15
- "content": "Spectrum 2 (S2) evolved around the need to bridge the gap between purely professional tools and more consumer-orientated applications, creating updates that prioritize more approachability, a clearer sense of attention hierarchy, and a stronger connection to product branding. Illustrations are a major part of how Spectrum 2 creates such experiences."
16
- },
17
- {
18
- "type": "guideline",
19
- "content": "Please note that parts of this illustration system are still in exploration, and will be added to these guidelines once they’re more defined. Animation is also currently being explored."
20
- },
21
- {
22
- "type": "guideline",
23
- "content": "Here’s a summary of the main updates that you’ll notice with Spectrum 2 illustrations, compared to the style of Spectrum 1:"
24
- },
25
- {
26
- "type": "guideline",
27
- "content": "Linear illustrations are monochromatic. They use the same color token as the icons (S2 / gray 800), and switch colors according to dark and light UI."
28
- },
29
- {
30
- "type": "guideline",
31
- "content": "Linear illustrations use the following naming convention:"
32
- },
33
- {
34
- "type": "guideline",
35
- "content": "Gradient illustrations are new to our design system with the update to Spectrum 2. Compared to linear illustrations, they’re much bolder. They can help users understand a message more quickly, or motivate them to perform a specific action."
36
- },
37
- {
38
- "type": "guideline",
39
- "content": "There are two gradients that can be used for surfaces that show different products, or that are not product-specific. The other gradients are tied to specific products or clouds. For example, blue is tied to the photography and digital imaging category (such as Photoshop, Lightroom, and Fresco), while green represents the 3D category (such as Substance 3D Stager and Substance 3D Designer). It’s essential to use the appropriate illustration colors according to the product categories. If the application is for multiple products, use one of the gradient swatches that incorporate the Adobe brand red."
40
- },
41
- {
42
- "type": "guideline",
43
- "content": "Do not use the category gradient sets as semantic colors to communicate meanings like errors (red), warnings (yellow), or successes (green)."
44
- },
45
- {
46
- "type": "guideline",
47
- "content": "Gradient illustrations use the following naming convention:"
48
- },
49
- {
50
- "type": "guideline",
51
- "content": "Linear illustrations are elements that communicate lower attention, as they blend in well with the rest of the UI. They can be used multiple times in a layout without drawing too much attention."
52
- },
53
- {
54
- "type": "guideline",
55
- "content": "Errors or critical messages should only use linear illustrations."
56
- },
57
- {
58
- "type": "guideline",
59
- "content": "Gradient illustrations use colors that can be misunderstood as semantic colors (e.g., green for positive, red for negative). They also have an upbeat and inspirational tone, which isn’t appropriate in situations where a user may be frustrated by something that’s an inconvenience or is disruptive to them in accomplishing their work."
60
- },
61
- {
62
- "type": "guideline",
63
- "content": "The linear illustration style works well for layouts that feature a number of illustrations together (such as a collection of cards). Linear illustrations draw a lower level of attention and blend in well with the UI, so it’s appropriate to use them in a collection of elements. Gradient illustrations draw a lot of attention in multiples, so they need to be used sparingly and sparsely."
64
- },
65
- {
66
- "type": "guideline",
67
- "content": "Don’t scale or resize linear illustrations. The stroke weight and the corner radii are already set to work best in the given canvas sizes."
68
- },
69
- {
70
- "type": "guideline",
71
- "content": "Gradient illustrations are high attention elements in the layout. Use them strategically and thoughtfully to draw the user’s attention and to provoke a delightful moment."
72
- },
73
- {
74
- "type": "guideline",
75
- "content": "Gradient illustrations draw more attention because they’re very colorful. Using more then one in a given view will make the UI too busy and too loud. Use gradient illustrations sparingly to guide a user’s attention to engaging, high-value actions such as uploads, starting projects, or commenting."
76
- },
77
- {
78
- "type": "guideline",
79
- "content": "Gradient illustrations incorporate product category colors, and also include colors that have semantic meanings in Spectrum: red, orange, or green. It creates inconsistency and confusion to have an error message or a critical alert in green (a color has a positive semantic meaning)."
80
- },
81
- {
82
- "type": "guideline",
83
- "content": "Use gradient illustrations when you want to emphasize positive actions. Gradient illustrations have an upbeat and inspirational tone, which isn’t appropriate in situations where a user may be frustrated by something that’s an inconvenience or is disruptive to them in accomplishing their work."
84
- },
85
- {
86
- "type": "guideline",
87
- "content": "The colors in gradient illustrations are connected to the product categories. For example, an illustration for a Substance 3D product should use the Substance 3D green colors."
88
- },
89
- {
90
- "type": "guideline",
91
- "content": "Do not use different colors than those of your product category. Reach out to the Spectrum Brand team for guidance about the appropriate colors for your use case."
92
- },
93
- {
94
- "type": "guideline",
95
- "content": "It’s highly recommended to test gradient illustrations as you’re designing your layout. They’re very expressive and colorful, so it’s important to determine how they complement (or don’t) different communication points (e.g., user-generated content, onboarding, feature banners, upsells, and more)."
96
- },
97
- {
98
- "type": "guideline",
99
- "content": "If gradient illustrations are making the layout too noisy, use linear illustrations instead."
100
- },
101
- {
102
- "type": "guideline",
103
- "content": "Thematic banners are descriptive and represent a specific topic or feature. Similar to the gradient illustrations, they’re either connected to the product brand categories by color, or they use the generic gradient swatches."
104
- }
105
- ],
106
- "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/illustrations/",
107
- "lastUpdated": "2026-02-02",
108
- "status": "published",
109
- "tags": ["designing"],
110
- "related": [{ "ref": "using-icons" }, { "ref": "motion" }]
111
- }
@@ -1,102 +0,0 @@
1
- {
2
- "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
3
- "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/object-styles.json",
4
- "name": "object-styles",
5
- "title": "Object styles",
6
- "category": "designing",
7
- "documentBlocks": [
8
- {
9
- "type": "purpose",
10
- "content": "Example of how object styles are combined to communicate different interactions.\n\nIn general, Spectrum 2’s system for rounding is more pronounced and flexible than in Spectrum 1.\n\nIn general, this system of rounding creates a visually balanced gap when nesting smaller objects within larger objects.\n\n\"There are two border widths used within in-product UI contexts:\"\n\n\"The third option is not used within in-product UI contexts:\"\n\nA medium divider separates two action button groups. Note that when dividers are used with visible gaps on both ends, the end caps are fully rounded.\n\nWhile the detailed values are still in progress, the foundational concepts for drop shadows still apply.\n\n\"In Spectrum 2, shadows are composed of three layers: a key shadow, an ambient shadow, and a transition shadow that’s between them.\"\n\nContainers that appear on top of content, such as menus and tooltips, have drop shadows to show elevation."
11
- },
12
- {
13
- "type": "guideline",
14
- "content": "Object styles are specific visual shapes or effects that are used to communicate intent or to give cues about an interaction."
15
- },
16
- {
17
- "type": "guideline",
18
- "content": "For example, different types of inputs all share styles. Search fields, text fields, and combo boxes use object styles to communicate a primary purpose: text input. A search field is often more of a global scope, and has full rounding to add emphasis and differentiation from other types of fields. Action buttons, pickers, and in-field buttons share a fill color to indicate selection. Checkboxes, radio buttons, and switches share object styles to indicate binary selection."
19
- },
20
- {
21
- "type": "guideline",
22
- "content": "Example of how object styles are combined to communicate different interactions."
23
- },
24
- {
25
- "type": "guideline",
26
- "content": "In general, Spectrum 2’s system for rounding is more pronounced and flexible than in Spectrum 1."
27
- },
28
- {
29
- "type": "guideline",
30
- "content": "Larger rounding values give components more expression and personality, and having more rounding options makes it possible to create visual balance across a wide range of contexts."
31
- },
32
- {
33
- "type": "guideline",
34
- "content": "In general, this system of rounding creates a visually balanced gap when nesting smaller objects within larger objects."
35
- },
36
- {
37
- "type": "guideline",
38
- "content": "Avatars are displayed in circles to draw attention to user content. All other representations, such as groups and products, are displayed in rounded squares."
39
- },
40
- {
41
- "type": "guideline",
42
- "content": "In Spectrum 2, rounding for different sized components varies based on a Major Second logarithmic scale. This allows for components to retain a consistent and identifiable shape at all sizes. Desktop and mobile scales share the same base rounding. Note that the values displayed are base values for desktop scale components, and specific corner radius values may vary between components."
43
- },
44
- {
45
- "type": "guideline",
46
- "content": "Borders are only used when spacing isn’t enough to show separation. For example, a divider might sometimes be needed to separate two distinct action button groups. Or, an object might have a border to demarcate distinct areas, such as separating a panel or card from the rest of the content on a page."
47
- },
48
- {
49
- "type": "guideline",
50
- "content": "There are two border widths used within in-product UI contexts:"
51
- },
52
- {
53
- "type": "guideline",
54
- "content": "The third option is not used within in-product UI contexts:"
55
- },
56
- {
57
- "type": "guideline",
58
- "content": "A medium divider separates two action button groups. Note that when dividers are used with visible gaps on both ends, the end caps are fully rounded."
59
- },
60
- {
61
- "type": "guideline",
62
- "content": "In Spectrum 2, large borders are only used in longform content, such as in documentation pages. Large borders aren’t used within in-product UI contexts."
63
- },
64
- {
65
- "type": "guideline",
66
- "content": "A full-width medium divider can be a helpful option for separating two distinct parts of a page, such as dividing a navigation panel from the rest of the content. When deciding whether a divider is needed, consider whether groups of information are still clear without one. Generally, more complex content with a varying alignment of objects will benefit the most from using a divider."
67
- },
68
- {
69
- "type": "guideline",
70
- "content": "Similarly to the previous example, a full-width medium divider separates a commenting panel from the rest of the page. The divider is helpful in this context since the commenting panel can have varying content, from an empty state to many layers of nested comments. By creating a clear boundary, this helps set expectations for what content is presented in the panel."
71
- },
72
- {
73
- "type": "guideline",
74
- "content": "Drop shadows draw attention and give the appearance of depth. By default, this style is used to show elevation, when content appears on top of other content."
75
- },
76
- {
77
- "type": "guideline",
78
- "content": "While the detailed values are still in progress, the foundational concepts for drop shadows still apply."
79
- },
80
- {
81
- "type": "guideline",
82
- "content": "In Spectrum 2, shadows are composed of three layers: a key shadow, an ambient shadow, and a transition shadow that’s between them."
83
- },
84
- {
85
- "type": "guideline",
86
- "content": "Containers that appear on top of content, such as menus and tooltips, have drop shadows to show elevation."
87
- },
88
- {
89
- "type": "guideline",
90
- "content": "By default, objects have no drop shadows. When a container is dragged, a drop shadow is used to show elevation in both default and emphasized containers."
91
- },
92
- {
93
- "type": "guideline",
94
- "content": "An overlay represents elevation in a different way: it focuses attention on the content above the overlay only. When using an overlay (for example, behind a dialog), no additional drop shadow is applied to the background."
95
- }
96
- ],
97
- "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/object-styles/",
98
- "lastUpdated": "2026-02-02",
99
- "status": "published",
100
- "tags": ["designing"],
101
- "related": [{ "ref": "fonts" }, { "ref": "spacing" }]
102
- }
@@ -1,25 +0,0 @@
1
- {
2
- "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
3
- "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/spacing.json",
4
- "name": "spacing",
5
- "title": "Spacing",
6
- "category": "designing",
7
- "documentBlocks": [
8
- {
9
- "type": "purpose",
10
- "content": "Spectrum 2 continues with Spectrum's current guidelines for spacing and responsive grids. More detailed guidelines for responsive design are currently in progress.\n\nThe primary update for Spectrum 2 is that **instead of dividers, spacing is used as the primary way to group and divide content**. Different spacing values establish rhythm and create hierarchy within a page. The [spacing values](https://spectrum.corp.adobe.com/page/spacing/#Spacing-values) themselves remain unchanged from Spectrum 1.\n\nSmaller spacing values should generally be used for objects that are closely related. An example of this would be to use a smaller spacing value in between the components that make up a component group, like in a button group or a group of cards.\n\nLarger spacing values should be used for groups of things that are less closely related. An example of this would be to use a larger spacing value to separate two distinct sections of content. Doing this helps to better organize a page.\n\nIn some contexts, a divider can still be appropriate to define larger areas of a page. View more about [border width](https://s2.spectrum.corp.adobe.com/page/object-styles/#border-width).\n\n### Example\n\nIn this example, the side navigation items use a smaller spacing value (spacing-75) in order to show a closer relationship. The side navigation items are grouped with a combination of a section title and a larger spacing value (spacing-400) to divide two distinct sections.\n\nSimilarly, cards that are part of the same group have a smaller spacing value (spacing-300) between them. Each group of cards has a title and a larger spacing value (spacing-500) to show two that the two groups are distinct.\n\nBy using spacing intentionally, the purpose of page content becomes more readily apparent and information can become easier to parse."
11
- },
12
- {
13
- "type": "guideline",
14
- "content": "Spectrum defines density as the spacing between components or UI elements, regardless of their size and scale. Density can be used alongside component size to create a range of layouts, from spacious to dense."
15
- },
16
- {
17
- "type": "guideline",
18
- "content": "For example, when creating complex UI layouts, high density is often combined with smaller components and tighter spacing in between elements."
19
- }
20
- ],
21
- "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/spacing/",
22
- "lastUpdated": "2026-02-02",
23
- "status": "published",
24
- "tags": ["designing"]
25
- }
@@ -1,142 +0,0 @@
1
- {
2
- "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
3
- "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/typography-fundamentals.json",
4
- "name": "typography-fundamentals",
5
- "title": "Typography fundamentals",
6
- "category": "designing",
7
- "documentBlocks": [
8
- {
9
- "type": "purpose",
10
- "content": "The variable font (VF) is the default typeface for Spectrum 2 web, iOS, and future desktop explorations.\n\n\"There are two major updates, compared with Adobe Clean:\"\n\n\"In general:\"\n\nUpdated (\\*) means that these sizes didn't follow the Major Second type scale in Spectrum 1 and have now been updated to reflect the accurate values\n\nSpectrum 2 uses type styles to help maintain a consistent semantic meaning and create accessible, legible, and on-brand experiences across platforms.\n\nComponent is the type style that is applied to text within UI components.\n\nCode is a typography component used for text that represents code. The default font for showing code is Source Code Pro.\n\nIn this file browsing example, Heading, Title, Component, and Detail style text are used to create hierarchy throughout the page.\n\nIn this commenting example, Title, Body, Component, and Detail style text are used to create hierarchy within the comments panel."
11
- },
12
- {
13
- "type": "guideline",
14
- "content": "The variable font (VF) is the default typeface for Spectrum 2 web, iOS, and future desktop explorations."
15
- },
16
- {
17
- "type": "guideline",
18
- "content": "There are two major updates, compared with Adobe Clean:"
19
- },
20
- {
21
- "type": "guideline",
22
- "content": "If you need to deviate from the default typeface (Adobe Clean Spectrum VF), you can use Adobe Clean Spectrum Serif VF, Adobe Clean Han, and Source Code Pro:"
23
- },
24
- {
25
- "type": "guideline",
26
- "content": "Spectrum ensures that different sizes of text can work together harmoniously, on both desktop and mobile. For Spectrum 2, all font sizes follow the Major Second type scale, which has a ratio of 1.125. This means that each size is multiplied or divided by 1.125 from the previous size, starting with the base size (font-size-100), and rounded to the nearest whole number. Custom text (any non-existing typography styles) or modifications to existing type styles should use a font size from this list."
27
- },
28
- {
29
- "type": "guideline",
30
- "content": "When selecting font sizes to ensure readability, keep in mind that Adobe Clean does not match 1:1 with system font size definitions. It’s generally a size smaller than system fonts such as SF Pro, Segoe UI, Roboto, and others."
31
- },
32
- {
33
- "type": "guideline",
34
- "content": "Updated (\\*) means that these sizes didn't follow the Major Second type scale in Spectrum 1 and have now been updated to reflect the accurate values"
35
- },
36
- {
37
- "type": "guideline",
38
- "content": "New (\\*\\*) shows Spectrum 2's new additions: font-size-25 is new to accommodate scaling to the smallest detail and body sizes. Font-size-1400 and -1500 are now available to provide consistent scaling to larger sizes. These are often needed in website design and for marketing scenarios."
39
- },
40
- {
41
- "type": "guideline",
42
- "content": "Spectrum 2 offers guidance for a wider range of font weights to help establish visual hierarchy in layouts, including the specific usages of Black, ExtraBold, and Medium weights."
43
- },
44
- {
45
- "type": "guideline",
46
- "content": "When used in Adobe Express products, the weight is set to Black in order to align to the Adobe Express brand guidelines. Black weight text should only be used in heading type styles, and never below 18 px font-size, to ensure the text remains legible."
47
- },
48
- {
49
- "type": "guideline",
50
- "content": "Select elements in the UI use a Bold font weight. Bold text is often used to accentuate the primary focus on a page or in a container, and in many uses, it’s paired with regular body text to create hierarchy. Titles, file names, user names, and button labels all use bold weight."
51
- },
52
- {
53
- "type": "guideline",
54
- "content": "In Spectrum 2, some components, like action buttons, badges, and tags, use Medium weight labels in order to maintain balance with Spectrum 2’s icons, which use a 1.5 px stroke."
55
- },
56
- {
57
- "type": "guideline",
58
- "content": "Regular is the default font weight for Spectrum components and body text. It should also be used for any content that’s entered by users, is editable, or longer in form (for example, text fields and text areas)."
59
- },
60
- {
61
- "type": "guideline",
62
- "content": "Line height values are updated in Spectrum 2 to better accommodate the baseline shift of the new default font — Adobe Clean Spectrum VF — and to position the text as vertically centered in UI components."
63
- },
64
- {
65
- "type": "guideline",
66
- "content": "To ensure that the space between lines of text appears balanced, the default line-height is adjusted from \\~130% at smaller font-sizes to \\~115% at larger font-sizes, and then rounded to whole even numbers to ensure that text within a component will not sit on a half-pixel."
67
- },
68
- {
69
- "type": "guideline",
70
- "content": "Body and Code type styles use a more spacious line height multiplier of 1.5x the font-size (line-height-200) to ensure that longform text has more space and is legible. CJK languages use a 1.7x multiplier."
71
- },
72
- {
73
- "type": "guideline",
74
- "content": "Spectrum 2 uses type styles to help maintain a consistent semantic meaning and create accessible, legible, and on-brand experiences across platforms."
75
- },
76
- {
77
- "type": "guideline",
78
- "content": "Keep in mind that a single product won’t need all of theses sizes, and especially at the same time. As a starting point, use a t-shirt size from each of the type styles (in Figma, these are known as text styles). For example: pair Heading Medium with Title Medium, Body Medium, and Medium t-shirt sized components."
79
- },
80
- {
81
- "type": "guideline",
82
- "content": "If you’d like to override these styles, there’s some flexibility for you to define your own typography and hierarchy as long as any customization follows Spectrum guidance for font size and color usage. Use what best fits your context and best supports your users."
83
- },
84
- {
85
- "type": "guideline",
86
- "content": "Heading text represents the biggest and boldest text on a page, and it draws the most attention. Only the broadest idea, such as the main page title, should use this style."
87
- },
88
- {
89
- "type": "guideline",
90
- "content": "Body is the type style that’s primarily used for longer-form text that may extend to multiple lines. “Body text” is a frequently used term to describe the text that creates the main content on a page, which is where this style gets its name from."
91
- },
92
- {
93
- "type": "guideline",
94
- "content": "“Detail text” is a broad term for any kind of text that communicates ideas that are even more specific than body text. Text using the Detail style acts as supporting context to any other information presented."
95
- },
96
- {
97
- "type": "guideline",
98
- "content": "Detail text often uses Medium weight when paired with iconography, to maintain visual balance with the 1.5 px stroke width of Spectrum 2 icons. It’s also often shown in gray-600 or gray-700 to make it more subdued in terms of visual hierarchy."
99
- },
100
- {
101
- "type": "guideline",
102
- "content": "The differences between Detail text, Component text, and Body text are nuanced and often come down to applied semantic meaning. The characteristic differences in Detail text are the default weight, size, letter spacing, all-caps treatment for marketing contexts, and color usage. Detail text defaults to Medium weight, a smaller font size, and lighter shades of gray. It also uses the updated per-font-size line height, while Body text uses the spacious line height multiplier of 1.5x font-size."
103
- },
104
- {
105
- "type": "guideline",
106
- "content": "Component is the type style that is applied to text within UI components."
107
- },
108
- {
109
- "type": "guideline",
110
- "content": "In Spectrum 1, the “component” line height meant “a line-height applied to text within UI elements.” Spectrum 2 expands on this by having text styles in the Spectrum Figma libraries, to let you quickly apply text formatting to any text element in a design. This will help you stay connected to the system without needing to detach or override other text styles like Body or Title."
111
- },
112
- {
113
- "type": "guideline",
114
- "content": "The Component type style comes in multiple font weights to support its flexibility across components in the design system. For example, the Spectrum 2 button uses the Component type style with bold weight. Action button uses the Component type style with medium weight, and text field uses the Component type style with regular weight."
115
- },
116
- {
117
- "type": "guideline",
118
- "content": "Code is a typography component used for text that represents code. The default font for showing code is Source Code Pro."
119
- },
120
- {
121
- "type": "guideline",
122
- "content": "The following are some general examples to show how the Spectrum 2 typography system all comes together, and how type styles can be used together to create visual hierarchy."
123
- },
124
- {
125
- "type": "guideline",
126
- "content": "In this file browsing example, Heading, Title, Component, and Detail style text are used to create hierarchy throughout the page."
127
- },
128
- {
129
- "type": "guideline",
130
- "content": "In this commenting example, Title, Body, Component, and Detail style text are used to create hierarchy within the comments panel."
131
- },
132
- {
133
- "type": "guideline",
134
- "content": "In instances where Spectrum’s typefaces might fail to load properly, there are defined fallback fonts that have been selected based on operating system consistency and similar anatomical relationships."
135
- }
136
- ],
137
- "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/typography-fundamentals/",
138
- "lastUpdated": "2026-02-02",
139
- "status": "published",
140
- "tags": ["designing"],
141
- "related": [{ "ref": "background-layers" }, { "ref": "fonts" }]
142
- }