@adobe/spectrum-design-data 0.3.0 → 0.6.0

package/guidelines/app-frame-content-area.json

@@ -0,0 +1,87 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/app-frame-content-area.json",
+  "name": "app-frame-content-area",
+  "title": "App frame content area (browsing context)",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "App frame content area (browsing context)"
+    },
+    {
+      "type": "guideline",
+      "content": "This layout is suitable when all content is related and unified by the primary purpose of the page. This single section can be subdivided using full-width dividers, or by creating visual groupings of content using proximity and spacing."
+    },
+    {
+      "type": "guideline",
+      "content": "Dividers are useful to separate content when using spacing alone wouldn’t be clear enough to mark the boundaries of distinct areas. Generally, more complex content with a varying alignment of objects will benefit the most from using a divider."
+    },
+    {
+      "type": "guideline",
+      "content": "The top section can also be useful to visually indicate that the content is separate and has additional affordances, such as the ability to be minimized. For example, “welcome” type content might be shown in the top section, and recent files might be shown below."
+    },
+    {
+      "type": "guideline",
+      "content": "When using horizontal sections, the page should scroll as a single unit. Consider other ways to minimize the top section if needed, such as through an additional control to show and hide content."
+    },
+    {
+      "type": "guideline",
+      "content": "The top section of a horizontal layout should be reserved for high-attention marketing messages or quick actions, and it should not be scrollable. Put infinite scrolling and longer content in the bottom section."
+    },
+    {
+      "type": "guideline",
+      "content": "This layout is suitable to separate content that’s not semantically related, and if one of the content areas can be minimized. For example, this might apply for onboarding tutorials, or to include an AI assistant."
+    },
+    {
+      "type": "guideline",
+      "content": "This layout is suitable to separate multiple groups of content that aren’t semantically related. For example, this could show several widgets and distinct marketing messages. This layout can also be useful if a user is able to customize the page."
+    },
+    {
+      "type": "guideline",
+      "content": "Make sure to consider smaller breakpoints and decide how content areas should reflow, hide, or combine. In general, show the most important information at the top, and if possible, then progressively disclose the not-as-important information."
+    },
+    {
+      "type": "guideline",
+      "content": "Backgrounds that use gradients are always placed within the app frame intentionally and with a strategic meaning. They should contribute to the visual hierarchy, not distract from it. And, their colors are directly tied to product brand color palettes."
+    },
+    {
+      "type": "guideline",
+      "content": "For example, on a Home screen, gradient backgrounds might call attention to new AI features in the product. On a Learn screen, gradient backgrounds might call attention to tutorials from new creators. On a Files screen, gradient backgrounds might not be used at all in order to focus attention on asset previews. In any context, consider where you want to draw attention and what you want to highlight for the user, what the user’s intentions might be, and how gradient backgrounds may add or detract from the goals of the page."
+    },
+    {
+      "type": "guideline",
+      "content": "While there isn’t an objective scale for each style, it can be helpful to think about backgrounds in terms of how much attention they draw, on a scale of low-to-high."
+    },
+    {
+      "type": "guideline",
+      "content": "While you may have seen past Spectrum 2 explorations showing gradients as the background in header and navigational areas, they should not be used in that context. This is because gradients that appear in the navigation of every page distract from more important information on the page, clash with other imagery, and might not work for some product segments."
+    },
+    {
+      "type": "guideline",
+      "content": "By using gradients in the content areas as backgrounds instead, there’s more flexibility to direct attention to different content and messages, depending on what’s important in the context of that page or workflow."
+    },
+    {
+      "type": "guideline",
+      "content": "Gradients are used to draw attention to important content and features. They can be used in the background of content areas. Using gradients in more than one content area results in multiple areas competing for attention. This is distracting from the task-at-hand workflows on the page."
+    },
+    {
+      "type": "guideline",
+      "content": "Gradients should always be delivered directly from the Spectrum Brand team and used as-is. Do not modify them."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-content-area/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    {
+      "ref": "s2-app-frame-side-navigation-browsing-context",
+      "kind": "guideline"
+    },
+    {
+      "ref": "s2-app-frame-creating-bluelines-browsing-context",
+      "kind": "guideline"
+    }
+  ]
+}

