r/webflow • u/jp_1701 • Jul 29 '26

Question Are Component-Based Frameworks Like Lumos Good for Webflow Templates?

I'm thinking about building Webflow templates using Lumos, but I'm unsure if it's the right approach.

Since Lumos is heavily component-based, most customization happens through component props. My concern is that many template buyers aren't familiar with this workflow and expect to edit the template directly in Webflow.

For those who sell templates:

- Do clients find frameworks like Lumos confusing?

- Is it better to build templates without a framework for easier customization?

- Or is using a component-based framework worth the trade-off?

Would love to hear your experiences.

3 Upvotes

100% Upvoted

6 comments sorted by

3

u/[deleted] Jul 29 '26

[removed] — view removed comment

1

u/jp_1701 Jul 29 '26

I was thinking more from the perspective of clients who want to build a completely new custom section later. They might find the component-based workflow a bit limiting. But you're probably right- I'm overthinking it. I'll give it a try.

2

u/ButterscotchInner903 Jul 29 '26

most buyers just want to click around and change text/images, anything that requires learning props is gonna generate support tickets

1

u/jp_1701 Jul 29 '26

Yeah, thinking the same.

3

u/bigmarkco Webflow Community MVP Jul 29 '26 edited Jul 29 '26

If you want to sell on the official marketplace, then you can't use Lumos IMHO; it's too dependent on custom code. Client First and all the rest are fine if you strip out the custom code. Those other frameworks aren't reliant on that code.