What is Infa
Infa Chrome Extension
How to use and install our Chrome Extension
Community
Browse community design systems
Release Notes
Featuring the latest changes to keep you up-to-date
Research Program
Participate in shaping the future of Infa
SOC 2 Type II Compliance Badge
Enterprise Ready
SOC 2 Type II certified for enterprise-level security and compliance
EventsLearnPricing
Sign up for free

Feedback

Share your feedback

Close
Anonymous submissions are auto-posted to #feedback channel. You can also share directly in Slack.

Need help?

Reach out to contact@infa.ai or see docs

Navigation
Search...
⌘ K
Focus sentinel
Close

Search Documentation

PressESCto close
Focus sentinel
Infa Documentation
  • General Information
    • Boards
    • Components
      • Main Components Vs Component Views
      • Component Tagging
      • Component Anatomy
    • Labels
    • Teams
    • Authentication
    • Permissions
      • Inviting People to Teams
      • Inviting People to Boards
    • Billing & Subscription
      • Managing Subscription
      • Promo Code Activation
    • Data Import, Export & Sync
      • Local vs. Cloud Boards
  • App Blocks
    • Building App Blocks
  • Chrome Extension
    • Deep Links
    • Using Labels
    • Updating the Extension
  • Integrations
    • MCP Server
    • Claude Code Plugin
    • External API
    • Progressive Web App
    • Figma Plugin
    • Coda Pack
    • Overview
    • Managing Runs
    • Board Agents
    • Overview
    • Infa Capture
    • Installation
    • Authentication
    • Connect a Board
    • Run Modes
    • Hooks & Agents
    • File Sync
    • CLI Reference
Switch to Light theme
Switch to Dark theme
TermsPrivacyChat with Us
  1. Docs
  2. General Information

Boards: Organization, Collaboration & Discovery

Learn about the concept of boards in Infa, their types, use cases, and best practices for effective component organization and collaboration.

Copy link
What are Boards?

Boards in Infa serve as containers for organizing, managing, and sharing your components and screens. Similar to Miro boards, Figma files, or Jira projects, boards provide a structured way to categorize and access your design system assets.

We at Infa have designed boards to be flexible and adaptable to various workflows, whether you're documenting your design system, researching competitors, or collaborating with team members.

Copy link
Key Use Cases for Boards

  • Boards excel as onboarding tools for design systems. By creating a comprehensive board of your components:

    • New team members can quickly understand your design system's structure
    • Components can be viewed in their actual implementation context
    • Documentation links and usage guidelines can be centralized
  • Boards serve as excellent research and analysis tools:

    • Collect and organize components from various websites and products
    • Compare different implementation approaches side by side
    • Track emerging design patterns across the industry
    • Organize components by competitor
    • Track changes to competitor interfaces over time
    • Compare your own components against industry standards
    • Identify gaps or opportunities in your design approach
  • Boards help you plan and implement design system adoption across products:

    • Track inconsistent components that need standardization
    • Create roadmaps for future design system enhancements
    • Identify components requiring refactoring or replacement
    • Link components across products using XPath selectors to visualize impact
    • Prioritize design system work based on usage patterns
    • Monitor design system adoption progress across products

Content Feedback

Feedback on selected content

Close
Anonymous submissions are auto-posted to #feedback channel. You can also share directly in Slack.

Need help?

Reach out to contact@infa.ai or see docs

Nextmain-components-vs-component-views