@adobe/spectrum-design-data 0.3.0 → 0.6.0

package/guidelines/manifest.json

@@ -0,0 +1,204 @@
+{
+  "guidelines": [
+    {
+      "slug": "app-frame-content-area",
+      "title": "App frame content area (browsing context)",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-content-area/",
+      "file": "guidelines/app-frame-content-area.json"
+    },
+    {
+      "slug": "app-frame-creating-bluelines",
+      "title": "Creating bluelines (browsing context)",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-creating-bluelines/",
+      "file": "guidelines/app-frame-creating-bluelines.json"
+    },
+    {
+      "slug": "app-frame-header",
+      "title": "App frame header (browsing context)",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-header/",
+      "file": "guidelines/app-frame-header.json"
+    },
+    {
+      "slug": "app-frame-overview",
+      "title": "App frame",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-overview/",
+      "file": "guidelines/app-frame-overview.json"
+    },
+    {
+      "slug": "app-frame-side-navigation",
+      "title": "App frame side navigation (browsing context)",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-side-navigation/",
+      "file": "guidelines/app-frame-side-navigation.json"
+    },
+    {
+      "slug": "attention-hierarchy",
+      "title": "Attention hierarchy",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/attention-hierarchy/",
+      "file": "guidelines/attention-hierarchy.json"
+    },
+    {
+      "slug": "background-layers",
+      "title": "Background layers",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/background-layers/",
+      "file": "guidelines/background-layers.json"
+    },
+    {
+      "slug": "brand",
+      "title": "Brand",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/brand/",
+      "file": "guidelines/brand.json"
+    },
+    {
+      "slug": "colors",
+      "title": "Colors",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/colors/",
+      "file": "guidelines/colors.json"
+    },
+    {
+      "slug": "containers",
+      "title": "Containers",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/containers/",
+      "file": "guidelines/containers.json"
+    },
+    {
+      "slug": "developer-overview",
+      "title": "Developer overview",
+      "category": "developing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/developer-overview/",
+      "file": "guidelines/developer-overview.json"
+    },
+    {
+      "slug": "faqs",
+      "title": "FAQs",
+      "category": "support",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/faqs/",
+      "file": "guidelines/faqs.json"
+    },
+    {
+      "slug": "fonts",
+      "title": "Fonts",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/fonts/",
+      "file": "guidelines/fonts.json"
+    },
+    {
+      "slug": "grays",
+      "title": "Grays",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/grays/",
+      "file": "guidelines/grays.json"
+    },
+    {
+      "slug": "icon-fundamentals",
+      "title": "Icon fundamentals",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/icon-fundamentals/",
+      "file": "guidelines/icon-fundamentals.json"
+    },
+    {
+      "slug": "illustrations",
+      "title": "Illustrations",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/illustrations/",
+      "file": "guidelines/illustrations.json"
+    },
+    {
+      "slug": "introduction",
+      "title": "Introduction",
+      "category": "fundamentals",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/introduction/",
+      "file": "guidelines/introduction.json"
+    },
+    {
+      "slug": "motion",
+      "title": "Motion",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/motion/",
+      "file": "guidelines/motion.json"
+    },
+    {
+      "slug": "object-styles",
+      "title": "Object styles",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/object-styles/",
+      "file": "guidelines/object-styles.json"
+    },
+    {
+      "slug": "principles",
+      "title": "Principles",
+      "category": "fundamentals",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/principles/",
+      "file": "guidelines/principles.json"
+    },
+    {
+      "slug": "resources",
+      "title": "Resources",
+      "category": "support",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/resources/",
+      "file": "guidelines/resources.json"
+    },
+    {
+      "slug": "spacing",
+      "title": "Spacing",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/spacing/",
+      "file": "guidelines/spacing.json"
+    },
+    {
+      "slug": "states",
+      "title": "States",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/states/",
+      "file": "guidelines/states.json"
+    },
+    {
+      "slug": "typography-fundamentals",
+      "title": "Typography fundamentals",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/typography-fundamentals/",
+      "file": "guidelines/typography-fundamentals.json"
+    },
+    {
+      "slug": "using-icons",
+      "title": "Using icons",
+      "category": "designing",
+      "status": "published",
+      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/using-icons/",
+      "file": "guidelines/using-icons.json"
+    }
+  ]
+}

package/guidelines/motion.json

