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. "

Bug Report

From the docs section Add favicon and metadata

Comment in code example states for "The doc prop contains some metadata about the page being rendered that you can use."

// The doc prop contains some metadata about the page being rendered that you can use.
const Wrapper = ({ children, doc }) => <React.Fragment>
  

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 👉 PR primer/css#1036

To Reproduce
Steps to reproduce the behavior:

1. Go to https://primer.style/css/support/color-syst

The docs on rebassjs.org are pretty slim when it comes to using forms and the props that are accepted and what they do.

I was able to use inputs and checkboxes without too much effort but wanted to use a Switch in an instance instead of a checkbox. A switch is a ON|OFF Component so it would make sense that in the DOM it would use a checkbox and allow handlers with OnChange but that is not wha

When applying FormField label styles (see #3998), for examplesize, the prop is being leaked to the DOM while it shouldn't.

Originally posted by @ericsoderberghp in grommet/grommet#3998

Not part of this review per-se, but we shouldn't be leaking `size` into the DOM.

Summary

Our current messaging around clarity core been" ETA" is confusing internal teams that are unclear whether the web components are even available through NPM.

Based on a discussion today, we want to update our messaging in such a way that we have the flexibility to make breaking changes to works-in-progress but also clearly delineate components and utilities whose API is stable.

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

When rendering a list page in the web admin using Filters and promoted filters, the UI 'jumps' after re-hydration.

<img width="1425" alt="Screen Shot 2020-04-28 at 9 32 13 AM" src="https://user-images.gi

• 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

In order to make the Tailwind preset more approachable for people that already know Tailwind, we should:

• Font sizes should have the same aliases (e.g. lg = 2)
• Colors should be aliased to the same aliases * 100, e.g. purple.5 === purple.500
• Breaking change for a major version: Make the padding scale match Tailwind's

This has confused me and at least 2 other devs. EuiInMemoryTable requires a selection prop and an itemId prop to enable selection. The only way to know this is looking at the Demo JS tab, spotting the itemId line, and recognizing it is important. Without itemId selection looks like it should be working but it mysteriously doesn't. Information about the necessary props should be inc

• Sorry if this is not the right place to ask, I read through the documentation and could not find anything on Nuxt
• Searched nuxt.js subreddit no mention
• I am using Nuxt in SSR mode, how would you add this library to it? Could you kindly the documentation to add a small section in case it is simple so that in the future people wont ask the same question
  Thank you for your time

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

On the Build step of the tutorial when explaining about GlobalStyles and the addDecorator function it never actually says where to add the code. I ended up adding it to the config.js and that worked, but it doesn't tell you to do that in the tutorial. In the actual Docs on [Decorators](https://storybook.js.org/docs

The problem

We need a more modern way to edit examples.

• TypeScript
• pug
• SCSS

It would be incredible if we could get contextual autocompletion

Proposed solution

• Use Monaco as the editor
• Update the inbrowser-compiler with
  • possible babel-typescript
  • pug co

The following warnings appear in the console during compilation, and they are also shown by stylable intelligence:

WARNING in Stylable: "@st-scope" must receive a simple selector, but instead got: ":global(.foo)"
@st-scope :global(.foo) { }

WARNING in Stylable: "@st-scope" received an unknown symbol: "html"
@st-scope html { }

The compiled CSS works correctly, though.

• I searched for nuxt in the issues section and did not find anything
• the documentation also covers only gulp webpack and manual install
• how do I install CodyHouse base in nuxt
• Would be awesome if you can add a section in the guide for the same
• Fantastic work team, cheers

@finnhvman You say

Components can be resized fluidly to match layout needs, otherwise they take up the size necessary.

Can you write up some guidelines how how we should actually do resizing.

For example matter buttons have min-width, height and line-height specified. So they don't actually take up the size necessary. Should we override all three of these.

Some css libs o

It would be nice to add a symbol to the theme objects so they can easily be identified.

A good reason for this is to be able to easily write a custom Jest snapshot serializer and avoids the entire theme from being serialized into the snapshot.

We have a custom Jest snapshot serializer that does this, but it has to rely on checking for the existence of several theme properties to identify the

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

There are two definitions of styled-components installed:

• styled-components_v3.x.x.js - definition for an older version (Orbit already uses 4.x.x)
• [styled-components_vx.x.x.js](https://github.com/kiwicom/orbit-components/blob/master/flow-typed/npm/sty