> 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-3-manage-media/review-configuration-of-image-media-display/exercise-3-3-challenge-change-image-size.md).

# Exercise 3.3 (Challenge): Change image size

Remove the *Scale width 1200* effect in the *Job Posting Image* style and replace it with Scale and Crop, applying 1200px wide and 400px height dimensions.

Review how GovCMS updates the *Job posting* images for the existing content.

**What if you want to change the image size?**

The original image is saved as a backup and can be changed. If you decide to change the *Job Posting Image* style later (for example change the image’s dimensions to 200 x 200) GovCMS will automatically resize all *Job posting* images. You can also completely change the image style used in a content type by editing the content type display settings. This also flushes the cached versions and creates new, resized versions (which are copies of the original).


---

# 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-3-manage-media/review-configuration-of-image-media-display/exercise-3-3-challenge-change-image-size.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.