package/guidelines/app-frame-creating-bluelines.json

@@ -0,0 +1,61 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/app-frame-creating-bluelines.json",
+  "name": "app-frame-creating-bluelines",
+  "title": "Creating bluelines (browsing context)",
+  "category": "designing",
+  "documentBlocks": [
+    { "type": "purpose", "content": "Creating bluelines (browsing context)" },
+    {
+      "type": "guideline",
+      "content": "Accessible names vary depending on the content. Accessible names must be defined for controls that don’t have visible text labels."
+    },
+    {
+      "type": "guideline",
+      "content": "Here are some guidelines to keep in mind as you define accessible names in the app frame:"
+    },
+    {
+      "type": "guideline",
+      "content": "Any non-text element in a digital interface with a text label must have a text alternative. Here’s an example of how you might name landmark regions in an app frame:"
+    },
+    {
+      "type": "guideline",
+      "content": "Here’s an example of how you might structure heading annotations for this screen:"
+    },
+    {
+      "type": "guideline",
+      "content": "Keyboard focus order will depend on what controls are available on the page. Here’s an example of how you might define the order in the app frame:"
+    },
+    {
+      "type": "guideline",
+      "content": "Example of correct usage, support for keyboard focus for size navigation. The side navigation width is focusable and resizable by using the left and right arrow keys."
+    },
+    {
+      "type": "guideline",
+      "content": "Example of correct usage, inclusion of a Skip to main content button within the app frame header."
+    },
+    {
+      "type": "guideline",
+      "content": "When properly supported, the F6 key allows keyboard users to navigate through different regions of an application efficiently. Without this support, keyboard-only users have no means to jump to specific areas of the application, resulting in an excessive number of keystrokes to reach their desired goal."
+    },
+    {
+      "type": "guideline",
+      "content": "Here are some key quality factors to consider:"
+    },
+    {
+      "type": "guideline",
+      "content": "For mobile breakpoints, a tray is used to open and close the app frame side navigation. In this example, the keyboard focus order starts at the “Create” button and ends at the close button. Clicking on esc should also close the tray."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-creating-bluelines/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    {
+      "ref": "s2-app-frame-content-area-browsing-context",
+      "kind": "guideline"
+    },
+    { "ref": "brand", "kind": "guideline" }
+  ]
+}

package/guidelines/app-frame-header.json

@@ -0,0 +1,75 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/app-frame-header.json",
+  "name": "app-frame-header",
+  "title": "App frame header (browsing context)",
+  "category": "designing",
+  "documentBlocks": [
+    { "type": "purpose", "content": "App frame header (browsing context)" },
+    {
+      "type": "guideline",
+      "content": "There are several parts of the header that are consistent across all Adobe products:"
+    },
+    {
+      "type": "guideline",
+      "content": "Shows a hamburger button on the far left of the header. This controls whether the minimized style of the side navigation (partial/full)."
+    },
+    { "type": "guideline", "content": "Shows navigation items in the header." },
+    { "type": "guideline", "content": "Shows a search option in the header." },
+    {
+      "type": "guideline",
+      "content": "Defines the style of the search option that's shown."
+    },
+    {
+      "type": "guideline",
+      "content": "The “skip to main content” button helps improve keyboard navigation by creating a shortcut to the main content of the page. This button is an accessibility feature to allow skipping to the first navigable HTML item."
+    },
+    {
+      "type": "guideline",
+      "content": "Shows an icon to represent the header navigation item."
+    },
+    {
+      "type": "guideline",
+      "content": "The text that is displayed as the label of the header navigation item."
+    },
+    {
+      "type": "guideline",
+      "content": "Presents the header side navigation as selected or not selected."
+    },
+    {
+      "type": "guideline",
+      "content": "Changes the header navigation item to the disabled state."
+    },
+    {
+      "type": "guideline",
+      "content": "Shows a chevron next to the label that indicates an additional menu."
+    },
+    {
+      "type": "guideline",
+      "content": "The text that is displayed as the label of the tooltip."
+    },
+    {
+      "type": "guideline",
+      "content": "As a general rule, only use one call-to-action (CTA) button, aside from any buttons used to log in or log out, as defined in the universal nav. When too many CTAs are shown at once, the messages compete for attention and dilute the ability for a focused attention hierarchy."
+    },
+    {
+      "type": "guideline",
+      "content": "If there are multiple actions, consider combining them into a single menu or use other button types. The button should represent the most important CTA across the product; for example, “Share” and “Get desktop app” are common CTAs."
+    },
+    {
+      "type": "guideline",
+      "content": "Diagram with notes about the app frame header in the editing context. If there’s a menu represented by a hamburger icon, such as the application menu in Creative Cloud, it should be shown to the left of the product logo for continuity with the browsing context. The product name can be hidden in the editing context in order to provide more room for other actions. The height of the header should be the same as in the browsing context (56 px)."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-header/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    { "ref": "s2-app-frame", "kind": "guideline" },
+    {
+      "ref": "s2-app-frame-side-navigation-browsing-context",
+      "kind": "guideline"
+    }
+  ]
+}

