Walkthrough: not every playground has a name

[o5k6]

The iD user interface may create the impression that all fields (i.e. tags) need to be filled. This is a general issue and cannot be completely avoided in an editor offering tag templates.

However, the tutorial's playground episode offers an opportunity to convey to the user that not every object needs to be given a name (tag). Currently it prompts to add a name, which I find somewhat unfortunate as it may lead to the impression that a name tag is always necessary.

This could be changed to something in the spirit of "Some objects have names, others don't. Roads and restaurants usually have one, a playground may not. In that case, just leave the name field empty (please don't make one up: 'playground' is not a name, but a feature class, and you already entered that). Let's assume this one is called 'Itchy & Scratchy Land' (or whatever you like). Enter that name and close the property editor."

Edit: Or better yet "... We'll assume this one is unnamed - so leave the name field empty and close the property editor." Entering names was already learned in an earlier episode.

The above is just a rough draft and a bit longish. Maybe the information could be distributed over two chapters of the tutorial.

[tmcw]

This seems like it should be in long-form documentation, not in the walkthrough. We cannot worry about or fix all potential misunderstandings because there are infinitely many.

[o5k6]

Sure. But you can - and IMHO should - care about the most frequent ones. And filling in tag templates "because they are there" is one of them, witness the results of beginners using Potlatch 2.

[jfirebaugh]

I agree with @tmcw -- we are never going to be able to foolproof the walkthrough. If anything, we need to make the text more concise -- see the screenshots in #1418.