> 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/understanding-requirements.md).

# Understanding requirements

When you’re building a site, it’s important to understand the client’s requirements. These cover creative requirements, technical requirements and content requirements.

1. **Creative requirements** Think about the site’s visual look and feel. The branding that needs to be applied, the colour scheme, and the agency’s creative requirements. What sort of websites do they like (a mood board with sample designs might help here). Ideally, you should also bring user research into the site building to understand the site’s audience and help you create personas and user pathways.
2. **Technical requirements** Think about the required functionality and how this maps to GovCMS. Which modules will you be using? Do you need to integrate with third-party APIs? At this stage, you’ll also need to decide whether GovCMS SaaS or PaaS is a better fit.
3. **Content Requirements** GovCMS comes with six content types out-of-the-box. While these content types are designed for government, you may need additional content types. Will your site use blocks? Think about the site’s taxonomy. You should also consider the content editors/users to work out what roles you’ll need and whether you’ll need content moderation workflow.

## Establishing requirements

The steps below provide a high-level overview of establishing requirements:

* Define the minimum viable product (MVP).
* Build a roadmap: Decide what are the features beyond the MVP? Identify features that are “low hanging fruit” - easy to build with high business value.
* Set measurable goals so you can measure the project’s success.
* Review the current systems.
* Consider mobile devices and establish Web Content Accessibility Guidelines (WCAG) compliance requirements.
* Research the editor types required for the site, and any approval workflow that’s required.
* Who are the site visitors (the audience)? Consider setting up personas for your site visitors.
* Define the minimum set of permissions and roles.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-1-functional-analysis/understanding-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.