Omlet Docs
BlogChangelogAsk the CommunityContact Sales
  • Get started
    • What is Omlet?
    • CLI & Dashboard
  • Omlet for VS Code
  • CLI & Dashboard
    • CLI
      • Your first scan
      • Set up your dashbard
      • Future scans
      • Ensure data accuracy
      • Config file
        • Exports configuration
        • Mapping aliases
        • Excluding certain components & files
        • Tutorial: Config file
      • Custom component properties
        • CLI hooks
        • Tutorial 1: Team/code owner usage
        • Tutorial 2: Package version tracking
        • Other example scripts
      • Set up regular scans
      • CLI commands
        • init
        • analyze
        • login
    • Analytics
      • Popular charts
      • Create custom charts
      • Save charts to dashboard
      • Share charts and dashboards with your team
      • Download chart data
    • Components
      • Search and filter components
      • Component tags
      • Dependency Tree
      • Props tracking
    • Workspace & Account
      • Invite team members
      • Renaming projects
      • Update your email address
      • Access your billing details & invoices
  • Security
    • Security in Omlet
    • Data collection
  • Help
    • Pricing
    • FAQs
      • How detection works?
      • Monorepo support
      • How to delete scans?
      • Omlet vs. React Scanner
      • Working with multiple workspaces
    • Troubleshooting
      • Debugging CLI issues
      • Some components aren't detected
      • API failed or timeout
      • Are you behind a proxy?
      • Troubleshooting Git errors
Powered by GitBook
On this page
  • Tag your design system components
  • Create more tags
  1. CLI & Dashboard
  2. CLI

Set up your dashbard

Your component scan is completed. Let's buckle a few things up to start analyzing your design system.

PreviousYour first scanNextFuture scans

Last updated 1 year ago

After the first scan, Omlet will take you through a 3-step process to tag your components on the Web app. These tags will be used to reference your design system components as well as other sets of components in the analytics dashboard.

Tag your design system components

First, you'll need to name a tag that represents your design system components. Feel free to choose any name you want. If you're not sure yet, most teams usually go with names such as "Core", "Library", or "UI Kit". Then, you can select which packages or folders contain these components from the packages list on the right.

No design system components?

If you don't see your design system components, make sure its repository is scanned. You can head to the root of the repository and run:

npx @omlet/cli analyze
yarn dlx @omlet/cli analyze
pnpm dlx @omlet/cli analyze

Create more tags

You can create more tags to identify different components as well—let's say you can tag legacy components that you deprecated here.

This step is optional. No need to do this right away — you can always later on.

Congrats! You completed the setup. Omlet will redirect you to the Analytics page, where you can get insights into your components.

🥳
adjust your tags