From d921b7f23f446cfb1b9f36edf6c996d013ed1c92 Mon Sep 17 00:00:00 2001 From: James Brooks Date: Mon, 6 Nov 2017 14:47:11 +0000 Subject: [PATCH] Typo in color --- docs/source/docs/configuration.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/docs/configuration.blade.md b/docs/source/docs/configuration.blade.md index d927c26e882d..1906fe38a610 100644 --- a/docs/source/docs/configuration.blade.md +++ b/docs/source/docs/configuration.blade.md @@ -9,7 +9,7 @@ Tailwind's defining feature is its ability to be customized. We understand that ## Introducing the Tailwind config -The Tailwind config file is where you customize Tailwind specifically for your project. It will include your colour palette, fonts, text weights, spacing and sizing definitions, borders, shadows, and much more. Think of the Tailwind config as a living definition of your design system. +The Tailwind config file is where you customize Tailwind specifically for your project. It will include your color palette, fonts, text weights, spacing and sizing definitions, borders, shadows, and much more. Think of the Tailwind config as a living definition of your design system. Tailwind is actually built on PostCSS and therefore is configured entirely in JavaScript. This can feel a little strange at first, especially if you're more familiar with setting variables in a preprocessor like Sass or Less. In practice though, defining your CSS configuration in a real programming language like JavaScript has a lot of benefits. You can create variables to share parts of your configuration. You have the full power of JavaScript to dynamically create or manipulate values. Eventually you may even be able to automatically generate custom documentation for your project from this config file.