Momen Docs
Go to Momen
  • Get Started
    • Introduction
    • Quick Start
    • Software Development Process
    • Editor Overview
  • Changelog
    • Latest Product Update
  • Build UI
    • Pages
    • Components
    • Canvas
    • Layout
    • Component - Display
    • Component - Input
    • Component - View
    • Component - List
    • Component - Tab View
    • Component - Select View
    • Component - Conditional View
    • Component - Others
    • Component - Map
    • Custom Component
  • Data
    • Overview
    • Data Model and Database
    • API
    • Variable
    • Parameter
    • Formula and Conditions
  • Actions
    • Overview
    • Request
    • Navigation
    • Actionflow
      • Custom Code
      • Database Trigger
    • AI
      • AI Data Model
      • AI Point
      • Vector Data Storage and Sorting
    • User Actions
    • Component Management
    • App and Page Management
    • Toast Notifications & Modal
    • Payment
    • SSO
    • Share
    • Location
    • File Management
    • QR Code
    • Clipboard
    • Conditional
    • Loop
  • Release and Growth
    • Publish Application
    • Upgrade Project
    • Multiple Clients
    • Permission
    • Log Service
    • SEO
    • Hosting Files
  • My Account and Community
    • My Wallet
    • Promoting Momen
    • Code Component
    • Collaboration
  • Debugging
    • How to Debug in Momen
    • Request Error Reference
  • Tutorial
    • How to Build an AI Needs Analysis Project?
    • How to Set Up Payment with Stripe Plugin?
    • How to Embed an Iframe Component into Your Momen Project?
    • How to Build Your Login Page?
    • How to Convert Momen App to Native Mobile App?
    • How to Build a CMS (MVP Version) in Hours?
    • How to Set a Countdown Timer When Sending a Verification Code
  • Template
    • AI Mental Health Assistant
    • Angry Dietitian
    • AI Help Center
    • AI Knowledge Base
    • SaaS Corporate Site
    • Blog
    • AI Feedback Tool
    • Feedback Tool, a Nod to Canny
    • Portfolio
    • Online Courses, a Nod to Udemy
    • Mobile Auto Repair AI Scheduler
Powered by GitBook
On this page
  • Background
  • Value
  • Scenario
  • Instructions
  • Functional Boundaries
  1. Build UI

Custom Component

Provides the capability to create Custom Components, allowing users to save configured components as Custom Components and add them to the left sidebar component library. Users can reuse them in multi

PreviousComponent - MapNextOverview

Last updated 1 day ago

Background

Building pages with finely granular components has always been popular among users. However, as the complexity of application pages increases, building the UI becomes cumbersome. We have focused on the scenario of user reusability and introduced the Custom Component feature. This feature allows users to save configured components as Custom Components and add them to the left sidebar component library, enabling reuse in multiple places within a project to enhance building efficiency.

Value

  1. Reuse in multiple places: Once a component is saved as a Custom Component, it can be directly dragged and used on all pages within the project.

  2. Collaborative efficiency: Project collaborators can directly use the saved Custom Components, improving building efficiency.

Scenario

Repeated general components: During project building, we often encounter some general components that appear repeatedly, such as top navigation bars, product lists, and user information panels. We can build the UI once and save it as a Custom Component, then drag it out from the left sidebar's Custom Component library to use on other pages.

Instructions

  1. Create: After selecting a component, save the configured component as a Custom Component through the right-click option or the shortcut cmd+shift+K. We will save all content, style, data configuration structure, and action configuration structure of the component. When there is a data dependency in the data or action configuration, users need to delete and reconfigure the configuration items.

  2. Fill in information: Enter the Custom Component panel, where we will automatically generate a preview image of the component, and users can also upload their own. Users can name the Custom Component and add a description in the panel. After clicking save, the component will be added under the left sidebar - Custom Components.

  3. Reuse in multiple places: Users can drag or double-click to add the saved component from the left sidebar - Custom Components to other pages for use. When there are too many Custom Components, users can accurately find the required component through the description in the upper right corner.

Functional Boundaries

  1. The maximum number of components that can be saved per project is 1000.

  2. Style editing is not supported.

  3. Cross-project use is not allowed.