package/guidelines/app-frame-overview.json

@@ -0,0 +1,167 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/app-frame-overview.json",
+  "name": "app-frame-overview",
+  "title": "App frame",
+  "category": "designing",
+  "documentBlocks": [
+    { "type": "purpose", "content": "App frame" },
+    {
+      "type": "guideline",
+      "content": "The app frame is the core navigation direction for Spectrum 2. It’s designed as a flexible framework that’s readily adaptable to specific product needs while still creating a shared, predictable experience across products."
+    },
+    {
+      "type": "guideline",
+      "content": "The app frame needs to be opinionated without being restrictive. It directly accounts for the needs of future Spectrum 2 products, and is also flexible enough to be readily adaptable across varying product segment needs."
+    },
+    {
+      "type": "guideline",
+      "content": "A cohesive, consistent app frame reinforces Adobe’s brand and helps users feel comfortable and familiar with our products. Predictable navigation across products is also imperative for Adobe to support users working across multiple applications — and helps people more readily learn how to use new products."
+    },
+    {
+      "type": "guideline",
+      "content": "The app frame is the main stage to showcase the Spectrum 2 style, and it reflects the core foundations and principles of the design system. It works readily with all other design system resources, is committed to complying with WCAG standards, and holds the highest standards for globalization support."
+    },
+    {
+      "type": "guideline",
+      "content": "Spectrum offers a high-level direction as well as a definition of which parts can be flexible and which parts need to be highly predictable. Product teams are then empowered to apply this direction in ways that make the most sense for their use cases and users."
+    },
+    {
+      "type": "guideline",
+      "content": "Zones are the general areas into which certain types of actions should go. They’re not specific to components."
+    },
+    {
+      "type": "guideline",
+      "content": "This is a general area that contains global actions, such as view actions (e.g., layout and zoom options) and supplemental features (e.g., AI Assistants). Actions here can be shown in different ways, such as using part of the content area to show actions in the header, or in a dedicated side rail. There is no single visual representation of how actions should look in this area."
+    },
+    {
+      "type": "guideline",
+      "content": "This area is reserved for transient actions that are contextual to content on the page (e.g., an action bar)."
+    },
+    {
+      "type": "guideline",
+      "content": "Parts of the anatomy have defined rules and behaviors. The terms used here to describe the anatomy of the app framework are for internal alignment only, and are not representative of how these parts of the app frame should be described to end users."
+    },
+    {
+      "type": "guideline",
+      "content": "In the S2 app frame, gradients are only used as backgrounds in content areas — they are not used in the header (A) and navigational areas (B). This allows for greater flexibility between pages where gradients may be calling attention to different kinds of content."
+    },
+    {
+      "type": "guideline",
+      "content": "There are two variants of the side navigation state control: hamburger and panel. They should never be used at the same time."
+    },
+    {
+      "type": "guideline",
+      "content": "Interacting with this icon in the header will either fully expand and collapse, or partially collapse, the panel."
+    },
+    {
+      "type": "guideline",
+      "content": "When hovering on the panel icon, the icon will show an animated preview of what action would be done upon interaction (either expanding or collapsing). This animation offers more context about what to expect. The placement of the panel icon is at the bottom of the app frame side navigation panel."
+    },
+    {
+      "type": "guideline",
+      "content": "To activate or deactivate the TAB, select the 9-grid icon. Once clicked on, the TAB will appear above the header. On a screen reader, if there is an alert banner present, then the visual placement from top to bottom would be alert banner, TAB, then header."
+    },
+    {
+      "type": "guideline",
+      "content": "The placement and appearance of the TAB icon may differ across Adobe products. Not all products will utilize the TAB. The currently supported products are Adobe Home, Firefly, Express, Photoshop, Lightroom, and Acrobat."
+    },
+    {
+      "type": "guideline",
+      "content": "For products that use the TAB, the side navigation state control (panel icon) will be at the bottom of the side navigation. For mobile experiences, the side navigation state control (hamburger icon) and product switcher will be in the header."
+    },
+    {
+      "type": "guideline",
+      "content": "The following are some common terms used at Adobe for describing the core UI elements that make up the app frame, along with some notable usage considerations. Consider this as a starting point for you to take and develop into working language that may need to be more contextual for your product. Work with your Content Strategy partners to adapt it to your needs."
+    },
+    {
+      "type": "guideline",
+      "content": "The word “content” is general in theory but specific in application. In general, it’s a catch-all word for something that is contained in a designated space, and communicates meaning or intention. Specific to the context of the app frame, it describes that what goes into this area is at the discretion of a given situation or user experience."
+    },
+    {
+      "type": "guideline",
+      "content": "This is a commonly used internal term, but is not recommended for describing the interface to an end user. This is because it relies upon a visual metaphor to mimic an analog concept: something that “sinks” into a UI plane, like a water well sinks into the surface of the ground."
+    },
+    {
+      "type": "guideline",
+      "content": "Internal jargon is important and we want to be aligned across teams, but we also need to be careful about using internal terms, externally. By “user-facing term,” we mean that user to be the “end user”: the person who encounters the UI of an Adobe experience."
+    },
+    {
+      "type": "guideline",
+      "content": "In general, if you’re creating resources for internal usage (such as design guidelines or specs), you can safely use internal jargon. If you’re creating actual product UI, you will need to ensure that you’re using the appropriate terms that will help your user best understand and navigate the interface. Use the following steps to decide on terms:"
+    },
+    {
+      "type": "guideline",
+      "content": "What's the context — the workflow or scenario — for where a term will appear? That will help you determine who you’re speaking to, with what language."
+    },
+    {
+      "type": "guideline",
+      "content": "Different deliverables will each have their own audience. For example:"
+    },
+    {
+      "type": "guideline",
+      "content": "Are you creating something for internal builders (designers, engineers, anyone creating products) at Adobe? Or are you creating something for an external user?"
+    },
+    {
+      "type": "guideline",
+      "content": "Be specific about who you’re speaking to. If you're speaking to an internal audience looking at design direction for how to build UI, that’s a different audience from the users who will ultimately work with the UI."
+    },
+    {
+      "type": "guideline",
+      "content": "Will the term appear as a UI string (such as the title of a panel)? Would it appear as a label in an image that shows the anatomy of different parts of the component?"
+    },
+    {
+      "type": "guideline",
+      "content": "The main focus for most users is on the content — the information being shown, and the actions to select from — rather than where or the means by which the action is contained."
+    },
+    {
+      "type": "guideline",
+      "content": "This app framework intentionally uses the anatomy term “content area” to describe the main information or main focus in a given view, because it’s a flexible area that’s contextual to the main view of a given place in a user’s workflow."
+    },
+    {
+      "type": "guideline",
+      "content": "To create more inclusive products, describe parts of the UI in terms of function (what something does, or what something is) rather than appearance or position (such as relative direction: left, right, top, bottom)."
+    },
+    {
+      "type": "guideline",
+      "content": "Describe the actions or items available."
+    },
+    {
+      "type": "guideline",
+      "content": "Avoid describing where to find specific items or actions in relation to UI construction."
+    },
+    {
+      "type": "guideline",
+      "content": "The word panel is acceptable as a user-facing term only when there is no other way to describe the interface."
+    },
+    {
+      "type": "guideline",
+      "content": "The word rail is acceptable to use as internal jargon, but it should never be used as a user-facing term. This is because the word is about how something looks: a long, straight divider, like a slide rule or a railroad track."
+    },
+    {
+      "type": "guideline",
+      "content": "Describe the action to take on the UI."
+    },
+    { "type": "guideline", "content": "Don’t describe the UI itself." },
+    {
+      "type": "guideline",
+      "content": "“Show” and “hide” are the preferred terms to use to describe the open/close actions on the side navigation. This is for several reasons:"
+    },
+    {
+      "type": "guideline",
+      "content": "As you’re designing the UI content of your app frame using this framework, follow the Spectrum content standards for all UI text and labels."
+    },
+    {
+      "type": "guideline",
+      "content": "Most of the components that will go into your app frame design have their own associated content standards:"
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-overview/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    { "ref": "containers", "kind": "guideline" },
+    { "ref": "s2-app-frame-header-browsing-context", "kind": "guideline" }
+  ]
+}

