= models . ImageField ( upload_to = "authors" ) Next you'll need to register your model with Django's admin to make it available as a content type. If your content type only exposes some new fields that you'd like to make editable in the admin, you can simply register your model using the mezzanine.pages.admin.PageAdmin class: Any regular model fields on your content type will be available when adding or changing an instance of it in the admin. This is similar to Django's behaviour when registering models in the admin without using an admin class, or when using an admin class without fieldsets defined. In these cases all the fields on the model are available in the admin. If however you need to customize your admin class, you can inherit from PageAdmin and implement your own admin class. The only difference is that you'll need to take a copy of PageAdmin.fieldsets and modify it if you want to implement your own fieldsets, otherwise you'll lose the fields that the Page model implements: When registering content type models with PageAdmin or subclasses of it, the admin class won't be listed in the admin index page, instead being made available as a type of Page when creating new pages from the navigation tree. Note When creating custom content types, you must inherit directly from the Page model. Further levels of subclassing are currently not supported. Therefore you cannot subclass the RichTextPage or any other custom content types you create yourself. Should you need