> 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: Updating Props

## Article: Updating Props

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

## Article Content:

<!-- heading -->

# Updating Props

<!-- end heading -->

## Considerations

Components should be performant, accessible, and maintainable. When contributing a new prop or updating the types of an existing prop, ask yourself how your change might:

- Be backwards compatible
- Increase or maintain performance
- Improve or maintain accessibility
- Address a pain point in the consumer experience
- Reduce complexity of the source code

If a component isn't flexible enough to meet your project's requirements, or if you're unsure whether a component is right for your use case, [contact our UX](https://wix.slack.com/archives/CR7P4A1UP) to discuss and evaluate. We're happy to collaborate to find a solution.

---

## How to contribute

To add or update a prop:

1. Explore and align on whether to add a new prop or update the types of an existing prop.
2. Add your change to the props interface.
3. Write or update the prop's description comment in the same change. Write it in present tense, start with a verb and end with a period, for example `Controls the size of the input.` One sentence is enough for most props; add a second when the prop only applies under a condition or needs more detail. The docs site shows it in the props table, so a prop without one is incomplete.
4. Update the `@default` value if relevant in the props interface.
5. Add tests to cover the changes.
6. Commit your changes and open a pull request.

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