> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/17.latest/develop-with-umbraco/tutorials/starter-kit/lessons/2-add-a-blog-post-publication-date.md).

# Add a Blog Post Publication Date

In this lesson, you will learn how to add a new date property to blog posts.

## Outcome

Content editors can specify the publication date for a blog post. Blog posts are displayed with the most recent publication date appearing first.

## Takeaway

Learn how to:

* Add a new property to a Document Type
* Edit a Template to display the new property
* Sort a list of items by a new property

## Steps - Part One

1. In the **Settings** section, expand **Document Types**.
2. Click on *Blogpost*. This is the Document Type that defines the fields for this type of page.

   ![Blogpost Document Type](https://2050077833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb0WSXUuM7Qx5BfREagAI%2Fuploads%2Fgit-blob-8166628d9702f6b0ff0fd6c1a4da859d6ca763c0%2FBlogpost-Document-Type-v14.png?alt=media)
3. The Document Type contains 2 groups: *Content* and *Navigation & SEO*.
   * At the bottom of the *Content* group select **Add property**.
   * This opens the **Property Editor** dialog window.
4. Give the property a name: *Publication Date*.
5. Give the property a description: *The date of the blog post. This is the date used to display the most recent posts first.*
   * Always try to add a meaningful description to help your editors.
6. Select **Select Property Editor** to specify what type of data is being stored.
   * Select the **Date Picker** icon since we need a standard date.
7. Enable the field in the validation section to make it mandatory.
8. Click **Add** to close the dialog and save the property.

   ![Property settings](https://2050077833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb0WSXUuM7Qx5BfREagAI%2Fuploads%2Fgit-blob-cc5d2737650c8aec2b77d476962a35f01c06ba9b%2Fproperty-settings-v14.png?alt=media)
9. Select the **Reorder** option near the top-right of the window.
   * Drag the new property after *Page Title*.
   * A logical order to your properties will make things easier for your editors.
10. Click **I am done reordering** near the top-right of the window.
11. Select **Save** the Document Type. A confirmation message appears confirming that the Document Type is saved.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/17.latest/develop-with-umbraco/tutorials/starter-kit/lessons/2-add-a-blog-post-publication-date.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.