You can see from the preceding lists, there are fields for most of the various types of information that you will need to store. It's not just a matter of the type of data, like text or number, but often what information the data represents, like a phone number or URL, and that's because there is often programming code that provides the formatting or validates what has been entered. For example, entering an email address in a phone number field will cause an error to be displayed.
So, let's take a look at a list of the information that we will want to store for an appointment, and the type of field that we can use for that. We'll also decide on a name for each field, which will be used for its label on the entry form, and help text with a a description to remind us or inform other users about the field's use:
| Information needed | Field type | Label | Help Text |
|---|---|---|---|
| Client name | text (plain) | Name1 | |
| Client phone number | text (plain)2 | Phone | ###-###-#### |
| Client email address | For example, bill@gmail.com | ||
| Appointment date and time | date | Date | |
| Who the appointment is with | list (text) | With | Select a name |
| The purpose of the appointment | text (plain, long) | Reason | |
| The status of the appointment | list (text) | Status | Select a status |
1 This is the renamed Title field
2 There is a field type for telephone number, but it is not enabled, so we will use plain text
With our list prepared, it's time to create the fields for our content type.