# PageSugar documentation

> 15 pages covering integration, customization, distribution and agent access.
> Every link below is the Markdown twin of the page.

Page: https://pagesugar.com/docs

## Start here

The requirements each component declares, the Tailwind setup they need, and how to add your first one.

- [Getting started](https://pagesugar.com/docs/getting-started.md): What these components are, what your project needs, and how to add your first component.
- [Understand component requirements](https://pagesugar.com/docs/component-contract.md): The declarations every published component makes about its runtime, integration level, dependencies, services, files and release state.
- [Tailwind prerequisites](https://pagesugar.com/docs/tailwind-prerequisites.md): How to configure Tailwind CSS 4 so the utility classes in copied components are generated.

## Using components

Getting a component’s source, adapting it, and what it needs from your project once it is in.

- [Get component source](https://pagesugar.com/docs/source-acquisition.md): The ways to retrieve a component's source for one exact version and variant, and how to verify what you received.
- [Customization](https://pagesugar.com/docs/customization.md): How palettes, variants and CSS variables work, and when to edit component source directly.
- [Dependencies and assets](https://pagesugar.com/docs/dependencies-and-assets.md): How components declare third-party packages, external services and bundled assets, and what you need to install or provide.
- [SvelteKit recipes](https://pagesugar.com/docs/sveltekit-recipes.md): How integration levels separate presentational components from SvelteKit integration recipes, and what a recipe asks of your project.
- [Accessibility in your project](https://pagesugar.com/docs/accessibility.md): What each component documents about accessibility, and what remains your responsibility once it is in your site.

## Agents and API

How coding agents find and fetch components: the MCP server, the public API, the bundle format and Markdown twins.

- [MCP reference](https://pagesugar.com/docs/mcp.md): The MCP server's endpoint, tools, limits, version rules, errors and privacy notes, with setup for each coding agent on the MCP page.
- [Agent workflow](https://pagesugar.com/docs/agents.md): A practical sequence for coding agents that select, retrieve and integrate catalogue components into a Svelte project.
- [Public API](https://pagesugar.com/docs/api.md): The public routes, filter vocabulary, limits and error codes shared by the website, the HTTP API and the MCP server.
- [Distribution format](https://pagesugar.com/docs/distribution.md): The distribution receipt, how file hashes and the artifact digest are computed, and the layout of a component bundle.
- [Markdown for agents](https://pagesugar.com/docs/markdown-for-agents.md): Every page has a Markdown twin: append .md to any path, or start from llms.txt, and read the catalogue without parsing HTML.

## Policies and support

How components are licensed, and how to report a problem.

- [License](https://pagesugar.com/docs/license.md): How component source and asset licenses are declared, and the current status of the default license and website content terms.
- [Help and issue reports](https://pagesugar.com/docs/reporting-issues.md): What to include when you report a problem with a component, the documentation or the catalogue services, and where to send it.