Forking native WeWeb components to use as Coded Components

WeWeb keeps releasing and improving its native components over time, and many of them are great.

However, every now and then we run into some limitations with these components. In those cases, it would be extremely useful to be able to “fork” a native component and use it as the base for a Coded Component.

This would allow us to:

  • Reuse the entire structure and design already built by WeWeb,

  • Make only the necessary adjustments (e.g., adding extra functionality, customizing behaviors, or changing interactions),

  • Avoid the heavy work of rebuilding a component from scratch — which often involves replicating design settings, layout, styles, and more.

I couldn’t find a way to do this directly through the editor.
Is there any official or alternative way to fork a native component — maybe through GitHub or another method — so we can build on top of it instead of starting from zero?

Hi Artur :waving_hand:

You can fork almost any element, you just need to click on the 3 dots and > Fork component

Wow, I totally missed that “Fork component” option :grinning_face_with_smiling_eyes:
Thanks a lot for pointing it out — super helpful!

1 Like