> ## Documentation Index > Fetch the complete documentation index at: https://docs.meibel.ai/llms.txt > Use this file to discover all available pages before exploring further. # Element types > The content roles an element can take, what each represents, and how it renders Layout analysis labels every region of a page with a content role. The role is what lets you treat content by its meaning: build an outline from headings, keep tables for data, route charts and formulas to their own handling, and drop page furniture from a body index. This page catalogs the roles. In the structured result, each element names its role with a `label` from a fixed set. The roles below group those labels by the kind of content they mark. ## Text roles | Label | Represents | Rendered in Markdown as | | --------------- | --------------------------------------------------------- | ------------------------ | | `Title` | The document's main title | `#` heading | | `SectionHeader` | A section or subsection heading, with a level from 1 to 6 | `#` to `######` by level | | `Text` | A block of body text | Plain paragraph | | `Caption` | A caption for a figure, table, or chart | Italic text | | `Footnote` | A footnote | Footnote definition | | `Code` | A block of code | Fenced code block | | `Formula` | A mathematical expression, recognized as notation | `$$` display math | | `DocumentIndex` | A table of contents or index | Plain text | A `Title` or `SectionHeader` carries a `heading_level` derived from the document's typography, so the section hierarchy is preserved. See [the parsed document](/document-parsing/concepts/the-parsed-document) for how levels are assigned. ## Figure roles These roles cover regions that are visual rather than textual. Charts, formulas, seals, and pictures are recognized by vision-language models, described in [charts, formulas, and vision models](/document-parsing/concepts/charts-and-vision). | Label | Represents | Notes | | --------- | ------------------ | ------------------------------------------------------------------ | | `Chart` | A plotted chart | Carries digitized `chart_data` and recognized labels on `ocr_text` | | `Seal` | A seal or stamp | Carries recognized text | | `Picture` | An image or figure | Recognized by a vision model | ## Tables | Label | Represents | Notes | | ------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `Table` | A tabular region | Carries a grid of cells with row and column positions and spans; see [extracting tables](/document-parsing/guides/extracting-tables) | ## Page furniture Page headers and footers are the repeating content at the margins of a page rather than part of the document body. Filtering them out by label keeps them out of a body-text index. | Label | Represents | | ------------ | -------------------------------------------------------------- | | `PageHeader` | Repeating content at the top margin | | `PageFooter` | Repeating content at the bottom margin, including page numbers | ## Legacy labels A few labels remain for backward compatibility but are not produced by the current layout model: `ListItem`, `Form`, `KeyValueRegion`, `CheckboxSelected`, and `CheckboxUnselected`. A list item in a document parsed by the current model comes through as `Text`. ## Handling unknown roles Treat the set of labels as open. The vocabulary can grow, so branch on the labels your application handles and fall through gracefully on the rest rather than assuming a fixed, exhaustive list. ## Related How typed elements form the document model. The fields each element carries.