> 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/functional-analysis.md).

# Overview

This unit focuses on the concepts of GovCMS site-building. At this stage, you’re familiar with the essentials of GovCMS. You may have been working already on a GovCMS site but never built one before. Or you may have learned the basics, but don't know how it fits together. Now you want to know how to put the building blocks together to make new, unique websites or applications.

In this unit you’ll learn:

* How to plan a new GovCMS website
* How to make changes to the site theme
* How to create new user roles
* How to configure role permissions
* About the page layout in GovCMS
* How to create and manage site navigation and place blocks

### What is site building?

Site building in GovCMS is about configuring the GovCMS solution to build a functional website. It needs a GovCMS developer who’s familiar with the contributed modules and site building in general.


---

# 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/functional-analysis.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.