> For the complete documentation index, see [llms.txt](https://promet-source.gitbook.io/provus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://promet-source.gitbook.io/provus/getting-started/theming/custom-theming.md).

# Custom Theming

How to start adjusting the default variables setup with the Provus theme.

Provus ships fully themed. All you need to add is content to have a complete website. However, Provus is also fully customizable. The themes colors, fonts, borders, shading, and much more can be edited to match your branding and style guides. This section provides some basic directions for custom theming of your Provus site. 

## Getting started

**NOTE:** The following instructions assume the use of Sass for theming. Sass files must be compiled into CSS files. While edits made to the CSS files directly if you are unfamiliar with or prefer not to use Sass, the Sass files will be overwritten if you later switch to compiling Sass files. Sass allows for global changes to variables so that multiple instances of color or font usage do not need to be changed individually. 

Start by navigating to `scss/global/_variables.scss` in your subtheme directory. 

At the very top of this file is an import for customizing the web font. Change the URL to web font you plan to use, or write CSS to bring in your own locally hosted fonts.

```
// Fonts
@import url('https://fonts.googleapis.com/css?family=Inter:100,200,300,400,500,600,700,800,900&display=swap');
```

### Fonts

After you have brought in the fonts you wish to use, adjust the variables for the body and heading font families.

```
// Body Font Family
$font-body: 'Inter', sans-serif;

// Heading Font Family
$font-heading: 'Inter', sans-serif;
```

### Colors

Next, adjust your main color variables. This would include your primary, secondary, and background colors ( along with the light versions of each ). 

```
// Primary Colors.
$primary: #2563EB;
$primary-hover: #114CAE;
$primary-contrast: #ffffff;
$primary-accent: #1C2B54;

// Secondary Colors.
$secondary: #00869E;
$secondary-hover: #045F70;
$secondary-contrast: #404758;
$secondary-accent: #5BCDE2;

// Background Colors.
$background-white: #ffffff;
$background-light: #FBFBFC;
$background-grey: #D6D6D6;
$background-lightblue: #EFF6FF;
$background-lightteal: #E7F6F9;
$background-gradient: linear-gradient(45deg, #2BAEC6, #094FC2);
```

After that, adjust the hex variables for text colors, body colors, accent colors, and any of the other color variables included in the Provus subtheme as needed.

```
// Text.
$text-primary: #2C2E30;
$text-secondary: #646F79;
$text-contrast: #FFFFFF;
$text-hint: #747474;
$body-color: #2C2E30;

// Accent.
$accent-light: $secondary-accent;
$accent-dark: $secondary-contrast;

// System/Alert Colors.
$success-light: #D1FAE5;
$success-primary: #258750;
$success-medium: #007038;
$success-contrast: #024825;
$error-light: #FEE2E2;
$error-primary: #D83A52;
$error-medium: #B63546;
$heading-color: #1d2b36;

// Base Font Size
$font-size-base: 1rem;

// Border Radius for Cards
$card-border-radius: .25rem;

// Card Padding
$card-spacing: 1.25rem;

// Card Border Colors
$card-border-color: #ddd;

// Site Background Color
$body-bg: #fff;

// Main Text Color
$body-color: #2C2E30;

// Text Primary Color
$text-primary: #2C2E30;

// Text Secondary Color
$text-secondary: #646F79;

// Text Contrast Color
$text-contrast: #FFFFFF;

// HR Color
$hr-color: #2C2E30;

// Border Color
$border-color: #C2D1D9;

```


---

# 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://promet-source.gitbook.io/provus/getting-started/theming/custom-theming.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.