# Content patterns

### Indicating required and optional fields

Clearly communicating whether form fields are required or optional helps users complete forms with confidence and reduces input errors. Use the following standards to ensure consistency and clarity across all form interfaces:

* When all fields are required: State `All fields as required.` as helper text. Do not use asterisks to indicate required fields.
* When all fields are optional: State `All fields are optional.` as helper text.
* When there is a mix of required and optional fields: State ` A red asterisk`` `` `<mark style="color:red;">`(*)`</mark>` `` ``indicates a required field. ` Then, apply the red asterisk after the label for any required fields.
* Don't indicate the quantity of required fields. e.g., "2 fields are required."

### Capitalization rules for different elements

#### Pages

* Titles and H1s
* H2s: Title case
* H3s and lower: Sentence case

#### Forms

* Titles and H1s
* H2s and lower: Sentence case
* Navigation menu labels: Sentence case


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.simpler.grants.gov/design-and-research/content-guidelines/content-patterns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.