package/guidelines/app-frame-side-navigation.json

@@ -0,0 +1,138 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/app-frame-side-navigation.json",
+  "name": "app-frame-side-navigation",
+  "title": "App frame side navigation (browsing context)",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "App frame side navigation (browsing context)"
+    },
+    {
+      "type": "guideline",
+      "content": "The side navigation is always used in partnership with the header, and never instead of it. When used, the side navigation holds the main categories of product functionality, such as workflow-related navigational items (e.g., Home, Files, Learn, Dashboards). Don’t use this for categorizing marketing pages."
+    },
+    {
+      "type": "guideline",
+      "content": "Side navigation consists of a few parts:"
+    },
+    {
+      "type": "guideline",
+      "content": "Additionally, this button should not be used outside of the app frame context. It has unique animations between expanding and collapsing that are optimized for the app frame side navigation panel."
+    },
+    {
+      "type": "guideline",
+      "content": "Allows the side navigation to be minimized by the user."
+    },
+    {
+      "type": "guideline",
+      "content": "The partial style displays icon-only side navigation items when minimized. The full style hides the side navigation when minimized."
+    },
+    {
+      "type": "guideline",
+      "content": "Shows a create button at the top of the panel."
+    },
+    { "type": "guideline", "content": "Enables drag on the side navigation." },
+    {
+      "type": "guideline",
+      "content": "If the side navigation panel can be minimized (Can be minimized: true), dragging to the min width (expanded) will collapse the side navigation into the minimized state."
+    },
+    {
+      "type": "guideline",
+      "content": "The minimum width that the side navigation panel can be adjusted to."
+    },
+    {
+      "type": "guideline",
+      "content": "The default width that the side navigation panel appears in."
+    },
+    {
+      "type": "guideline",
+      "content": "The text that is displayed as the label of the app frame side navigation item, to supplement the icon."
+    },
+    {
+      "type": "guideline",
+      "content": "Hides the label, making the app frame side navigation item icon-only."
+    },
+    {
+      "type": "guideline",
+      "content": "The number of lines that is shown before the label is truncated."
+    },
+    {
+      "type": "guideline",
+      "content": "After the user clicks on an app frame side navigation item, the left visual bar will turn gray-800, text will bold, and color will change to content-neutral."
+    },
+    {
+      "type": "guideline",
+      "content": "Changes the side navigation item to the disabled state."
+    },
+    {
+      "type": "guideline",
+      "content": "The text that is displayed as the label of the tooltip."
+    },
+    {
+      "type": "guideline",
+      "content": "Use the overlay variant of the app frame: side navigation (browsing) component for smaller breakpoints. The overlay is triggered via the hamburger menu in the header (rather than a touchpoint at the bottom)."
+    },
+    {
+      "type": "guideline",
+      "content": "Although 768 px is the recommended breakpoint to begin displaying the overlay designs, each product team should determine which breakpoint best suits their needs."
+    },
+    {
+      "type": "guideline",
+      "content": "The divider at the bottom of the side navigation is an intentional visual element that separates overflow side navigation items and end section items from the state control icon."
+    },
+    {
+      "type": "guideline",
+      "content": "The end section is optional and used to contain navigation items in a separate category that is secondary to the main navigation items. Categories, when defined, should readily communicate a clear purpose and be meaningful to users. Items placed here sit on a separate area. When resized to a smaller height, the items should append onto the start section and scroll together."
+    },
+    {
+      "type": "guideline",
+      "content": "The minimum width is customizable, depending on the number of levels:"
+    },
+    {
+      "type": "guideline",
+      "content": "If the side navigation contains user-generated content (like shortcuts to folders and files), enabling resizing can be a good way to improve usability by respecting user content, without needing to predict the length of labels that users might input."
+    },
+    {
+      "type": "guideline",
+      "content": "Along with being descriptive, the labels of navigation items should be succinct. Keep navigation strings to 1 or 2 and no more than 3 concise words (in U.S. English, which is the source locale). Reduce any unnecessary words in order to ensure simplicity."
+    },
+    {
+      "type": "guideline",
+      "content": "Navigation items should never be so long that they require truncation, except in instances where navigation is user-generated (e.g., folder and file names)."
+    },
+    {
+      "type": "guideline",
+      "content": "If possible, the default width should auto-adjust to the longest string in the navigation in order to accommodate all translations. As a last resort for long strings, specific line breaks can be built into the implementation. These line breaks depend on the content, and requires manual handling by Globalization engineers."
+    },
+    {
+      "type": "guideline",
+      "content": "When navigation items are shown in both the side navigation and header at the same time, the hierarchy and relationships between them become unclear. If the side navigation is used, don’t put any navigation items in the header."
+    },
+    {
+      "type": "guideline",
+      "content": "Supporting multiple states (default, and partial or fully minimized style) provides users with the option to choose their preferred layout based on their own preferences. In user studies, individual preference is the biggest factor when it comes to whether or not people want to view labels by default."
+    },
+    {
+      "type": "guideline",
+      "content": "If supporting multiple states, consider showing the side navigation in the expanded state by default, and preserve user preferences across pages and sessions. If minimizing the side navigation is not supported, show the side navigation in the expanded state. Showing labels by default increases recognition and familiarity."
+    },
+    {
+      "type": "guideline",
+      "content": "There are some app frame-specific constraints for the side navigation. Icons are required at the parent level. Nested items can have no icon, but the parent level must have an icon."
+    },
+    {
+      "type": "guideline",
+      "content": "Diagram describing notes about the side navigation for the app frame, in the editing context. While toolbars share the same location as the app frame side navigation in a browsing context, toolbars in an editing context serve a different purpose: to readily select commonly used tools, rather than to navigate between pages. The behavior and interaction of toolbars doesn’t need to mirror the side navigation and should instead best serve user needs in an editing context. For example, the option to show and hide tool labels can be an additional customization option and doesn’t need to be controlled by the hamburger menu, which is used to display the application menu in Creative Cloud."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/app-frame-side-navigation/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    { "ref": "s2-app-frame-header-browsing-context", "kind": "guideline" },
+    { "ref": "s2-app-frame-content-area-browsing-context", "kind": "guideline" }
+  ]
+}

