Feature Request

Add a file named pull_request_template.md in the .github folder of the repository so that whenever a new PR is opened on the repository it follows the template.

The problem

Wrapping a TextInput in <TouchableWithoutFeedback onPress={Keyboard.dismiss}> prevents text input in web browsers. It works in the Android emulat

Would be great to provide a documentation section with practical examples on how we propose to handle various popular patterns which usually are solved by pseudo selectors, nested classes etc.

Environment
Windows 10/ Chrome, Microsoft Edge and Firefox

Steps
Open the page http://localhost:8080/step1-02/demo/ as per the instructions in the README file.

Actual Result
The logo image is not loaded in the page. In the Developer tools 404 error is seen.
Only the alternate text is visible in browser.

Expected Result
The logo image should load

Clearly describe the bug

"false-positive" no-descending-specificity with "empty" definitions (see below)

Which rule, if any, is the bug related to?

no-descending-specificity

What code is needed to reproduce the bug?

    nav {
      display: inline-block;
      a {
        display: inline-block;
      }
    }

    a,
    button,
    label {
      &:focus,

I am looking into variants and i feel like its a bit confusing which is the old api and which is the new one?

I feel like I should just be able to drop the variant function onto a component and give it scale="accents" and then if I pass variant="info" then it should look in the theme object for accents and pull the info key inside that yet it doesn't do that unless I write `variants: {

How import stylesheets-files?

@import url('https://fonts.googleapis.com/css?family=Spectral&display=swap');

Came up with the following solution:

import {create} from 'jss';

create().createStyleSheet({
	'@import': 'url(https://fonts.googleapis.com/css?family=Spectral&display=swap)'
}).attach();

But I would like to do it in global styles.

But the `j

Describe the enhancement

Firstly we add more chapters to docs/CONFIGURATION.md to group working integrations

• Next.js heading and link to with-linaria example
• Gatsby.js heading with a link to gatsby-plugin-linaria and optional custom config. Custom config

To reproduce:

$ npm pack styled-jsx@3.2.4
npm notice
npm notice 📦  styled-jsx@3.2.4
npm notice === Tarball Contents ===
npm notice 6.1kB  dist/.DS_Store
npm notice 599B   dist/_constants.js
npm notice 22.3kB dist/_utils.js
npm notice 8.2kB  dist/babel-external.js
npm notice 46B    babel-test.js
npm notice 753B   dist/babel-test.js
npm notice 41B    babel.js
npm notice 10.4k

Hi Mathew,

I think this library is a gem and is very valuable to set up a new site. However, I found it extremely hard to understand how to use rhythm, scale and other functions, even after Googling, looking at the source code, it is still not clear why and when we need to use rtythm and why rtythm(1) = 1.25rem, why we need something like ...scale(1/10) or ...scale(2/5).

It will

The Styletron documentation has a section on Descendant Hover. In practice, we typically include hover styles with focus/active styles for accessibility. Therefore, we should include documentation on how to add descendant focus/active styles.

Video ❤️

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

A minisite for jsxstyle would be a nice way to show off the things you can do with jsxstyle. As far as content goes, the README provides a decent starting point.

Description

We should document the way insertRule removes unsupported rules so people are not confused when not finding a rule that is part of a fela style. See #783

Create a next.js template, to make it easier for people to adopt it.

This a 🐛 bug report.

.documents is not accepting an object as second parameter even though it's documented in the README.

Expected Behavior

var someState = { render: 'me' }

// Documented API:
// `compiler.documents(routename, [opts], done(err, { buffer, hash }))`
compiler.documen

Frameworks like Gatsby already come with their own PostCSS loader, handling autoprefixing and more. I think treat could reduce its dependencies by delegating post-processing to webpack loaders.