> For the complete documentation index, see [llms.txt](https://mariohernandez.gitbook.io/components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariohernandez.gitbook.io/components/drupal-site-building/blog-content-type.md).

# Blog articles

We'll modify Drupal core's Article content type so we can use it to generate blog post for our site. Blog articles are the content we will display on the homepage as Featured Content and From our Blog. This means each card in the homepage represents a blog article in a compact view. We will achieve the Card and Card Wide displays using Drupal's View Modes.

1. From Drupal's Admin Toolbar, click **Structure | Content Types**
2. Click **Manage fields** next to **Article**
3. Delete the \*\*Comments \*\*field
4. Add the missing fields based on the table below
5. Click the **Save and manage fields** button at the bottom of the page

#### Add the following fields:

| Field label | Machine name     | Field type                                                 |
| ----------- | ---------------- | ---------------------------------------------------------- |
| Title       | `label`          | **This** **field is auto generated. No need to create it** |
| Body        | `body`           | **This** **field is auto generated. No need to create it** |
| Date        | `date`           | **This** **field is auto generated. No need to create it** |
| Image       | `field_image`    | Media Reference                                            |
| Tags        | `field_tags`     | Taxonomy Term Reference                                    |
| Author      | `field_author`   | User Reference                                             |
| Category    | `field_category` | Text (plain)                                               |

For the Author field, set the following configuration:

* **Allowed number of values** is 1
* **Reference type** deselect *Include the anonymous user*


---

# 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, and the optional `goal` query parameter:

```
GET https://mariohernandez.gitbook.io/components/drupal-site-building/blog-content-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.