@@ -0,0 +1,41 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/motion.json",
+  "name": "motion",
+  "title": "Motion",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "Spectrum 2 builds on top of the [existing motion guidelines for the design system](https://spectrum.corp.adobe.com/page/motion/): that motion is always purposeful, intuitive, and seamless. With this update, we also use motion to draw attention to areas where we want to add personality. No matter what, the usage of motion should be adding meaning to an experience. And, motion over large surface areas needs to support browser and system settings for reduced motion.\n\nMotion is also an important part of brand expression. Just like tone in language, tone in motion can range from formal and direct to lighthearted and subtle.\n\nMotion in Spectrum 2 is categorized into the areas of **directional** motion, **interaction** motion, and **wayfinding** motion. Wayfinding motion is still in development."
+    },
+    {
+      "type": "guideline",
+      "content": "Linear motion indicates forward movement and a sentiment of progress. When emphasizing movement to a different section, page, or item (such as a button or link), the destination is readily clear and minimally disruptive.\n\nIf you're creating a custom animation, consider [RTL (right-to-left) languages](https://spectrum.corp.adobe.com/page/bi-directionality/) and also how the meaning of motion might differ depending on cultural context.\n\nProgress bars communicate forward progression. They work well to show determinate (finite) progress.\n\nIn the example of a button, a static arrow icon facing toward the right already indicates forward movement. When linear motion is added to the arrow upon hover, the movement is emphasized. Use this button option with motion sparingly, only on the most important action(s) on a page."
+    },
+    {
+      "type": "guideline",
+      "content": "Diagonal motion indicates larger movement, and can be potentially disruptive. This type of motion can be used to emphasize that there's a switch in context happening, like linking out to a different view or destination.\n\nIn the example of a link, a static arrow icon facing the top right already indicates a potentially disruptive action. When diagonal motion is added to the arrow on hover, the meaning of the arrow is emphasized. Use this link option with motion sparingly, and only to communicate that there will be a switch in context."
+    },
+    {
+      "type": "guideline",
+      "content": "Clockwise motion indicates a holding pattern that's repetitive and doesn't have clear forward momentum or progress. This is most often used for loading indicators.\n\nProgress circles have clockwise motion and work well to show indeterminate (infinite) progress."
+    },
+    {
+      "type": "guideline",
+      "content": "Motion shows users feedback that, when interacting with the UI, their actions are registering with a system. It's not the only way to show feedback, but it helps objects to feel more dynamic and responsive. It also can help communicate meaning, or add emphasis that something is happening that requires attention."
+    },
+    {
+      "type": "guideline",
+      "content": "A [microinteraction](https://www.nngroup.com/articles/microinteractions/) is a single action (like a click, tap, or swipe) which triggers a response (like a transition or animation). In Spectrum 2, microinteractions offer moments of personality that are reflective of product branding."
+    },
+    {
+      "type": "guideline",
+      "content": "In this example, the button scales down on the down state, emphasizing that something — the action of selecting — happened."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/motion/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"]
+}

package/guidelines/object-styles.json

@@ -0,0 +1,105 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/object-styles.json",
+  "name": "object-styles",
+  "title": "Object styles",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "Object styles are specific visual shapes or effects that are used to communicate intent or to give cues about an interaction."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "Example of how object styles are combined to communicate different interactions."
+    },
+    {
+      "type": "guideline",
+      "content": "In general, Spectrum 2’s system for rounding is more pronounced and flexible than in Spectrum 1."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "In general, this system of rounding creates a visually balanced gap when nesting smaller objects within larger objects."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "There are two border widths used within in-product UI contexts:"
+    },
+    {
+      "type": "guideline",
+      "content": "The third option is not used within in-product UI contexts:"
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "While the detailed values are still in progress, the foundational concepts for drop shadows still apply."
+    },
+    {
+      "type": "guideline",
+      "content": "In Spectrum 2, shadows are composed of three layers: a key shadow, an ambient shadow, and a transition shadow that’s between them."
+    },
+    {
+      "type": "guideline",
+      "content": "Containers that appear on top of content, such as menus and tooltips, have drop shadows to show elevation."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/object-styles/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    { "ref": "fonts", "kind": "guideline" },
+    { "ref": "spacing", "kind": "guideline" }
+  ]
+}

package/guidelines/principles.json

