Component Marketplace

Templates are great, but wouldn't it be awesome if the template marketplace on Webflow had a section with individual elements that you could clone and use within your site without having to start a whole new site to get a feature you like from a template.

For example, an individual blog post container that you could copy and paste into your custom site. This would save a lot of time designing and building out interactions/transitions if there were a marketplace that contained these individual pre built items that you could use wherever you like.

  • Justin Dalzell
  • Jan 18 2017
  • In backlog
  • Aug 3, 2018

    Admin Response

    As promised, our first step toward a user component system was shipping copy and paste between projects in April, which has spawned a growth of cloneable UI kits (and hopefully made many of your lives a lot easier, as it has ours).

    We’re now working on Components to rehaul and dramatically improve what’s possible with symbols: think nestable (symbols within symbols), overridable styles, and ultimately, easy sharing across projects. We’re still in the initial planning phases of this project so can’t share timelines, but know that we’re thinking long term on this challenge and have exciting developments in the works. Once we launch Components, that will lay the foundation for a larger, collaborative “marketplace” of shareable, user generated components.

  • Jason Zucchetto commented
    January 18, 2017 04:35

    Great idea, modifying the title from "Individual Pre Built Elements within the Template Marketplace" to "Component Marketplace".

  • Ed Bini commented
    January 18, 2017 08:33

    Sounds good I like this idea. 

  • Roberto Virili commented
    January 18, 2017 11:39

    This would be fantastic.

  • Juan Manuel Garrido commented
    January 18, 2017 16:34

    +1 for this awesome feature!

  • Brian Hermelijn commented
    January 18, 2017 18:18

    I am wondering if that would initially kill the idea of "having a template" altogether, seeing that a template is an all in one package, so how would lets say the pricing be justified, if someone only pays an individual build component?

    Unless you specifically mean purchasing a template, and have the ability to transfer just one component to your project.

  • Martijn Hoppenbrouwer commented
    January 19, 2017 11:26

    I think this is a must-have for Webflow. It will boost the community to create specific solutions with specific components and also profit from them - and in the end the users of these components will benefit from more (prebuild) components and boost their quality and production-rate. As of today, there are too many templates which just don't exactly match all the needs for a project.

  • Timothy Noah commented
    January 19, 2017 15:44

    Interested to see how this idea develops...

  • Andrew Reaney commented
    January 20, 2017 13:29

    This might be the "It" that webflow really needs to transcend.

  • Jake V commented
    January 22, 2017 02:30

    ALLL OF MY YES on this one.

  • Otto Berger commented
    January 22, 2017 09:02

    exactly! also re-using interactions/symbols across sites would be awesome!

     

  • Oliver Curting commented
    February 03, 2017 20:30

    I'd love contributing with components through a marketplace. Would be great.

  • Jan Haas commented
    February 08, 2017 16:05

    Reminds me on how http://blocsapp.com/ does it. "Would make webflow greater again" :) 

  • Dave Williams commented
    February 10, 2017 09:11

    Really interesting idea! I think some kind of component review would be needed, the last thing we want is a marketplace filled with poorly constructed components. Looking forward to see how this idea develops.

  • Masarati Pietro commented
    February 17, 2017 23:29

    I'm really in love of WebFlow, and I think as well that a collection of premade components can be helpfull for speeding up the building of some sections. Another platform for making websites (not comparable to Webflow) is offering like this (see attachement).

    Maybe it is an idea to implement in Webflow.

  • Tayler Odea commented
    April 06, 2017 14:41

    this could get dangerous for selling themes and templates, how would licensing work, components would all have to be GPL 

  • Gonsalves Media commented
    April 07, 2017 19:59

    Great idea. 10/10 would buy + build components

  • Improve Webflow commented
    May 08, 2017 22:55

    Or maybe integrations with Webflow? Say, maybe a dynamic element? Or e-Commerce?

  • Scott Van Zandt commented
    May 26, 2017 01:26

    A marketplace for the community to share these elements (after being approved by Webflow) would be great. Either share them for free or simply charge a monthly rate to have access to everything. Designers who contribute get paid for the popularity of their element/widget. 

  • Brandon commented
    June 02, 2017 21:21

    Honestly, this could be tied into the #1 trending wishlist item right now: cross site copy/paste. You would need the ability to "copy" individual elements or symbols into your site not only from one of your sites to another but from a general public marketplace (just like themes).

  • Matthew Oliver commented
    May 01, 2018 23:14

    Expect to see some crazy stuff on the market when this gets released :)

  • Mario Gonzalez commented
    August 07, 2018 12:22

    This is going to be beyond Awesome. We are currently looking for a tool that allows us to create a design system. We've tried sketch, InVision, Figma, Atomic, Framer but they lack what we can do in Webflow for high-def prototyping. "Components" as you describe them above will be a game changer since every tool out there is trying to be THE TOOL to build design systems. You have a clear advantage in IMO since you do actual html/css/js and not just static representations. If you get this right and communicate its power to the world, you will be THE TOOL.  

  • Robert Cat commented
    September 28, 2018 21:24

    That's just a dream feature

  • Andu Potorac commented
    November 21, 2018 18:21

    I can't wait to see how the Marketplace will work when ready!

    As we integrated different components across multiple publishing platforms (Shopify, Weebly, CloudFlare, Wix, etc), I'm excited to add our library to Webflow as well!

    A few notes:

    - content should be dynamic (to work with the backend)
    - there should be a store front with reviews and most popular apps
    - components should be completely responsive
    - users should be able to subscribe to each component as a SaaS product

    Cheers!

  • Pierluigi Giglio commented
    December 24, 2018 12:17

    This is such a Great idea: I would LOVE a components marketplace since this would make our lives soo much easier!

  • Rodney commented
    28 May 21:25

    I would suggest that you drive towards the same goal that the entire HTML specification is moving towards - reusable custom HTML components.  Essentially the ability to define new elements - i.e. <my-banner color="red">This is banner text</my-banner> or <login-form/>.  These custom elements will be first class citizens of HTML - complete peers with existing elements like <div> or <ul>.  This is where HTML is going, and it's the sole reason for the existence of all of the most popular web development frameworks (vue, angular, react).

    Add a Vue container to your existing palette.  The user then puts whatever he/she wants in it, including existing elements and other other previously created components.  When finished, the user drags it back to the palette where it is given a name.  From that point onward, the new component would be used exactly the same as any other palette element.

    Whatever is in the component would be written out as a fully encapsulated vue single file component (a .vue file) with its own template and scoped CSS.  And BTW, don't even think about shipping this feature without the ability to nest components to any desired level.

    Do this, and your product will suddenly become much more than the design and prototyping tool it currently is - supporting this would make it feasible for use by business systems developers - essentially increasing your potential user base by orders of magnitude.  I would guess that for the most part, your primary customers are design teams and UI/UX persons.  I know that in its current state, your tool can only be used to provide an overall look and feel for enterprise level developers to mimic in their development efforts - the best of these may be using the code your tool generates, but probably no one or very few are doing it seamlessly via automation.

    Supporting the creation and use of reusable custom components would open the door to your tool becoming a staple of nearly every enterprise developer in the world - and the vast majority of them are all moving towards the use of reusable components.  For every design user you may have, there would be anywhere from a handful to hundreds of enterprise level developers.

    With the ability to visually construct component based forms and pages, your product would be more valuable than platinum to their employers. 

    Doing this would pretty much obsolete the need for classes and Symbols - A component could encapsulate both of those in a much more intuitive and concrete manner.   CSS in a component does not effect anything outside of that component.