...
The documentation includes a
- 1 Glossary, which defines the terms used in the Search Editor and gives examples.
- 2 How-to guides
- 1 Guides, which guides the reader through very basic functionality.
- 2 Use cases, which puts the use of the Search Editor into a practical context.
- 3 Understanding the UI elements, which describe the UI's partitioning and some design decisions
Reading guide
The suggested way of approaching these documentation pages is to first get acquainted with the 1 the Glossary; getting acquainted with the UI in 3 Understanding the UI elements; then trying to perform the examples in the 1 Guides. All the while revisiting the 1 Glossary when/if there is any confusion/doubts; and finally reading the 2 the Use cases to put the gathered knowledge into a wider perspective.
...
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in these pages are to be interpreted as described in RFC 2119.