@@ -0,0 +1,30 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/principles.json",
+  "name": "principles",
+  "title": "Principles",
+  "category": "fundamentals",
+  "documentBlocks": [
+    { "type": "purpose", "content": "Principles" },
+    {
+      "type": "guideline",
+      "content": "Rational.\n\nSpectrum is based on real-world situations. Every component, pattern, and principle is informed by thoughtful testing. Every decision is backed by thorough interdisciplinary research.\n\nSpectrum is not a rigid set of rules for how to build products, but rather a set of adaptable resources for making experiences feel contextual, cohesive, and performant."
+    },
+    {
+      "type": "guideline",
+      "content": "Human.\n\nSpectrum places people's needs first. It's deeply committed to a high standard of inclusivity, accessibility, honesty, and respect.\n\nSpectrum is adaptable to meet as many user expectations, platform requirements, and product visions as possible. It's always what it needs to be, accommodating a flexible range of expression. It balances the human needs of utility and joy."
+    },
+    {
+      "type": "guideline",
+      "content": "Focused.\n\nSpectrum delivers what's needed, when it's needed. Every decoration is purposeful and meaningful. Every communication touchpoint is relevant.\n\nSpectrum experiences are built to a high standard of quality. Everything incorporates attention to details, and that creates experiences that look and feel well-crafted. Things are delightful to use because they balance functionality and expression."
+    },
+    {
+      "type": "guideline",
+      "content": "Collaborative.\n\nSpectrum belongs to everyone. It's a reflection of an ever-growing community that makes decisions thoughtfully, holistically, and collectively.\n\nSpectrum examines from multiple angles, then refines, then repeats. Constantly."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/principles/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["fundamentals"]
+}

package/guidelines/resources.json

@@ -0,0 +1,59 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/resources.json",
+  "name": "resources",
+  "title": "Resources",
+  "category": "support",
+  "documentBlocks": [
+    { "type": "purpose", "content": "Resources" },
+    {
+      "type": "guideline",
+      "content": "The Spectrum 2 Figma libraries are the primary resource for Spectrum 2 components, styles, and variables. These libraries are stable, so you can use the designs in production."
+    },
+    {
+      "type": "guideline",
+      "content": "An example of the Spectrum 2 library: the action button page."
+    },
+    {
+      "type": "guideline",
+      "content": "This GitHub repository houses Spectrum’s design tokens, which are primarily name-value pairs used to store design decisions and distributed in a way that platforms, implementations, and products can use across design tools and coding languages."
+    },
+    {
+      "type": "guideline",
+      "content": "This tool allows you to search for token names or values, filter values by scale and theme, and explore the relationship between Spectrum’s tokens by selecting tokens to see their connections."
+    },
+    {
+      "type": "guideline",
+      "content": "To support this transition, S2/Color has been removed from the inheritance chain in the Figma libraries. Designers should update their files to replace color styles with color variables. Following the steps in the guide will help ensure your files remain stable and aligned with the Spectrum system moving forward."
+    },
+    {
+      "type": "guideline",
+      "content": "These changes are for Spectrum 2 libraries. They do not apply to Spectrum 1."
+    },
+    {
+      "type": "guideline",
+      "content": "To support the new font, we’ve updated our default line-height values and introduced symmetrical vertical padding token values to our design system. The Spectrum 2 typography guide includes details about what’s changing, what’s staying the same, and options for updating design files or implementations."
+    },
+    {
+      "type": "guideline",
+      "content": "These changes are for Spectrum 2 libraries and implementations. They do not apply to Spectrum 1 components."
+    },
+    {
+      "type": "guideline",
+      "content": "Spectrum 2 includes two new grays — gray-25 and gray-1000 — plus an update to the rest of the 11 grays. The migration guide goes into more detail about what’s changing and what’s staying the same."
+    },
+    {
+      "type": "guideline",
+      "content": "Creating interfaces that support right-to-left (RTL) and bi-directional (Bidi) languages is essential to ensuring that our products are inclusive of global audiences. These guides, created by the Adobe International team, offer comprehensive frameworks on how to design and build for both web and mobile components."
+    },
+    {
+      "type": "guideline",
+      "content": "The Adobe Design Brand team has created Spectrum 2-inspired desktop and mobile backgrounds for you to download."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/resources/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["support"],
+  "related": [{ "ref": "contact" }]
+}

package/guidelines/spacing.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/spacing.json",
+  "name": "spacing",
+  "title": "Spacing",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "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."
+    },
+    {
+      "type": "guideline",
+      "content": "For example, when creating complex UI layouts, high density is often combined with smaller components and tighter spacing in between elements."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/spacing/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"]
+}

package/guidelines/states.json

@@ -0,0 +1,34 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/states.json",
+  "name": "states",
+  "title": "States",
+  "category": "designing",
+  "documentBlocks": [
+    { "type": "purpose", "content": "States" },
+    {
+      "type": "guideline",
+      "content": "In Spectrum 2, some components use a change in size instead of color to communicate a down state. This gives the illusion of objects being pressed-in, and makes interactions more dynamic and responsive."
+    },
+    {
+      "type": "guideline",
+      "content": "[Disabled states](https://spectrum.corp.adobe.com/page/states/#Disabled) generally stay the same from Spectrum 1, but there have been some minor updates to specific components. For example, a text field retains the outline style when disabled, to more closely match its default state."
+    },
+    {
+      "type": "guideline",
+      "content": "Selected states use a primary style by default, generally through a gray-800 fill. Some have an accent color option that can be used to draw emphasis. This is primarily helpful in contexts with a specific and narrowly-scoped goal (for example, in a dialog), or when there's a single, clear call to action within a page (for example, a \"Create\" button)."
+    },
+    {
+      "type": "guideline",
+      "content": "When there's many groups of controls that require the same amount of attention (such as in a panel) the not emphasized option works best. For more details about this concept, view [Attention hierarchy](https://s2.spectrum.corp.adobe.com/page/attention-hierarchy/)."
+    },
+    {
+      "type": "guideline",
+      "content": "A dragged state has a unique drop shadow to draw attention to the dragged object. Learn more about [drop shadows](https://s2.spectrum.corp.adobe.com/page/object-styles/#drop-shadow)."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/states/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"]
+}