Urge authors to make better project summaries
I see these neat projects all the time in the newsletter, but when I click on them I'm often bewildered.
When I see an instructible want to know one thing: What does it do?
Maybe it's my own shortcoming, but I wish that people would say in the first sentence what the point is of their project.
This project is super cool and the steps seem clear. However, what does it do? It says in the title "facilitates DC restoration". I don't know what that means. It also says in the link "PC Sound Card Oscilloscope". Does an oscilloscope somehow facilitate DC restoration?
I probably don't know enough about electronics for this to be useful to me, but it would be really nice to understand what he's making and what you'd use it to do.
I'm sorry to pick on the guy who's apologizing for his English, but I wish that it said what the robot does.
This has a great description, and this is what I'm talking about. I can't imagine what you would do with it, but it clearly makes algae. Cool, if I want to make algae, I'll know where to look!
I think it would be easy to encourage people to include the purpose of their project in the summary, and perhaps it could be incorporated easily into the submission process (although a simple suggestion might do the trick).
Of course there are times when it wouldn't be appropriate, like when posting art related instructables. Also the general purpose stuff, like how to make balls of ice (although it would be interesting to know why someone would make an ice sphere maker)! Also guides, like "Plant Terrarium Basics" don't need the purpose spelled out. But, I think that lots of other things would really benefit from it!