Updated website features documentation for the new AnnotationLevel.NONE.

website/features/Data.html

@@ -31,7 +31,8 @@
 			explicitly; <code>@Data</code> is smart enough to defer to those annotations.
 			</p><p>
 			All generated getters and setters will be <code>public</code>. To override the access level, annotate the field with an explicit <code>@Setter</code> and/or
-			<code>@Getter</code> annotation.
+			<code>@Getter</code> annotation. You can also use this annotation (by combining it with <code>AccessLevel.NONE</code>) to suppress generating a getter and/or setter
+			altogether.
 			</p><p>
 			All fields marked as <code>transient</code> will not be considered for <code>hashCode</code> and <code>equals</code>. All static fields will be
 			skipped entirely (not considered for any of the generated methods, and no setter/getter will be made for them).

website/features/GetterSetter.html

@@ -55,6 +55,9 @@
 				Any annotations named <code>@NonNull</code> (case insensitive) on the field are interpreted as: This field must not ever hold
 				<em>null</em>. Therefore, these annotations result in an explicit null check in the generated setter. Also, these
 				annotations (as well as any annotation named <code>@Nullable</code>) are copied to setter parameter and getter method
+				</p><p>
+				Using the <code>AccessLevel.NONE</code> access level simply generates nothing. It's useful only in combination with
+				<a href="Data.html"><code>@Data</code></a>.
 				</p>
 			</div>
 		</div>