nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

List advantages/disadvantages of options as well as best practices in Help

YvesLeger

I would like to see the help files list the advantages and disadvantages for each option, when multiple options for a function are listed. Currently options are listed, but the user must try to figure out what the advantage of one option is over another. It would also be good if it gave "best practices" examples for functions.

Find more posts tagged with

Documentation & Help

Closed

Status: Closed

Comments

ChrisMathers

A tool is only a part of a workflow though. Perhaps what would be better would be a set of help documents or a user driven web site where best practices could be disscussed for various workflows. "I need to do X, what is the best way to accomplish this?" Or do you mean what are the best values to start from when running an unfamiliar tool?

YvesLeger

Yes, when using an unfamiliar tool, it often means lots of trial and error and lots of time wasted.

MarkZollinger

Typically the best practices for a tool are listed in the usage notes. Usage notes provide guidance on tool settings to the extent this is practical.

If after reviewing usage notes, you aren't sure which options to use, post a question to Esri Community with more detail about your workflow. Most tools can be used in enough different workflows that covering them all in the parameter doc would be more confusing than helpful.