# Lists and tables
Use Mintlify-style Markdown lists, task lists, nested lists, and tables for structured docs content without adding extra component chrome.
Source: /docs/components/lists-tables
Last modified: 2026-06-20
Use native Markdown lists and tables before reaching for cards. They keep implementation docs readable when the content is a sequence, checklist, field comparison, or compact reference.

## Ordered steps

Use ordered lists for lightweight sequences that do not need anchors, descriptions, icons, or rich child content. Use [Steps](/docs/components/steps) when the procedure is the main teaching path.

1. Create a test offer.
2. Add one product and one price.
3. Publish the checkout page.
4. Connect a buy button.
5. Verify the completed purchase event.

````mdx title="ordered-list.mdx"
1. Create a test offer.
2. Add one product and one price.
3. Publish the checkout page.
4. Connect a buy button.
5. Verify the completed purchase event.
````

## Nested lists

Use nested lists when each top-level item needs a short supporting checklist. If a nested branch becomes long, split it into its own section.

- Offer setup
  - Product attached
  - Price selected
  - Checkout template published
- Site integration
  - Button target set
  - Browser SDK loaded
  - Success URL tested
- Automation
  - Purchase event observed
  - Receipt path verified
  - Fulfillment sequence connected

````mdx title="nested-list.mdx"
- Offer setup
  - Product attached
  - Price selected
  - Checkout template published
- Site integration
  - Button target set
  - Browser SDK loaded
  - Success URL tested
````

## Task lists

Use task lists for implementation checklists, migration readiness, and QA notes. Keep them short enough that the reader can complete the checklist without losing the surrounding explanation.

- [x] Create the offer in test mode.
- [x] Add the browser SDK to the page.
- [ ] Connect production Stripe credentials.
- [ ] Send a test purchase through the published button.

````mdx title="task-list.mdx"
- [x] Create the offer in test mode.
- [x] Add the browser SDK to the page.
- [ ] Connect production Stripe credentials.
- [ ] Send a test purchase through the published button.
````

## Tables

Use tables when the reader needs to compare compact structured values. Keep cells short; if a cell needs multiple sentences, use fields, cards, or normal sections instead.

| Surface | Use for | Better component when richer |
| --- | --- | --- |
| Ordered list | Short sequence without anchors | [Steps](/docs/components/steps) |
| Task list | QA or migration checklist | [Callout](/docs/components/callouts) plus sections |
| Table | Compact reference or comparison | [Fields](/docs/components/fields) |
| Nested list | Supporting detail under one item | [Accordion](/docs/components/accordions) |

````mdx title="comparison-table.mdx"
| Surface | Use for | Better component when richer |
| --- | --- | --- |
| Ordered list | Short sequence without anchors | [Steps](/docs/components/steps) |
| Task list | QA or migration checklist | [Callout](/docs/components/callouts) plus sections |
| Table | Compact reference or comparison | [Fields](/docs/components/fields) |
````

## Props


### Markdown surfaces


- `ordered list` (1. 2. 3.):
    Use for short, linear sequences. If the steps need anchors, icons, or nested rich content, use `Steps`.


- `unordered list` (- item):
    Use for options, constraints, and short grouped detail.


- `nested list` (indented list):
    Use only one or two levels deep. More than that usually belongs in sections or accordions.


- `task list` (- [x] item):
    Use for implementation checklists. Checked and unchecked states render as styled disabled checkboxes.


- `table` (Markdown table):
    Use for compact references. Tables are styled with a border, header band, aligned cells, and mobile-safe overflow behavior.


## Related


  - [Steps](/docs/components/steps): Use for primary procedures.
  - [Fields](/docs/components/fields): Use for API and parameter shape.
  - [Accordions](/docs/components/accordions): Use when detail should unfold progressively.