# Themes Blocks Styling FAQ

Source: https://docs.arcxp.com/en/products/themes/themes-2-0-faq.html

## Introduction

The Themes design system lets you customize the styling of Themes components and blocks. It is built on global tokens, breakpoints, and alias tokens, which give you a flexible and scalable way to create a website that represents your brand. You can style the out-of-the-box blocks, and a set of atomic components is available for you to style and compose within your custom blocks.

For example, if your organization wants a particular button style, your development team can update the style in the appropriate [styles folder](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#themes-20-design-system-files), and that change applies wherever the button component is used.

Our [developer documentation](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#basics) has all the details on how to use the block styling configurations. Because you can style more Themes blocks without forking them, your organization spends less time on custom code maintenance.

## Blocks Styling

### Where can I learn more about the styling capabilities in Themes?

You can find the design system details in our [Themes Design System](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#basics) documentation.

### What component and block tokens are supported?

You can view a full list of supported tokens here:

- [Component tokens](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#styling)
- [Blocks tokens](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#block-tokens)

### What are some common use cases for the design system?

You have a lot of flexibility to update style properties with the [design tokens](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#tokens). Beyond the [examples](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#styling) provided in our [developer documentation](https://dev.arcxp.com/themes/developer-docs/introduction-to-themes-20-design-system-developer-guide/#basics), you can also add the CSS properties needed to support your design use cases. Some common use cases we have observed to align with organizations’ branding and style guides include:

- Setting site font and typography styles at the component or block level
- Updating the border radius of a component, like a button or pill
- Changing the background color of a block and consequently in line text, for better contrast
- Applying a specific color, size, and/or font weight to an overline, to highlight specific topics or sections
- Updating hover styles on components or blocks
- Adding or reducing spacing on components or blocks
- Increasing or decreasing line height on the paragraph text component
- Changing the alignment of a component on a block, like left aligning the header, instead of center
- Setting the case on a text component, like uppercase/capitalized overlines
- Defining a variant in styling for a component, based on a CSS selector on the page
- and many more

Block styling is also a good fit for a site redesign or rebranding, because styles can be applied at the component or block level, rather than updating the CSS for every individual component.

### Do I need to fork a block to change its styling?

No. You can add styling customizations to any design token, component, or block without ejecting (forking) the block, so the block continues to receive future updates.

### Can our custom blocks use the design system? Do we still need custom blocks?

You can use Arc XP blocks alongside your custom blocks. Styling applies to the out-of-the-box components and blocks, including Arc XP components used in your custom blocks. Full custom blocks that are not built from Arc XP components are not watched by the StyleBuilder script, but you can still apply your own styling.

### Where can I see the design files for Themes blocks?

You can find the Themes components, blocks, and styling system in [Themes 2.0 - Blocks Styling Figma Library](https://docs.arcxp.com/en/products/themes/themes-2-0---blocks-styling-figma-library.html). Our design files are hosted in Figma. For organizations that also use Figma, you have the option to copy or branch the files as well.

### Do you support an integration with any design software?

Themes does not currently support an out-of-the-box integration with any design software; however, we are capturing interest for this functionality and monitoring opportunities for keeping your design tokens source of truth in tools like Figma, and having an easy path to automate importing your tokens into the design system. You also can continue to import your own stylesheet into your output types.

### Why does block styling use JSON? Will you support .css, .scss, .js files for styling blocks?

JSON provides a structured syntax that enables design system frameworks to output and compile styles to other formats easily and also lays the foundation for low-code design system changes in a UI.

### Can I create block style variants?

Variants are supported using custom Themes blocks styling. Create a new unique token for a style, based on CSS selectors that differentiate your variant by its relationship to other elements on the page. For more details, see [variants and custom tokens](https://dev.arcxp.com/themes/developer-docs/themes-20-creating-a-custom-block-with-styling/#variants-and-custom-tokens). Data-driven variants are not supported unless you create a custom chain that wraps your blocks with a unique class name based on this data, or you fork the block.

## Custom blocks and deployment

### How do I set the Themes version and deploy my bundle?

Set the Themes version in the `themesReleaseVersion` property of your `blocks.json` file, and make sure the compatible PageBuilder Engine version is also set. See [How to run PageBuilder Engine locally](https://dev.arcxp.com/pagebuilder-engine/how-to-guides/basics/how-to-run-pagebuilder-engine-locally/) for compatible versions.

The `blocks` array in `blocks.json` needs to match the blocks you use, and Fusion needs to be run locally so that the StyleBuilder script can create a proper `_index.scss`. After that, run `npx fusion zip` and deploy the bundle to your environment. See [How to deploy a bundle](https://dev.arcxp.com/pagebuilder-engine/how-to-guides/optimization-and-deployment/how-to-deploy-a-bundle/) for the full steps.

### Do my custom blocks need to support Image Resizer V2?

Themes out-of-the-box blocks support [Image Resizer V2](https://dev.arcxp.com/photo-center/developer-docs/migrate-from-resizer-v1-to-v2/). If you also maintain custom blocks with images, you must make the necessary updates for Image Resizer V2 on those blocks only.

Image Resizer V2 is a more powerful and reliable resizing service. It lets you add SEO-friendly names for images, which can help your site’s SEO performance. The authentication token is included in the Arc XP Native Specification (ANS) for the image and is good for all resize variations, so you do not have to store the secret key.

### Where can I read more developer focused FAQ considerations for planning our site build?

You can read answers to commonly asked questions about developing on Themes in our [Themes developer FAQ](https://dev.arcxp.com/themes/themes-faq/).

## Choosing Themes

### What are the benefits of Themes blocks?

- Improved speed to market with pre-built, data-driven blocks, pages, and templates that makes site setup and maintenance easier
- Low maintenance efforts with ongoing support and upgrades for out-of-the-box blocks integrated with the Arc XP product suite
- Optimized components that are built with best practices in performance, SEO, and accessibility in mind
- Out-of-the-box components and blocks mean you can focus your resources on brand differentiation and compelling user experiences

### How do I know if Themes is not the best solution for our organization?

If your site has specific pseudo-class or selectors requirements or other extremely unique CSS requirements, does not utilize our PageBuilder Editor solution, or prefers to fully maintain your own custom front-end solution, Themes may not be the best solution for your organization. You may still use the rest of the Arc XP product suite that best fits your needs and maintain your own front-end code.
