> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-site-builder/unit-1-functional-analysis/define-user-stories.md).

# Define user stories

User stories are another way to find out more about your audience and ensure your website is designed to meet users’ needs. For site builders, you can create user stories for the end site visitors and for the people who will be working on the CMS (backend) to create the site (e.g. Content Editors and Content Approvers).

* As a job seeker, I want to be able to find a job I’m interested in so that I can apply online.
* As a Content Editor, I want to create and find content in one place so that I can do my job more efficiently.
* As a Content Approver, I want to see any content that’s waiting for my review/approval as soon as I login to the site so that I can review content quickly and easily.

###


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-1-functional-analysis/define-user-stories.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.