# Custom CSS

When you import some WooCommerce templates that include the Woo Notice element into an existing project, they might look different from the demo. This is because we used custom CSS to style them, which was added in **Bricks Settings > Custom CSS**.

\
Copy the code below and place it there:

{% tabs %}
{% tab title="Just Bricks" %}

```css
:where(p) {
    margin: 0;
}

/* Woocommerce buttons */
.woocommerce .button {
  transition: var(--bt-transition-medium);
  min-height: unset;
}

.woocommerce .button:hover {
  box-shadow: 0px 24px 48px 0 rgba(0, 0, 0, 0.1);
}

.woocommerce .button.disabled {
  background-color: var(--bt-neutral-6);
  color: var(--bt-neutral-9);
  border-color: var(--bt-neutral-6);
}

/* Woocommerce notices */
.woocommerce-error, .woocommerce-info, .woocommerce-message {
  position: relative;
}

.woocommerce-error:before {
  content: "\f268";
  font-size: var(--bt-text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--bt-space-xs);
}

.woocommerce-info:before {
  content: "\f1a0";
  font-size: var(--bt-text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--bt-space-xs);
}

.woocommerce-message:before {
  content: "\f14a";
  font-size: var(--bt-text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--bt-space-xs);
}
```

{% endtab %}

{% tab title="Automatic CSS" %}

```css
.woocommerce .button.disabled {
  background-color: var(--neutral-light);
  color: var(--neutral-semi-dark);
  border-color: var(--neutral-light);
}

/* Woocommerce notices */
.woocommerce-error, .woocommerce-info, .woocommerce-message {
  position: relative;
}

.woocommerce-error:before {
  content: "\f268";
  font-size: var(--text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--space-xs);
}

.woocommerce-info:before {
  content: "\f1a0";
  font-size: var(--text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--space-xs);
}

.woocommerce-message:before {
  content: "\f14a";
  font-size: var(--text-l);
  display: inline-block;
  font-family: Ionicons;
  font-style: normal;
  font-variant: normal;
  font-weight: 400;
  line-height: 1;
  text-transform: none;
  position: absolute;
  left: var(--space-xs);
}
```

{% endtab %}
{% endtabs %}


---

# 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.brickstheme.com/common-issues/custom-css.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.