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

package/guidelines/manifest.json

@@ -8,30 +8,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/support/ai-resource-guide",
       "file": "guidelines/ai-resource-guide.json"
     },
-    {
-      "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",
@@ -40,14 +16,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/foundations/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": "applying-the-type-system",
       "title": "Applying the type system",
@@ -128,14 +96,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/support/contact-us",
       "file": "guidelines/contact-us.json"
     },
-    {
-      "slug": "containers",
-      "title": "Containers",
-      "category": "designing",
-      "status": "published",
-      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/containers/",
-      "file": "guidelines/containers.json"
-    },
     {
       "slug": "content-area-browsing-context",
       "title": "Browsing context: Content area",
@@ -232,14 +192,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/foundations/visual-language/illustration",
       "file": "guidelines/illustration.json"
     },
-    {
-      "slug": "illustrations",
-      "title": "Illustrations",
-      "category": "designing",
-      "status": "published",
-      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/illustrations/",
-      "file": "guidelines/illustrations.json"
-    },
     {
       "slug": "in-product-word-list",
       "title": "In-product word list",
@@ -277,7 +229,7 @@
       "title": "Introduction",
       "category": "fundamentals",
       "status": "published",
-      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/introduction/",
+      "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/getting-started/introduction",
       "file": "guidelines/introduction.json"
     },
     {
@@ -304,14 +256,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/foundations/behavior/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": "object-styles-overview",
       "title": "Object styles",
@@ -325,7 +269,7 @@
       "title": "Principles",
       "category": "fundamentals",
       "status": "published",
-      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/principles/",
+      "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/getting-started/principles",
       "file": "guidelines/principles.json"
     },
     {
@@ -352,14 +296,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/foundations/app-frame/side-navigation-browsing-context",
       "file": "guidelines/side-navigation-browsing-context.json"
     },
-    {
-      "slug": "spacing",
-      "title": "Spacing",
-      "category": "designing",
-      "status": "published",
-      "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/spacing/",
-      "file": "guidelines/spacing.json"
-    },
     {
       "slug": "spacing-overview",
       "title": "Spacing overview",
@@ -376,14 +312,6 @@
       "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/foundations/behavior/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": "typography-overview",
       "title": "Typography",

package/guidelines/principles.json

@@ -23,8 +23,8 @@
       "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",
+  "sourceUrl": "https://main--spectrum-hub--adobe.aem.live/getting-started/principles",
+  "lastUpdated": "2026-09-17",
   "status": "published",
   "tags": ["fundamentals"]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adobe/spectrum-design-data",
-  "version": "3.3.0-beta.0",
+  "version": "3.3.0-beta.1",
   "description": "Spectrum design tokens in cascade format — the canonical source of truth for @adobe/spectrum-tokens",
   "type": "module",
   "repository": {

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

@@ -1,81 +0,0 @@
-{
-  "$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" },
-    { "ref": "s2-app-frame-creating-bluelines-browsing-context" }
-  ]
-}

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

@@ -1,58 +0,0 @@
-{
-  "$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" },
-    { "ref": "brand" }
-  ]
-}

package/guidelines/app-frame-header.json

@@ -1,72 +0,0 @@
-{
-  "$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" },
-    { "ref": "s2-app-frame-side-navigation-browsing-context" }
-  ]
-}

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

@@ -1,138 +0,0 @@
-{
-  "$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" },
-    { "ref": "s2-app-frame-content-area-browsing-context" }
-  ]
-}

package/guidelines/containers.json

@@ -1,62 +0,0 @@
-{
-  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/guideline.schema.json",
-  "$id": "https://opensource.adobe.com/spectrum-design-data/guidelines/containers.json",
-  "name": "containers",
-  "title": "Containers",
-  "category": "designing",
-  "documentBlocks": [
-    {
-      "type": "purpose",
-      "content": "Examples of containers: two cards with different sizes and layout options, and a select box.\"\n\nAll containers share a set of defined styles.\n\nInternal padding is dependent on component size, density, and platform scale, all of which vary for specific components and patterns.\n\nThis medium card uses spacing-300 for internal padding.\n\nNote that specific components might have different options and states.\n\nExample of an app frame with a side navigation."
-    },
-    {
-      "type": "guideline",
-      "content": "Containers separate concepts with distinct purposes."
-    },
-    {
-      "type": "guideline",
-      "content": "In Spectrum 2, containers have more defined rules to help guide in the creation of custom containers for product-specific contexts. Containers are used across Spectrum 2 interfaces in multiple ways, but the commonality they share is that they group related concepts together into distinct areas. Some usages of containers have more detailed guidelines."
-    },
-    {
-      "type": "guideline",
-      "content": "For example, a card uses a container and inherits its properties, but it can only represent a distinct object (such as an individual asset or product). A block of marketing material containing multiple concepts (like subscription information plus actions to take) is grouped together in a container, but is not considered a card. Whether broad or specific, a user should be able to readily tell the purpose of a container."
-    },
-    {
-      "type": "guideline",
-      "content": "Examples of containers: two cards with different sizes and layout options, and a select box."
-    },
-    {
-      "type": "guideline",
-      "content": "All containers share a set of defined styles."
-    },
-    {
-      "type": "guideline",
-      "content": "Internal padding is dependent on component size, density, and platform scale, all of which vary for specific components and patterns."
-    },
-    {
-      "type": "guideline",
-      "content": "This medium card uses spacing-300 for internal padding."
-    },
-    {
-      "type": "guideline",
-      "content": "In this group of containers — each representing a product — different container styles can be used to draw attention to a specific item. In this case, the emphasized container is paired with a badge, and contrasts against the more subdued containers with filled (gray) backgrounds."
-    },
-    {
-      "type": "guideline",
-      "content": "Note that specific components might have different options and states."
-    },
-    {
-      "type": "guideline",
-      "content": "A consistent app frame helps create a sense of brand unity and helps users feel comfortable and familiar with our products. Predictable navigation is also especially helpful for users who work across multiple applications, and it makes it easier to learn how to use new products."
-    },
-    {
-      "type": "guideline",
-      "content": "Example of an app frame with a side navigation."
-    }
-  ],
-  "sourceUrl": "https://s2.spectrum.corp.adobe.com/page/containers/",
-  "lastUpdated": "2026-02-02",
-  "status": "published",
-  "tags": ["designing"],
-  "related": [{ "ref": "states" }, { "ref": "s2-app-frame" }]
-}