> For the complete documentation index, see [llms.txt](https://sdk.chorus.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.chorus.one/our-products/chorus-one-widget/customize-and-deploy.md).

# Customize and Deploy

**Tailor the staking experience to your brand.** The Chorus One Widget Builder lets you seamlessly apply your own design elements, colors, and style, so the earn section feels fully native to your platform and delivers a consistent, branded user journey.

### Access the Widget Builder

The Chorus One Widget Builder can be easily accessed at [widget.chorus.one](https://widget.chorus.one/)

### Customize

The left sidebar provides all customization options. Changes are applied in real time so you can preview how the Chorus One Widget will appear within your application.

**Accent Color**

* Customize the accent to match with your brand’s primary color.
* Color tones can be adjusted directly through a palette, enter a HEX value or RGB values

**Brand Logo**

* Displaying your own logo by updating the URL.
* Default: Leave the URL field empty to display no logo.

**Networks:**

* Select the desired networks you want to offer in your platform
* Default: All available networks will be shown to users

**Referrer Code (optional):**

* Enter an identifier to track reference across all networks

### Deploy with 1-Line Code

{% hint style="warning" %}
Prerequisite: Please contact Chorus One team at <StakingBOS@bitwiseinvestments.com> to whitelist your domain.
{% endhint %}

After customizing the widget to match your branding, you can simply copy the intergration code into your platform by embedding the widget URL inside an `<iframe>`. The widget is framework-agnostic and works seamlessly across any tech stack, including no-code platforms.

```
<iframe 
  src="https://widget-staging.chorus.one/eth/stake?primaryColor=%232a2d2d&bgColor=%23FFFFFF&textColor=%23000000"
  width="600" 
  height="900" 
  frameborder="0"
></iframe>
```


---

# 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://sdk.chorus.one/our-products/chorus-one-widget/customize-and-deploy.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.