Uncodie
Technical DocumentationNo CodeTutorialsChangelogDisccord
No Code
No Code
  • 🏁Getting Stared
    • 🥳Introduction
      • What is Uncodie?
      • App
      • Figma No Code Plugin
        • How to associate your Figma token to Uncodie?
        • How to associate an Uncodie project to figma?
  • 📖Basic Concepts
    • 🧩Components
      • Screen Page
        • Screen Layout
        • Screen Content
      • Table View
        • Table View Header
        • Table View Row
        • Table View Cell
      • Form
        • Text Area
        • Selector
        • Input
        • Button
        • Output
      • HTML components
        • Headers
          • H1
          • H2
          • H3
          • H4
          • H5
        • Title
        • Parragraph
        • List
        • Iframe
        • Video
        • Audio
        • Link
        • Progress
        • Meta
        • Image
        • SVG
      • Advanced
        • Chart
          • Style Personalization
        • Repeat
        • Loading
    • 🎨Appearance
      • Visibility
      • CSS
      • Adaptative Design
      • Responsive Design
    • 🏗️Prototyping
      • Modals
      • Variants
      • Navigation
    • 🔤Variables
    • 💽Data Sources
      • Collections
      • Queries
      • Scripts
    • 🔍Data Binding
    • ⚡Actions
      • Scripts
      • Events
    • 🧑User Management
      • Privacy
    • 🍪SEO and Tracking
      • Capabilities
      • HTML Head Scripts
    • ☁️Publish and Deploy
      • Custom Domains
Powered by GitBook
On this page

Was this helpful?

  1. Basic Concepts

Appearance

Setups and good practices for a figma element on your project

PreviousLoadingNextVisibility

Last updated 1 year ago

Was this helpful?

Getting Started

You can set component appearance details in the plugin. Uncodie will make its best effort to generate a pixel-perfect representation of your on-screen design. Nevertheless, there are some concepts and key differences that Figma does not handle in terms of web design and web development. For example, you may require a specific browser property or a dynamic value to be handled by your component in real-time. Additionally, you might need to show or hide your component depending on the user role or app state. This level of customization can ensure that your web components function seamlessly across various conditions and user interactions, thus providing a more tailored and responsive user experience.

Integrating these dynamic features allows developers to create more interactive and user-friendly applications, ultimately enhancing overall usability and performance. It's important to understand these nuances to effectively translate your static designs into fully functional web components.

📖
🎨