> For the complete documentation index, see [llms.txt](https://wiki.owain.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.owain.codes/coding/tips-how-to/wrapped-up-a-site.md).

# Wrapped up a site

First thing is you need to check if there is pending work on Dev that isn't on the live environment.

If there is, (check by making a temp PR on DEV to UAT for example) this work really should get pushed up to LIVE through the usual steps e.g DEV->UAT, UAT-> LIVE

Assuming there isn't any changes, you'll want to pull down Develop, and then clean it up (remove connection strings, api keys etc).

Then zip it up without the .git hidden folder, (there is more you can clean up such as doing a VS clean on it to clear obj and bin folders, removing the packages folder etc other wise it will be 100's of MB big.

You'll also want to zip up the live Umbraco forms, and Media from blob storage, and then the live database.

<br>


---

# 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://wiki.owain.codes/coding/tips-how-to/wrapped-up-a-site.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.