> For the complete documentation index, see [llms.txt](https://docs.venuecms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.venuecms.com/developers/sdk-next/reference/type-aliases/contentstyles.md).

# ContentStyles

[**@venuecms/sdk-next**](https://docs.venuecms.com/developers/sdk-next/reference/index.md)

***

## Type Alias: ContentStyles

```ts
type ContentStyles = Pick<ElementClasses, 
  | "p"
  | "h1"
  | "h2"
  | "h3"
  | "ul"
  | "ol"
  | "li"
  | "code"
  | "a"
  | "img"
  | "image"
| "linkCard">;
```

Defined in: [packages/sdk-next/src/components/VenueContent/index.tsx:351](https://github.com/venuecms/sdk/blob/cfed6bdc583cc0d277b4fe1af72727ff7219484d/packages/sdk-next/src/components/VenueContent/index.tsx#L351)

The class names a caller may set, one per thing the renderer puts a class on.

Listed explicitly rather than derived from the handler map, which named the wrong things and named them too widely. Two problems it had: the handlers are keyed by node type (`paragraph`, `bulletList`) while the classes they read are keyed by the tag the node renders as (`p`, `ul`), so half the declared keys were never read and half the read ones were undeclared; and `getDefaultHandlers` is annotated `NodeHandlers`, whose string index signature collapsed `keyof` to `string` — making this `Record<string, string>`, which accepted any key at all and, once listing components shared the map, forced every value to be a string.

Keyed on ElementClasses so a class the renderer stops reading cannot linger here. `text`, `heading`, `hardBreak` and `iframe` are deliberately left out: the renderer declares them but applies none of them (`heading` defers to h1/h2/h3, `hardBreak` renders a bare\
, the youtube embed ignores `iframe`, and `text` is read into an expression whose result is discarded), so naming them here would promise styling that never lands.


---

# 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.venuecms.com/developers/sdk-next/reference/type-aliases/contentstyles.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.
