Feature Request: Support for Large Multi-Part Projects

MakerWorld
1

I have a project called ExoGuitar. It’s designed to be a modular system. It has at this point dozens of parts that can be pieced together in different ways. For example: I have Different face plates for Acoustic guitars versus Electric guitars; humbucker or telecaster; different wing sets; Explorer, Les Paul, Firebird; etc… Maintaining these as a cohesive experience on Makerworld is a bit challenging. The best thing available is a Category, which helps, but isn’t quite enough.

What I think I would need is a page of some kind that I can fill out as an index page for the entire project, that then links to the individual pieces, that can be customized so I can guide users through the process of picking the pieces they want. That would be perfect. Maybe this could be done by expanding the Category system to have a full WYSIWYG editor like the Model descriptions.

For an example of why this is an issue, people keep landing on one of the Wing Sets and leaving comments that are answered in the description of the core set; so I had to put a block of text at the top of every wing-set that it’s part of a larger project with a link back to the core project.

And no, I’m not just going to keep uploading the different wing-sets as print profiles of already existing projects, because they’ll get ZERO visibility and no-one will know that a new one is available.

2

you can create different collections for each part group

3

I too have thought about this. To clarify, when you say ‘Category’, do you mean Collection? At least, for me (in US), there are what is called collections where you can group models. For instance some of my models are specific around board games, so I created a Board Game collection (and make it public) that I can reference in my board game listings.

Assuming we are talking about the same thing, I agree, I would like to see collections be able to have a full rich text description (right now I think limited to 150 characters or something). And for something like you are describing, I could imagine even sub collections would be handy feature.

Furthermore on this idea. Around licensing, I have cases where I want to have a standard “locked down” license on a core design, but allow customization remixes for parts of it. In your example this could be situation where core components of your module system are locked down, but you want to provide step files for certain parts so people can create and post those with specific logos and such. I wish there was a more succinct way to accommodate this.