From caa00bbd3879a994518bd74bf023c1db2aeaa6b4 Mon Sep 17 00:00:00 2001
From: Adam Wathan <adam.wathan@gmail.com>
Date: Wed, 15 Nov 2017 11:14:24 -0500
Subject: [PATCH] Add options key to default config and document

---
 defaultConfig.stub.js                   |  12 +--
 docs/source/docs/configuration.blade.md | 117 +++++++++++++++++++++++-
 docs/tailwind.js                        |   1 +
 3 files changed, 123 insertions(+), 7 deletions(-)

diff --git a/defaultConfig.stub.js b/defaultConfig.stub.js
index 04f1158b3..3731eb808 100644
--- a/defaultConfig.stub.js
+++ b/defaultConfig.stub.js
@@ -759,17 +759,17 @@ module.exports = {
 
   /*
   |-----------------------------------------------------------------------------
-  | Packages
+  | Options                  https://tailwindcss.com/docs/configuration#options
   |-----------------------------------------------------------------------------
   |
-  | Here is where you can define the configuration for any Tailwind packages
-  | you're using. These can be utility packs, component bundles, or even
-  | complete themes. You'll want to reference each package's
-  | documentation for a list of settings available for it.
+  | Here is where you can set your Tailwind configuration options. For more
+  | details about these options, visit the configuration options documentation.
   |
   */
 
-  packages: {
+  options: {
+    prefix: '',
+    important: false,
   },
 
 }
diff --git a/docs/source/docs/configuration.blade.md b/docs/source/docs/configuration.blade.md
index ee3ed52b9..351999806 100644
--- a/docs/source/docs/configuration.blade.md
+++ b/docs/source/docs/configuration.blade.md
@@ -28,6 +28,121 @@ Please see the [installation](/docs/installation#4-process-your-css-with-tailwin
 
 As you can see below, the default config file is heavily documented. Read through it to get a better understanding of how each section can be customized for your project.
 
+<pre class="h-128 overflow-y-scroll language-javascript"><code>{!! str_replace('// var defaultConfig', 'var defaultConfig', file_get_contents(dirname(dirname(__DIR__)).'/defaultConfig.stub.js')) !!}</code></pre>
+
+## Options
+
+In addition to defining your project's design system, the configuration file can also be used for setting a variety of global options.
+
+These options are available under the top-level `options` key, located at the bottom of the configuration file by default.
+
+### Prefix
+
+The `prefix` option allows you to add a custom prefix to all of Tailwind's generated utility classes.
+
+This can be really useful when layering Tailwind on top of existing CSS where there might be naming conflicts.
+
+For example, you could add a `tw-` prefix by setting the `prefix` option like so:
+
 ```js
-{!! str_replace('// var defaultConfig', 'var defaultConfig', file_get_contents(dirname(dirname(__DIR__)).'/defaultConfig.stub.js')) !!}
+{
+  // ...
+  options: {
+    prefix: 'tw-',
+    // ...
+  }
+}
+```
+
+It's important to understand that this prefix is added to the beginning of each *utility* name, not to the entire class name.
+
+That means that classes with responsive or state prefixes like `sm:` or `hover:` will still have the responsive or state prefix *first*, with your custom prefix appearing after the colon:
+
+```html
+<div class="tw-text-lg md:tw-text-xl tw-bg-red hover:tw-bg-blue">
+  <!-- -->
+</div>
+```
+
+Prefixes are only added to standard Tailwind utilities; **no prefix will be added to your own custom utilities.**
+
+That means if you add your own responsive utility like this:
+
+```css
+@responsive {
+  .bg-brand-gradient { ... }
+}
+```
+
+...the generated responsive classes will not have your configured prefix:
+
+```css
+.bg-brand-gradient { ... }
+@media (min-width: 576px) {
+  .sm\:bg-brand-gradient { ... }
+}
+@media (min-width: 768px) {
+  .md\:bg-brand-gradient { ... }
+}
+@media (min-width: 992) {
+  .lg\:bg-brand-gradient { ... }
+}
+@media (min-width: 1200px) {
+  .xl\:bg-brand-gradient { ... }
+}
+```
+
+If you'd like to prefix your own utilities as well, just add the prefix to the class definition:
+
+```css
+@responsive {
+  .tw-bg-brand-gradient { ... }
+}
+```
+
+### Important
+
+The `important` option lets you control whether or not Tailwind's utilities should be marked with `!important`.
+
+This can be really useful when using Tailwind with existing CSS that has high specificity selectors.
+
+To generate utilities as `!important`, set the `important` key in your configuration options to `true`:
+
+```js
+{
+  // ...
+  options: {
+    important: true,
+    // ...
+  }
+}
+```
+
+Now all of Tailwind's utility classes will be generated as `!important`:
+
+```css
+.leading-none {
+  line-height: 1 !important;
+}
+.leading-tight {
+  line-height: 1.25 !important;
+}
+.leading-normal {
+  line-height: 1.5 !important;
+}
+.leading-loose {
+  line-height: 2 !important;
+}
+```
+
+Note that any of your own custom utilities **will not** be marked as `!important` just by enabling this option.
+
+If you'd like to make your own utilities `!important`, just add `!important` to the end of each declaration yourself:
+
+```css
+@responsive {
+  .bg-brand-gradient {
+    background-image: linear-gradient(#3490dc, #6574cd) !important;
+  }
+}
 ```
diff --git a/docs/tailwind.js b/docs/tailwind.js
index 7eaf6c7bb..8a8c63e66 100644
--- a/docs/tailwind.js
+++ b/docs/tailwind.js
@@ -68,6 +68,7 @@ config.width = Object.assign(config.width, {
 
 config.height = Object.assign(config.height, {
   '7': '1.75rem',
+  '128': '32rem',
 })
 
 config.padding = Object.assign(config.padding, {