# Content Titles & Headings

## Titles

As part of the UG Drupal platform, every content type you create requires a title in order for the content to be successfully created. It is important that the title is unique among the webiste, descriptive of the content, but not too long. The title is the first thing that is shown on each page and it gives the user a general understanding of what the content following it.

![Basic Page Title](/files/-Ldu94XKZD1HURZljFdk)

Page Titles will also appear in the tab in your browser.

## Headings

When writing text for web pages, consider the fact that some users cannot get an overview of a page visually, and instead rely on structural presentation. Make sure that pages are divided into logical sections, each with a heading that is descriptive of the section.

Headings can be selected in the Drupal text editor. Simply highlight some text, and then use the drop-down menu to select the heading level:

![WYSIWYG Editor with Headings Drop-Down Menu](/files/-Ldu94XMWT61jyoqSrI9)

**/! Note**: Do not use heading elements simply to increase font size, and do not use *empty* heading elements to create space on the page. These improper uses of headings will make the web page less accessible.

**/! Strong Recomendation**: Headings should be used in successive order. This means that any headings related to the Overall Page title (h1) start with h2 and then follow in order. Picture example below:

![Example of Nested Headings](/files/-Ldu94XOkWfq61mEdkq9)


---

# 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://ccsdrupalguide.uoguelph.ca/accessiblecontentguide/content-titles-and-headings.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.