A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

Situation

I am working on a set of components which can be easily reused over several Gatsby projects. Additionally I create project specific components.

To provide a proper documentation to the team of other devs & editors, I want to display documentation from my project specific components plus the ones I included from the (community) rep

Describe the bug

• Dead anchor links. The color system doesn't list the variables/information for black and white.
• We are also missing the View source link on this page

To Reproduce
Steps to reproduce the behavior:

1. Go to https://primer.style/css/support/color-system
2. Click on Black or White in the color palette

Steps to reproduce:

1. Open https://rebassjs.org/flex
2. Click on "Getting Started" (or any item on the left menu)

Expected:
Sends you to "Getting Started Page"

Actual:
Nothing happens. You need to click "Getting Started" a second time, to actually get sent there.

Basically you need to click left nav items twice instead of once, before getting sent to the page.

Describe the bug

There is no description on the website how to set the error state of a page. Only picture describing that the page number should be substituted by error icon, but not how.

How to reproduce

Steps to reproduce the behavior:

1. Go to https://v2.clarity.design/wizards
2. Search for clrWizardPageHasError

Expected behavior

Clear description of the `clrWiz

I'm wondering why there isn't a page in the documentation with all the styles declared and every classes in a single page.
It's really easy to find the right class for beginners this way.

Are you planning to integrate something like this maybe?

Include React95 logo in the bundle so users could use it (for example in Start button like shown here). It would be nice to make it as an SVG too

Describe the bug
By clicking See guide in Library Screen the app opens a broken link.

To Reproduce
Steps to reproduce the behavior:

1. Go to Home Screen
2. Click Library
3. Scroll down
4. Click in See Guide link
5. Wait Browser open Doc Page
6. See error

Expected behavior
Open Install local library guide page

Screenshots

Expected Page

![image](https://user-im

Issue Summary

Related to #1897 which was closed by this PR, when the modal closes, the correct slide down animation is missing when the component is set to true directly using the syntax open && <Modal open={open} />.

Expected behaviour

See the Modal component on the [Polaris](https://polaris.shopify.com/components/overlays/moda

• I have searched the issues of this repository and believe that this is not a duplicate.

Version

1.11.10

Component

Nav

Environment

Chrome Latest

Reproduction link

Steps to reproduce

期望可以透传s

Based on the discussions around #121 and the test we just merged in #662, we are going to convert theme-ui to TypeScript! 🎉 The plan is to go package-by-package and gradually move all .js files to .ts files.

Add tabs option to the docs component ?

Would be cool to have the option to add tabs to the component, unless there is already a way to do this. Thanks

Currently it only accepts onClick but badges can also link to other pages as well. It should accept href similar to EuiButton.

Current behavior

When applying mixins, vue - as far as i understand - is taking account of the order. For example:

const a = {
  props: {
    value: { type: [ String, Number ], default: '' }
  }
}
const b = {
  props: {
    value: { type: Number, default: Infinity }
  }
}

export default {
  name: 'my-component',
  mixins: [ a, b ]  // the resulting value-type will be

As reported by @stephyswe on Discord:

1. Prepare your design system for export - BABEL_ENV needs "set" to work for Windows Users, also --copy-files to add .mdx files in /dist/ folder
   REPLACE
   {
   "scripts": {
   "build": "BABEL_ENV=production babel src -d dist",
   WITH
   {
   "scripts": {
   "build": "set BABEL_ENV=production&& babel src -d dist --copy-files",
   ...

Currently we only provide documentation for consuming the existing custom-values offered by Stylable, stMap, stArray and if you explicitly import it stBorder.

Need to add the relevant documentation to both the package readme and to the stylable.io.

Hello, I am using atomize in one of my soon to be released project. I loved the concept how atomize works.
But I feel the documentation needs more work. Also there aren't any release changelog in github.
It would be good to have a changelog so that I can keep track with version updates.
Also any plan of moving the examples to functional components and introducing more hooks?

Also I had some

Description

The small card description does not look right:

Small cards should not be used without --quiet.

The card is in fact used without --quiet and adding --quiet messes up the styling

Link to documentation

https://opensource.adobe.com/spectrum-css/components/card/

With docs and static storybook now integrated in the CI process, the npm run storybook script no longer builds a static storybook.

We should either a) remove the script all together or b) refactor the code to allow devs to build static stories if they run npm run storybook.

Component to amend

Selector

Visual

Context

We have a few issues to address on this:

• The Selector component is currently not accessible - not focusable via keyboard. That's because the markup structure

Is your feature request related to a problem? Please describe.

Some components are opinionated about what they want as children (most aren't)

Example:

<Breadcrumb>
  <Breadcrumb.Link href="/home">Home</Breadcrumb.Link>
  <Breadcrumb.Link href="/parent">Parent</Breadcrumb.Link>
  <Breadcrumb.Link href="/parent/page">Page</Breadcrumb.Link>
</Breadcrumb>

Right now, th