A simple starter project for playing around with Tailwind in a proper PostCSS environment.
To get started:
-
Clone the repository:
git clone https://github.com/tailwindcss/playground.git tailwindcss-playground cd tailwindcss-playground
-
Install the dependencies:
# Using npm npm install # Using Yarn yarn
-
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.
-
Open
public/index.html
in your editor and start experimenting!
A CodeSandbox version of this playground is one click away!
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.
Sometimes you want to have a subdirectory on the master
branch be the root directory of a repository’s gh-pages
branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master
branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist
.
Remove the dist
directory from the project’s .gitignore
file (it’s ignored by default by Yeoman).
Make sure git knows about your subtree (the subfolder with your site).
git add dist && git commit -m "Initial dist subtree commit"
Use subtree push to send it to the gh-pages
branch on GitHub.
git subtree push --prefix dist origin gh-pages
Boom. If your folder isn’t called dist
, then you’ll need to change that in each of the commands above.
If you do this on a regular basis, you could also create a script containing the following somewhere in your path:
#!/bin/sh
if [ -z "$1" ]
then
echo "Which folder do you want to deploy to GitHub Pages?"
exit 1
fi
git subtree push --prefix $1 origin gh-pages
Which lets you type commands like:
git gh-deploy path/to/your/site