> 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: Fixing a Bug

## Article: Fixing a Bug

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

## Article Content:

<!-- heading -->

# Fixing a Bug

<!-- end heading -->

<br />

> Bug fixes are high-impact contributions that ensure we deliver a reliable experience to our consumers.

## How to contribute

1. [Submit a bug report](https://wix.slack.com/archives/C39FTGUBZ).
   - Include a clear description of the issue, steps to reproduce, and any relevant screenshots or logs.
   - If you can, provide a link to the code that is causing the issue.
2. In the report, mention that you would like to contribute a fix.
3. Assess the time and difficulty of finding and fixing the bug.
4. If you discover that fixing the bug is too complex or will take longer than you can commit, that's okay! Your findings will help the next developer on finding a fix.
   - Update the report with a comment detailing your findings. Describe the bug and share permalinks to the lines involved.
   - If you have a potential fix locally, commit and push your changes, then open a draft pull request that links to the bug report. Write a clear description of the issue and your proposed solution at the pull request description.
5. Ensure that the fixed bug is covered by tests (unit/visual/e2e).
6. Once completed:
   - Commit your changes and open a pull request.
   - Tag the WDS team in the report, so that we can see it more quickly and start reviewing it.

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