Let's forge ahead now and create a piece of Webform content to define our speaker registration form.
We need to be logged into our site as an administrator with Webform: Create new content permissions to continue. For the purposes of this demonstration it is best if you are logged in as the main site administrator to avoid difficulties with permission issues, as we were when we installed and enabled Webform.
Speakers at the Fictitious Conference are requested to fill out the form below to ensure an enjoyable conference experience.
Having created a Webform node (content type), we now have a standard Drupal container for our Webform content. All of the activities that follow in this demonstration will be applied within this node. Drupal automatically assigns a number, called a node ID, to each new piece of content. This number is used within the underlying database to link various database tables and their rows of data.
When we installed and enabled the Webform module in Chapter 1, Setting up Webform, the installation process created several new tables in our database to store information about Webforms. These tables provide storage areas for information regarding different aspects of each Webform we create on our site. The information we entered previously has been written to the Drupal system node table and to the main Webform table.
As we progress through the various phases of building our form, adding form components, configuring response e-mails, and making test submissions, we will be populating additional Webform system tables in the database. The node ID helps the system identify which specific Webform node each bit of data belongs to.
If at a later point in time we decide that we would like to enable site visitor comments for our Webform or change the menu settings, we can return to the node settings page by clicking on the EDIT tab. To view what our form currently looks like we may click on the VIEW tab, as shown in the following screenshot: