Update README with list of current field types

README.md

@@ -28,7 +28,7 @@ class Person(models.DeclarativeBase):
 	last_name = fields.StringField()
 	join_date = fields.DateTimeField()
 	# See fields.py for a complete list of fields
-	
+
 me = Person()
 me.first_name = "Joe"
 me.last_name = "Somebody"
@@ -37,6 +37,17 @@ me.join_date = datetime.datetime.now()
 json.dumps(me)
 ```
 
+## Field Types
+
+* DeclarativeField - Base field type. Make your own types by inheriting from this.
+* GenericField - Passes values through with no parsing or encoding.
+* StringField - Sends and receives strings. Coerces to string if necessary.
+* UUIDField - Sends and receives UUIDs and UUID v4-formatted strings.
+* DateTimeField - Sends and receives datetime objects. Parses using python-dateutil.
+* DateField - Sends and receives date objects. Parses using python-dateutil and can accept a datetime.
+* TimeField - Sends and receives time objects. Can accept a datetime.
+* JSONField - Sends and receives JSON objects. Must be able to be loaded and encoded through json.loads and json.dumps.
+
 The normal use case for declarative models and fields is for ORMs and business objects. You could use it for APIs and SDKs, or to pass data between systems via JSON. All JSON encoding is done automatically based on the field type you use.
 
-If you need a new field or have a suggestion, please create an issue or PR! 
+If you need a new field or have a suggestion, please create an issue or PR!