# Introduction

> What Dotquilt is, how its skeleton loaders work, and how a loading region hands over from placeholder to your content.

Dotquilt is a set of skeleton loaders (loading placeholders) drawn from small marks. While your data loads, the marks hold the shape of what is coming. When it arrives, they fade out as your content rises into place.

## What is a skeleton loader?

A skeleton loader, or skeleton screen, is a placeholder in the shape of the content that is on its way: lines where text will be, a block for an image, a circle for an avatar. It shows that something is loading and where it will appear, and it keeps that space, so the page doesn't jump when the content arrives. A spinner only says that something is happening.

Dotquilt's skeleton loaders are made of small marks. When your data arrives, the marks move to your content's real shape, then hand over to it. For when to use a skeleton and when a spinner or a progress bar is better, see [Skeleton loader or spinner?](/docs/guides/skeleton-or-spinner/).

## How it works

Every loader sits inside a **loading region**. The region decides when to switch; the loader only draws.

- **Pending:** the region shows its placeholder and keeps your content hidden from people and assistive technology.
- **Ready:** the region hands over. The marks travel to your content's real shape (each line's length, the image, the avatar), then your content wipes in as they leave, in about a second.
- **Refreshing:** your content stays visible and usable while new data loads.

Your application owns the data, the request and the state. Dotquilt owns only the decoration and the handoff.

## The components

| Component | Holds the place of |
| --- | --- |
| SkeletonBlock, SkeletonLine, SkeletonCircle, SkeletonText | images, text lines, avatars and paragraphs |
| TextLoader | a number or short label |
| ChartLoader | a chart |
| TableLoader | a table |
| TypingDots | a reply that is being written |
| LoadingRegion | the area that switches from placeholder to content |

## Works everywhere

The components are native web components, so they work in plain HTML and in any framework. A thin React adapter adds server rendering and typed props. Reduced motion, forced colours and keyboard focus are handled for you.
