<Box css={{ marginBlockEnd: "$050" }}>
 <Change type="ComingSoon">Coming soon</Change>
</Box>

This status indicates that the component designs have been finalized and the component
is currently under development. This status only appears on the sidebar of our navigation.

---

<Box css={{ marginBlockEnd: "$050" }}>
 <Change type="Alpha">Alpha</Change>
</Box>

This status indicates that the component is available via code, but BREAKING CHANGES
can be expected and the documentation is still in refinement. That would mean that guidance
can change, code examples might change and content can be corrected, rephrased and/or removed.

This status will appear as a banner on the component documentation page.

---

<Box css={{ marginBlockEnd: "$050" }}>
 <Change type="Beta">Beta</Change>
</Box>

This status indicates that the component design + documentation is finalized and
it is available via code. Additive changes may still occur but no breaking changes
will occur unless a security fix is needed.

This status will appear as a banner on the component documentation page.

---

#### Stable

If no status is shown on the component it indicates the component has reached a stable state.
Any changes that occur to the component will be communicated far ahead of their implementation.

The life cycle of our component on our doc site after designs have been finalized has 4 phases 3 of which are indicated by a visible status. This support guide will define each status and how it relates to the usage of the component.

Component status

### Support channels

- Slack channel (#wpds)
- GitHub issues

---

## Change/request

So you have an idea? Great, we love to hear it! Our design system aims to listen to all of the needs and ideas of our community of adopters. The team will work together with you to determine the result of the idea submitted. If you are interested in contributing a component, read more about [our process.](/../resources/guides/contribute-a-component)

### Using our slack workflow

1. Head over to our #WPDS slack channel where you will kick off your idea!
2. In the channel, type /change or /request, and you will see the option to submit an Idea to DS
3. Now, a form will open up with some questions. Please be as detailed as possible to the best of your knowledge.
4. Hooray! You submitted an idea. The WPDS team will be notified, and now it is open for public discussion across many teams that use WPDS. The team will generate a ticket and prepare it for the next steps of our workflow.

 

## Not at the Washington Post?

Contact us at wpds@washingtonpost.com

Get help

<Alert dismissable={false} variant={"warning"}>
 WPDS v0 is no longer under active development.
</Alert>

 

The Washington Post Design system has evolved from its initial form — known as &ldquo;version 0&rdquo; — developed from 2018&mdash;2019.

 

**Version 0 has been deprecated to legacy status and is no longer under active development.**

 

For additional information visit the [WPDS v0 docs site](https://build.washingtonpost.com/v0).

v0 Design System

## Cycles

- Bug fixes are released in the form of a patch release. This is the most frequent release type. A patch release is a release that fixes a bug in a token or a component (design or in code). We ship patches on a weekly basis. For example, "1.0.1" is the first patch release.

- Feature releases are released in the form of a minor release. This is the second most frequent release type. A minor release is a release that adds to our tokens or components (brand new components, tokens too) (design or in code). We ship minor releases on a monthly basis. For example, "1.1.0" is the first minor release.

- Major releases are releases that add new features to the platform. We ship major releases on a quarterly basis. For example, "2.0.0" is the first major release.

<InlineSVG
 path="/img/process/release/release-diagram.svg"
 width={400}
 height={200}
/>

##

Components are released batches but only components with full documentation are fully supported. Any other components that are released in the batch without docs will be consider in Alpha status and will be indicated on the doc site as Alpha status. Those will not be fully supported until official release.

Release cycles

<Alert dismissable={false} variant="information">
 Note: We reevalute our supported platforms at the end of our fiscal
 year.
</Alert>

 

## Browsers

We support the following browsers (up to the latest 2 stable versions):

- Google Chrome
- Apple Safari
- Mozilla Firefox
- Microsoft Edge

```jsx
last 2 Chrome major versions, last 2 Safari major versions, last 2 Firefox major versions, last 2 Edge major versions, not dead
```

See Browserslist config [link](https://browsersl.ist/#q=last+2+Chrome+major+versions%2C+last+2+Safari+major+versions%2C+last+2+Firefox+major+versions%2C+last+2+Edge+major+versions%2C+not+dead)

 

## Server environments

We support Node.js 18 and 16

 

## React

- 18

 

## React frameworks

We are open to adding more React frameworks here. Contact us through our [support](/support) channels.

- Next.js 14+

 

## Typescript

Ui Kit requires a minimum version of TypeScript 3.8. This aims to match the policy of DefinitelyTyped, with the support of the versions of TypeScript that are less than two years old.

More about the platforms the WPDS UI Kit supports

Component status

Get help

v0 Design System

Release cycles

Supported platforms