package/guidelines/attention-hierarchy.json

@@ -0,0 +1,42 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/attention-hierarchy.json",
+  "name": "attention-hierarchy",
+  "title": "Attention hierarchy",
+  "category": "designing",
+  "documentBlocks": [
+    { "type": "purpose", "content": "Attention hierarchy" },
+    {
+      "type": "guideline",
+      "content": "Design systems are ultimately communication systems. A main goal of any kind of UI communication — visual, linguistic, motion, and more — is to convey a message in a way that the audience can readily understand what they need to know and why it matters. And most importantly, communication needs to be respectful of user attention."
+    },
+    {
+      "type": "guideline",
+      "content": "**Attention hierarchy** is a core concept in Spectrum 2. This idea has always been a part of Spectrum as a design system — and a tenet of responsible UX design as a whole — but it's now more formalized as a way to validate assumptions using clear guidelines and considerations. It's based on the methods of typographic hierarchy, where scale, size, and text pairings help readers to readily recognize what's the most broad and important information to the most detailed and nice-to-know information. We've extended this practice beyond just text and into all the ways that UI communicates."
+    },
+    {
+      "type": "guideline",
+      "content": "Another way to think of attention hierarchy is as a way to manage the ratio of signal-to-noise in an experience. Different parts of the UI all communicate meaning, at different levels of attention. High attention elements show a primary area of focus, and communicate timely, high-signal meanings. Low attention elements blend into the background, and communicate more utilitarian, lower-priority meanings. Things like object styles, component options, and typography all draw different levels of attention."
+    },
+    {
+      "type": "guideline",
+      "content": "High attention elements should be used sparingly and selectively. If too many things are high attention at once, the experience becomes noisy and unfocused. For example, both high-contrast colors and elevation communicate specific meanings and add emphasis within pages and flows — and these are both used very thoughtfully."
+    },
+    {
+      "type": "guideline",
+      "content": "As a general rule, only one element or group of elements should have high attention on a page. Too many elements drawing high attention makes it difficult to focus."
+    },
+    {
+      "type": "guideline",
+      "content": "**Good example:** The \"Share\" button is the most timely and high-impact action to take in this example. It's high attention because the next step after finishing creating something within the canvas would be to share it."
+    },
+    {
+      "type": "guideline",
+      "content": "**Bad example:** The \"Share\" button is competing with the selected states of items in the navigation. These navigational items are still important for communicating wayfinding and context, but are not as timely as the action of sharing."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/attention-hierarchy/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"]
+}

package/guidelines/background-layers.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/background-layers.json",
+  "name": "background-layers",
+  "title": "Background layers",
+  "category": "designing",
+  "documentBlocks": [
+    {
+      "type": "guideline",
+      "content": "Layer 2 is the color of the canvas. This background layer color can also be used in both professional and lightweight editing applications, in the app frame, to put it on the same dimension as the primary content."
+    },
+    {
+      "type": "guideline",
+      "content": "Layer 1 can be used as the app frame color in professional editing applications, which require additional depth differentiation."
+    },
+    {
+      "type": "guideline",
+      "content": "The pasteboard has a dedicated background layer. This is because no components are placed directly on top of it, with the exception of an artboard (which uses a white background color). Other components should be placed on a layer 1, layer 2, or elevated background."
+    },
+    {
+      "type": "guideline",
+      "content": "This example shows an editing application using background layer 2 for both the artboard and the app frame. An elevated background is used for a floating toolbar, which appears on top of the canvas."
+    },
+    {
+      "type": "guideline",
+      "content": "Spectrum 2 uses gray-25 as the base background color to draw attention to the primary content of a page. Using gray-25 allows for higher contrast between the background and content, and it provides a blank canvas for more vibrant colors."
+    },
+    {
+      "type": "guideline",
+      "content": "In dark theme, the primary background (using the background base layer) is the darkest color. This allows for more flexibility for the grays that are layered on top of it, and provides contrast for more vibrant user-created content."
+    }
+  ],
+  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/background-layers/",
+  "lastUpdated": "2026-02-02",
+  "status": "published",
+  "tags": ["designing"],
+  "related": [
+    { "ref": "colors", "kind": "guideline" },
+    { "ref": "typography-fundamentals", "kind": "guideline" }
+  ]
+}