So I just copy & paste all of that into the command block? Thank you, but I don't know what you're doing with the commands, since I'd have written it myself if I did. Why do I need a scoreboard for the block to take away a wool and give the strings? I'd rather the user of the block just click a button or put the wool block(s) in an attached chest.
I've see requests for a spinning wheel that go back years; I don't get why Mojang seems to ignore suggestions for such a simple and logical feature. It makes more sense to spin wool into yarn than it does to transmute spiderwebs into wool.
No, each line is a separate command block. Create a clock and connect the commands to it. Be sure that the order of execution is retained with the order I wrote the commands.The reason for scoreboards is because you can't target an entity by it's data tag in the commands I am using any other way.The method I provided works anywhere in the world, instead of having a button connected to a command block at only one place where you would have to go. It is also simpler to test for item entities than items in a chest, in my opinion, so I made it that way. It's also more fun to drop it down and watch it turn into string.
All those @a's they hurt my poor eyes. I would suggest adding scoreboards so you can track which player used the ability, and replace the @a with an @p with score selector tags. Although I'm not sure whether you could preserve it as a one-block-creation though.
PS: did you use a compiler/tool to create this, or did you write it up manually?