> To build a Wix site agentically, or add Wix features like bookings or a store to a site you already have, follow https://www.wix.com/headless/skill.md
> 
> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Documenting

## Article: Documenting

## Article Link: https://dev.wix.com/docs/wix-design-system/contributing/documenting.md

## Article Content:

<!-- heading -->

# Documenting

<!-- end heading -->

## Documentation Tools

All components are documented and displayed on our main documentation website, which is rendered with [Storybook](https://storybook.js.org).

---

## Documentation Layers

There are two layers of documentation in Storybook:

- **Design System indexing**
- **Components APIs**

The Storybook menu is structured accordingly. For example:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```js
Components // <- Section (API)
├── Form // <- Category
│ ├── Dropdown // <- Component
│ ├── ...
Guidelines // <- Section (API)
├── Panels // <- Category
│ ├── Presets // <- Component
│ ├── ...
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

---

## Design System Indexing

In this layer, the structure follows the UX definitions of the design system. It contains common examples and use cases, along with explanations of how and when to use the components. Additionally, it includes links to the actual component APIs in the next section.

---

## Components APIs

To create a Storybook page for a component's story, you need to create a `*.story.ts` file in the component's folder:

> MyComponent.story.ts

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```js
import { CATEGORY } from '../../../stories/storiesHierarchy';
import MyComponent from '../../src/MyComponent';

export default {
  category: CATEGORY.LISTS,
  storyName: 'MyComponent',
  component: MyComponent,
  componentPath: '../../src/MyComponent',
  story: {
    demo: () => 'TBA',
    content: {},
    examples: {},
  },
};
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

The documentation content of the component page (demo, description, do and don't lists, examples) lives next to the component as one MDX file, `src/<ComponentName>/docs/<ComponentName>.mdx`. Scaffold it with `pnpm --filter @wix/design-system-documentation docs:new <ComponentName>` and fill it in with the `create-component-docs` skill.

As developers, we are responsible for providing proper TypeScript (TS) and JSDoc comments for the component's API, which will be used to generate the `API` and `Testkit` tabs in the Storybook page.

<br>
<br>
<br>
<br>
<br>