Introduction: [blog 2006-04-15] Tagging an Idea

One of the things that we're very really excited about for Instructables is the concept of a derivative project -- a project that uses another project as a stepping stone for further refinement, improvement, or application to a totally different problem. The community of DIYers that we're all a part of can really do some amazing things working together as a community. Innovation rarely happens in a vacuum.

The obvious next step is to let the community help refine and evolve ideas that aren't yet ready to be finished projects. And, the wonderful thing is that this is already happening: Toy Cookie Dunking Cup is a derivative idea based on Oreo Milk Dunker. This is exactly the process that yields the best products.

I'd like to encourage anyone with an idea to post it and tag it "idea." Show us what you're thinking about and get community feedback. Describe where you're stuck and ask for help. If you have pictures or graphics, that's great. If not, sketch your idea on paper and scan it in; I find it works best to start with a pencil and when you have it right, outline with a black marker or highlighter like this. If it's a derivative idea, tag it with the name of the original idea or project.

We'll figure out a logical way to organize and separate projects and ideas. For the time being, browse through the ideas by searching for the idea tag:


jtobako (author)2009-04-19

Wouldn't this be better as a forum post? Like the other forum posts with the same idea in different forms?

Ludwig Gunner (author)2007-10-26

this is the least popular instructable online. serusly



westfw (author)2006-06-15

So the instructables main page mentions collaboration. Is it actually possible for more than one author to work on a single project (other than via comments.)

radiorental (author)2006-04-18

I understand you're working on a better solution. But specifying a project type at the back end of the documentation process (tagging your project) is not the way users think, in my mind. I would say the thought flow goes a little something like this 1)Hey, thats a cool project, it give me an idea 2)I'll post my idea in the comments > done 2.1)I'll post my idea in a new project 3)Write up idea 4)Publish, wait for comments, get pissed about the few complainers that say 'this isnt well documented' or whatever So I see two problems here. Firstly you approach your documentation stage with the mindset that this is 'a project','a sub project','just an idea' etc etc so the tagging should become predefined labeling. 2ndly How will the complainers know that a new project is just an idea and should not be bitched about? Another general issue is a week or two from now when this blog entry has scrolled off view, will people remember to define their project type with 'idea' and will anyone else looking for inspiration remember to search on 'idea', and given the possibly few people will tag idea, is there even any point searching 'idea' if its only going to produce a very few projects. Yes it may catch on, but I doubt it. Tagging is a nice feature if implemented in such a way that its use is seamless in the overall functionality. It shouldnt be used as a stop-gap solution to meet a requirement such as project type definition. My suggestion would be to do labeling instead of tagging. Generate a small list of project types (+'other') that the user selects at the start of the documentation process, call them predefined tags if you will. These labels are both searchable as tags but also visable in the project header (not just the tag cloud) pauric

pt (author)2006-04-15

great idea - i suspect a lot of folks will post up ideas to consider for a group of folks who can build upon them. i'll post up on make.