LogoLogo
Quest HomeSign Up
  • 😀Welcome to Quest
  • Getting Started
    • Quest Overview
    • Helpful Resources
    • Quick Start - Build your first component from Figma
    • Quick Start - Build your first component from a Wireframe
    • AI Prompt
  • Fundamentals
    • Customizing & Using the UI Kit
    • Designing Custom Components in Figma
    • Easily Sync Designs without Losing Work
    • Setting Up Props & Bindings
    • Exporting Code
    • Push to your Repository
    • Creating Responsive Components
    • Nesting Components
    • Workspaces & Apps
    • Code & Preview Mode
    • Prototypes/Wireframes
    • Animations - build with React Spring
    • Quest plugin for Figma Dev Mode
    • Publish on Quest to a URL
  • Features
    • Working with Variants & States
    • Naming Conventions
    • Previewing with Custom Fonts
    • Light & Dark Mode
    • Creating a custom Tooltip
    • Creating a Floating Popover
    • Creating a Dialog pop-up
    • Radio Group
    • Using the MUI Data Grid & Table
    • Data & List Bindings
    • Dynamic Bindings
    • Grid
    • File Upload
    • Design System Tab and Theme Import
    • How-to use a Theme in your Application
    • Accessibility Support
    • Design Tips and Tricks
    • Video
    • Lazy Loading
    • Sticky Position
    • Link
    • Custom Breakpoints
    • Min / Max Width
    • Supported Quest UI Kit Components & How-to Make Edits in Figma
    • Supported Chakra Components & How-to Make Edits in Figma
  • Advanced Tutorials
    • Setting up Bindings and Features on the MUI Button
    • Display Repeating Components based on a Dynamic List
    • How-to Pass Values from Parent to Nested Components
    • How-to Invoke a modal Dialog Box from a Button Click
    • How to Setup a popover
  • 🔍Help
    • Product Updates
    • FAQs
    • Plugin Warnings / Alerts
  • 💡Support
    • Why does my design look different in Quest than Figma?
    • Can I keep making changes in Figma without affecting code?
    • What are some best practices?
    • Does Quest support more than Figma and React?
    • How do I manage users?
    • What is the refund process?
    • How do I get in touch with Quest?
    • Do I have to use MUI if I'm using Quest?
Powered by GitBook
On this page

Was this helpful?

  1. Features

Design System Tab and Theme Import

How to sync, import and export your theme files

PreviousFile UploadNextHow-to use a Theme in your Application

Last updated 1 year ago

Was this helpful?

When you press the "Design Sytem" tab it will take you to the Design System tab for the App you're working on. When you start with Quest, by default, we seed the Quest Design Kit as the design system for your App. The Quest Design Kit is based on MUI so if you've picked a Chakra App, the seeded design system will be based on the .

From here, you can view information about the theme files for the design system. In the top-left you can rename the Design System / Theme files to match what you'd prefer. On the top-right side you'll see which Component library the theme files are from, either MUI or Chakra UI as well as the NPM Version it is coming from.

If you're using Quest Design Kit or MUI 5.9 Kit, you'll see 2 theme files. If you're using Chakra UI or MUI 5.11, you'll only see the one theme file as those kits are not set up by default to support dark and light mode.

If there are any issues and your components are not working properly, you can always "Restore" back to the last synced or possibly the seeded theme. This ensures you will never break your App and can always rollback to a working version. If "Restore" is disabled, your most recent Theme file is from your design system sync. You can make the necessary changes in your Design System and sync it or you can download the Theme file from Quest, modify and upload it directly within Quest.

When importing theme files, declared variables in light and dark theme files must have different names in order to allow for Dark/Light Preview in Quest. Each module should have a default export of a theme. Icons from imported files are currently not supported in preview/edit mode. We still honor them in exported App but you will not see them in Quest Editor. Icons must be added manually to the folder from which they are imported in theme module. Please note we are using absolute path and theme file path is 'src/'.

Below that you'll see information about the latest sync or import of the design system / theme files. "Last Sync" or "Last Import" will give you a time or day. Additionally "Synced by" or "Imported by" will show what user took the last action. "Synced From" will show what Figma file by name was the used for the Sync to help keep track in case you have multiple files. This section is designed to help keep teams in sync while working on theme files.

Below that, you'll see information about the actual theme files used in your Application. First you'll see the name of the themes. The theme source can be either "Seeded", "Synced" or "Imported" to tell you where the theme comes from. Syncing a design system is done by . Importing a theme is done through the "Import" button on the right side. You can additionally "Download" the theme files to view them locally. If there are any errors with imported theme files, you may see an error alert to warn you of issues.

In the bottom section, you'll find help links relevant to the design system / component library that you're using for your App. Additionally, you can choose what is the default view in Quest Editor when looking at components: . Light and Dark mode can easily be toggled in the Quest Editor to see either but this will simply help start the Quest Editor in your mode of choice.

modifying a Figma design kit
Light or Dark mode
Chakra Design Kit
Design System Tab