Skip to main content

Create own Components/Modules

Feature Request

Requirements

  • Allow Users to create own components which could be reused on program and/or file-level

  • A Custom component could also be able to create own states like hover, focus, checked, selected or maybe even a custom state

  • Allow users to edit the source component if needed, which will overwrite the original

  • Import/Export via a common format like YAML/JSON

Posted by Devinside ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Devinside

    •

    Mar 14, 2025

    Amazing Job thank you!!! After some extending Testing, I would have some suggestions:

    • Child Elements have to be always converted to a Component to access the extended Features. Could you introduce an another Switch, called “Child-Component”? It would behave like a component as long as it’s inside of a real component, but would be excluded in the component-file or alternatively → a switch for exclude from Library

    • Could you extend “inherit-styles” with for example accordeons and checkboxes? For example: I want to inherit from the font-styles only the color, but not the font or anything else?

    • Could you extend “set-state-from-property” to overwrite any style option? For example if I have a boolean switch on false, it would set padding-left to 10px, If I turn it on, it could set it to 25px. For the Style-Options, there could be a select with optgroups of all availbable options from the inspector to select from

    Thank you for this huge update! It’s a game changer! Only those points and custom color-palette and I might be the happiest F0-User!!!!