# Introduction

As a global society, we should be making an effort to [be on track with the necessary changes](https://climateactiontracker.org/publications/state-of-climate-action-2022/). These changes are needed to keep global temperature increases below 1.5°C compared to pre-industrialised times. According to [the studies](https://climateactiontracker.org/publications/state-of-climate-action-2022/), the temperature will likely be breached in 2023. This will have additional impacts on the warming weather pattern, for example, more extreme weather events driven by El Niño.

The severe disruption to society will also extend to businesses with physical and digital infrastructure suffering damage, affecting employee’s ability to work.

The [2023 Edelman Trust Barometer found that business is the most trusted institution](https://www.edelman.com/trust/2023/trust-barometer), above NGOs, governments, and media. Therefore, businesses need to live up to that trust on issues like climate and ecological emergencies.

Digital industry organizations have a part to play in meeting the challenge of reducing emissions:

* [The emissions caused by the digital industry are equivalent to the airline industry](https://www.cell.com/patterns/pdfExtended/S2666-3899\(21\)00188-4).
* Since the Paris Agreement, the [average web page size has increased by 64% on desktop and 132% on mobile](https://httparchive.org/reports/page-weight?start=2015_12_01\&end=latest\&view=list).
* This is worsening because more people are consuming heavier-weight software; [internet users have increased by 60%, while internet traffic has increased by 440%](https://www.iea.org/energy-system/buildings/data-centres-and-data-transmission-networks).

Given the above, this documentation describes some of the best practices that can be applied when developing digital experiences. The recommendations are given by a group of Umbraco Community members in [the Sustainability Team](https://umbraco.com/blog/meet-the-new-community-sustainability-team/).

## Read our best practice guide for developers

We have decided to target our best practices to specific roles. As a result, we have grouped the documentation into four categories: Infrastructure, Backend, Frontend, and Editor. You can dive into one of the categories that interests you the most.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/pages/cpVOA0YnA96rerRJpkMv"><strong>Infrastructure</strong></a></td><td>Read about some basic considerations for a sustainable infrastructure.</td><td><a href="/files/TKI6iRwqlCKeAwAJzjsZ">/files/TKI6iRwqlCKeAwAJzjsZ</a></td><td><a href="/pages/US1mHMeoXQgtvI3jXh9X">/pages/US1mHMeoXQgtvI3jXh9X</a></td></tr><tr><td><a href="/pages/bFIAXpROKipxhFQeR9wt"><strong>Backend</strong></a></td><td>Learn about the common pitfalls and much more.</td><td><a href="/files/hJ5TyLCkT8JiNz8W1jp2">/files/hJ5TyLCkT8JiNz8W1jp2</a></td><td><a href="/pages/a51AfildVpumPtwbk09R">/pages/a51AfildVpumPtwbk09R</a></td></tr><tr><td><a href="/pages/PVV3KiRQw6Gapj2nonDr"><strong>Frontend</strong></a></td><td>Learn about how you can optimise assets, implement a mobile-first strategy and other suggestions.</td><td><a href="/files/7hyh9Xtdw6yL3XFEbpvD">/files/7hyh9Xtdw6yL3XFEbpvD</a></td><td><a href="/pages/DPA4wCDfCotUlUN9Sa0d">/pages/DPA4wCDfCotUlUN9Sa0d</a></td></tr></tbody></table>

## Are you an Editor? - You can also do a lot for the environment

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/pages/9E9TrawM0zQqVrE2hotE"><strong>Editors</strong></a></td><td>Take a look at our sustainability guide for editors</td><td><a href="/files/KwZGDH6qD12ywQySHLJB">/files/KwZGDH6qD12ywQySHLJB</a></td><td><a href="/pages/rBgyjYQfSNbndqFTZQtW">/pages/rBgyjYQfSNbndqFTZQtW</a></td></tr></tbody></table>

## Telemetry Data

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/pages/GvFul3aLsYoaLbBGHKRz"><strong>Telemetry Data</strong></a></td><td>Take a look at the insights received from the collected detailed telemetry.</td><td><a href="/files/YUpkoWhmdY78STMdH86A">/files/YUpkoWhmdY78STMdH86A</a></td><td><a href="/pages/GvFul3aLsYoaLbBGHKRz">/pages/GvFul3aLsYoaLbBGHKRz</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.umbraco.com/sustainability-best-practices/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
