---
# System prepended metadata

title: Untitled

---

* Page in the docs detailing what contributions we tend to accept
* Issue template for issues:
  * Regular issue
  * New component proposal
* PR tempaltes:
  * New feature or component
  * Bugfix or general change




New Contribution Guidelines
- How we generally decide on what to add


1. If you'd like feedback before starting work open an issue, to avoid starting work on something that might not get accepted

2. If accepted, start work, checkout our contribution guidelines for a checklist of what kinds of things should be included in a PR (tests, docs, etc) & to get an idea of our code style

3. Open a PR, we'll take a look

(add note about why actions don't run for outside contributors - ask folks to run tests & linting locally if actions don't run )

- TypeScript testing sandbox

4. If the PR is approved, we'll merge it into the appropriate release branch for you


## PR template 
- screenshots of before/after
- a general summary of the component API in the description
- If there's breaking changes, a migration strategy or summary of the breaking changes for our release notes


## Other 
- look into if we can get tests running in forks 
- change tests & linting to only run against PR events instead of push events
- clarify treeshaking in docs + add subheader for it