> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-site-builder/unit-2-designing-and-planning-content/discussion/exercise-2-3-create-a-content-type.md).

# Exercise 2.3: Create a content type

Different content types meet different content requirements while ensuring consistency across a type of content. Content types are set up with text boxes and structured through pull-down menus and check boxes.

<https://www.drupal.org/docs/user\\_guide/en/structure-content-type.html>

In this exercise you’ll create a Job Posting content type. The screenshot below shows the form and what the posting will look like on the website.

| Create job posting form                                   | Individual job posting                               |
| --------------------------------------------------------- | ---------------------------------------------------- |
| ![Image of Job posting form](/files/AageBG7b2OSXPjsxBHLo) | ![Image of job Posting](/files/hbG8WA0Jbcg0sMkVuFS4) |

As the name suggests, the *Job Posting* content type will be used to post jobs on the website. There are three stages involved:

1. Create content type
2. Review your content type
3. Adjust the permissions for your new content type

## Create a content type

1. Go to *Structure* → *Content types*. Click **Add content type**.
2. Next, type in the content name and description:
   * **Name**: Job Posting
   * **Description**: Post a job to the jobs section of the site. (The description should explain the content type.)
3. Next, scroll down to the configuration tabs. Under **Submission form settings** follow these:
   * **Title field label:** Job title.
   * **Preview before submitting:** Disabled.
   * **Explanation or submission guidelines**: Leave this empty. This field lets you put in any specific instructions for the content type.
4. We want jobs to be published by default, but not automatically promoted to the front page, so under **Publishing options** use these settings:

   * **Published**: Leave selected.
   * **Promoted to front page:**: Deselect.
   * **Sticky at top of lists**: Leave unselected.
   * **Create new revision**: Leave selected.

   <img src="/files/riXkrtBXNlMLWVLfla2E" alt="Image of Add content type" data-size="original">

   > **Note:** Some Content Authors (depending on their permissions) will be able to override these defaults when creating content.
5. We don’t want the author’s name or the content publish date displayed, so under **Display settings** deselect the *Display author and date information option* if it is selected.
6. We also don’t want job listings being added to the menu navigation, so under the default **Menu settings**, deselect Main menu.
7. Click ***Save and manage fields***. This brings you to the Manage Fields admin page - admin/structure/types/manage/job\_posting/fields. Review the default fields that were created for your new content type.

![Image of Jobs content type fields](/files/PUEyWiRNWxMvyglnX2zl)

## Review your content type

Go to *Content* → *Add content* and select **Job posting**. Review the form for your new content type.

## Adjust permissions for your new content type

Go to **People** → **Permissions** and change the permissions to match the other content types.

## Challenge exercise 2.4: Plan a new content type

Looking back on what you’ve learnt so far during this unit, think about how you’d add a new content type, such as ‘Media conference’. What fields would you need to include? Plan out the process you’d follow to create the new content type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-2-designing-and-planning-content/discussion/exercise-2-3-create-a-content-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.