name: Tiles description: Visual components that display content in a card-like format with media elements, ideal for presenting items in grid layouts or lists. category: Layout slds_classes: root: slds-tile elements: - class: slds-tile__detail description: Main content area of the tile purpose: Contains title, description, and metadata - class: slds-tile__meta description: Metadata container purpose: Additional information about the tile content modifiers: - class: slds-tile_board description: Board-style tile for kanban layouts usage: Tiles used in board or kanban interfaces states: - class: slds-is-selected description: Selected tile state trigger: When tile is currently selected - class: slds-has-focus description: Focus state for interactive tiles trigger: When tile has keyboard focus variants: - name: Base description: Standard tile with media and content classes: - slds-tile usage_context: Default tile implementation for content display differences: Media object pattern with visual element and content lightning_component: name: lightning-tile url: https://developer.salesforce.com/docs/component-library/bundle/lightning-tile mapping_notes: Direct mapping - Lightning component implements SLDS tile blueprint accessibility: keyboard_support: - Tab to focus interactive tiles - Enter/Space to activate tile actions - Arrow keys for grid navigation when appropriate screen_reader: - Tile content and purpose announced - Media elements described appropriately - Selection states communicated - Associated actions clearly identified aria_attributes: - aria-labelledby for tile titles - aria-describedby for tile metadata - role='button' or 'link' for interactive tiles - aria-selected for selectable tiles usage_guidelines: when_to_use: - For displaying collections of related content - In grid layouts showing multiple items - For content previews or summaries - When visual hierarchy with media is beneficial when_not_to_use: - For simple text lists (use list components) - When media elements are not relevant - For complex interactive content (use cards instead) best_practices: - Use consistent tile sizing within collections - Provide meaningful titles and descriptions - Choose appropriate media elements - Maintain good visual hierarchy - Support keyboard navigation for interactive tiles common_mistakes: - Inconsistent tile sizes in the same collection - Poor media element choices - Unclear or missing tile labels - Overloading tiles with too much information code_examples: - title: Basic Tile code: "