This seemingly makes it impossible to enter a URL with encoded chars, such as:
thenounproject.com/.../%20power&i=343723I wanted to use the above URL for attribution, but I had to modify it so it didn't have the embedded %20 or space in it.
It would be nice if the store content engine would just encode (*) all our plain text normally, so it's displayed exactly the way it was typed in. Considering that markup and angle brackets are not allowed, I don't see a downside to this.
(*) Or not decode, whatever the case may be.