> 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/about-our-client.md). # About our client The current government jobs website is a static website, managed manually by a number of employees at a government agency. Job categories and individual pages require a manual update. The same content has to be updated in multiple places, to stay in sync across various sections of the site. This has led to incomplete and mismatching content. A Google search widget allows job seekers to find jobs, but the search is lacking configuration and flexible styling. Your client wants to enhance the search functionality with facets, to facilitate easy filtering of search results. As the number of jobs listed on the site has grown over time, managing the site has become difficult. The government agency that maintains the site has requested a new website and CMS and they have approached you as a site builder. --- # 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/about-our-client.md?ask=&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.