> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/bigcommerce/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/bigcommerce/1.0-4/look-and-feel.md).
# Look and feel
Using the [Cornerstone theme](https://support.bigcommerce.com/s/article/Cornerstone-Theme-Manual?language=en_US), you can style the look and feel of the elements within the [Drop-in](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/drop-in) component using [Page Builder](https://support.bigcommerce.com/s/article/Page-Builder?language=en_US).
You can change the following body text and link attributes:
* Body text font family
* Link font family
* Link color
* Link hover color
Form Checklist
* Form Background
* Form header text color
* Form border color
## Styling the Pay button
To style the Pay button within the Digital River drop-in component:
1. Click **Store Setup** in the app menu on the left and then click **Themes**.
2. Under **Current Theme**, click **Advanced**, and select **Make a Copy** from the drop-down list.\
3. Enter a name for the theme in the **Theme Name** field and click **Save a Copy**. \
4. Under **Themes**, click more options on your created theme and select **Edit Theme Files**.\
5. Click the **Do not show me again** checkbox and click **Edit theme files**. 
6. From your browser's **Stencil File Editor** tab, click **assets**, click **scss**, and then click **optimized-checkout.scss**.\
7. Copy the following text and paste it at the bottom of the optimized-checkout.scss file.\
\
`.DR-pay-button{`\
`background-color: BLACK !important;`\
`}`\
`.DR-button-text{`\
`color: RED !important;`\
`}`\
**Important**: You must add the `!important` rule to the CSS line.
8. Click **Save File**. The results will look like this:
---
# 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://docs.digitalriver.com/bigcommerce/1.0-4/look-and-feel.md?ask=&goal=
```
`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.