> For the complete documentation index, see [llms.txt](https://docs.beefree.io/beefree-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/beefree-sdk/~/changes/3EjxmC5rAYEIQ0JKR16k/other-customizations/appearance.md). # Appearance Beefree SDK enables you to customize the appearance of a variety of elements. Reference the following sections to learn more about how you can customize appearance:


Content Defaults: Define how content looks when dragged into an email or page.			Content Defaults
Custom Sidebar Position: Choose whether to display the builder sidebar on the left or on the right side of the screen.			Custom Sidebar Position
Content Title Sorting: Change the order of the content tiles in the editor’s sidebar.			Content Tile Sorting
Content Title Grouping: Group content tiles in the editor’s sidebar.			Content Tile Grouping
Loading Spinner Theme: Choose between a dark and light theme for the loading animation			Loading Spinner Theme
Custom Tab Layout: Re-organize the way tabs are ordered.			Custom Tab Layout
Themes: Change the builder’s appearance when rendered within your application			Themes
Custom CSS: Define a custom look and feel through a CSS stylesheet			Custom CSS

--- # 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://docs.beefree.io/beefree-sdk/~/changes/3EjxmC5rAYEIQ0JKR16k/other-customizations/appearance.md?ask=&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.