From d249608f1e0b521fedc94e23def00fff80e40ea0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C3=ABl=20De=20Boey?= <info@michaeldeboey.be>
Date: Sat, 2 Dec 2017 17:44:23 +0100
Subject: [PATCH] appearance

---
 docs/source/docs/forms.blade.md | 34 +++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/docs/source/docs/forms.blade.md b/docs/source/docs/forms.blade.md
index 7f1f822c8..aa4d8a8e6 100644
--- a/docs/source/docs/forms.blade.md
+++ b/docs/source/docs/forms.blade.md
@@ -37,3 +37,37 @@ Form controls are great candidates for component classes, but just for fun, here
   </div>
 </div>
 @endcomponent
+
+## Customizing
+
+### Responsive, Hover, and Focus Variants
+
+By default, no hover, focus, or group-hover variants are generated for form control appearance utilities.
+
+You can control which variants are generated for form control appearance utilities by modifying the `appearance` property in the `modules` section of your Tailwind config file.
+
+For example, this config will _also_ generate hover and focus variants:
+
+```js
+{
+    // ...
+    modules: {
+        // ...
+        appearance: ['responsive', 'hover', 'focus'],
+    }
+}
+```
+
+### Disabling
+
+If you aren't using the form control appearance utilities in your project, you can disable them entirely by setting the `appearance` property to `false` in the `modules` section of your config file:
+
+```js
+{
+    // ...
+    modules: {
+        // ...
+        appearance: false,
+    }
+}
+```