> 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/13.latest/tutorials/starter-kit/lessons/2-add-a-blog-post-publication-date/part-3.md).

# Add a Blog Post Publication Date

In [Part Two](/umbraco-cms/13.latest/tutorials/starter-kit/lessons/2-add-a-blog-post-publication-date/part-2.md), we displayed a nicely formatted publication date on the blog post page.

Finally, in Part Three we shall change the blog listing.

## Steps - Part Three

1. In the **Settings** section, expand **Partial View Macro Files**.
   * Select *LatestBlogPosts.cshtml*.
   * **Macros** are beyond the scope of this lesson, but you don't need to understand them right now.
2. Scroll down to find the `blogpost-date` element and change it to use a nicely formatted Publication Date, i.e.:

   ```html
   <small class="blogpost-date">@post.PublicationDate.ToLongDateString()</small>
   ```
3. Further up in the view, you also need to redefine the `blogposts` variable:

   ```csharp
   var blogposts = startNode.Children.OrderByDescending(x => x.Value<DateTime>("PublicationDate")).ToList();
   ```

   * Because we are sorting by a custom property we need to use the generic `Value` method.
4. *Save* the partial view - a confirmation message should appear confirming that the Partial view has been saved.
5. Now view both the Blog overview and the blog posts themselves in the browser to confirm that all is working as expected.

## Summary

Nice job! In this lesson, you've learned what a **Document Type** is and how to add a new Property to it. You've also learned how to change Templates and sort by custom Properties.

[Back to Lessons](/umbraco-cms/13.latest/tutorials/starter-kit/lessons.md)


---

# 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/13.latest/tutorials/starter-kit/lessons/2-add-a-blog-post-publication-date/part-3.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.