No description
Find a file
Simon Vrachliotis b0e5bdc952
Update README.md
Add link to CodeSandbox URL n README.
2020-08-21 15:21:32 +10:00
.vscode add vscode extension recommendation 2019-05-17 00:05:44 +01:00
public Add new intro page design, restructure folders 2019-05-16 14:13:29 -04:00
.gitignore Add new intro page design, restructure folders 2019-05-16 14:13:29 -04:00
package.json updating playgound to recent (v1.7) Tailwind versions. Upgrading dependencies, README, removing PurgeCSS which is now built-in, and configured from the config file 2020-08-20 16:35:37 +10:00
postcss.config.js updating playgound to recent (v1.7) Tailwind versions. Upgrading dependencies, README, removing PurgeCSS which is now built-in, and configured from the config file 2020-08-20 16:35:37 +10:00
README.md Update README.md 2020-08-21 15:21:32 +10:00
sandbox.config.json Create sandbox.config.json 2019-12-11 14:10:36 +01:00
tailwind.config.js moving variants and plugins outside of theme in config 2020-08-21 13:00:44 +10:00

Tailwind CSS Playground

A simple starter project for playing around with Tailwind in a proper PostCSS environment.

To get started:

  1. Clone the repository:

    git clone https://github.com/tailwindcss/playground.git tailwindcss-playground
    
    cd tailwindcss-playground
    
  2. Install the dependencies:

    # Using npm
    npm install
    
    # Using Yarn
    yarn
    
  3. Start the development server:

    # Using npm
    npm run serve
    
    # Using Yarn
    yarn serve
    

    Now you should be able to see the project running at localhost:8080.

  4. Open public/index.html in your editor and start experimenting!

Play with it on CodeSandbox

A CodeSandbox version of this playground is one click away!

Building for production

Even though this isn't necessarily a starter kit for a proper project, we've included an example of setting up cssnano to optimize your CSS for production.

To build an optimized version of your CSS, simply run:

# Using npm
npm run production

# Using Yarn
yarn production

After that's done, check out ./public/build/tailwind.css to see the optimized output.