> For the complete documentation index, see [llms.txt](https://docs.ektothemes.com/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ektothemes.com/guides/sense/customization/homepage/publish-date.md).

# Publish date

The **Publish date** option allows you to control the visibility of the post date displayed on post cards.

This applies to all areas where post cards are shown, including:

* Homepage
* Tag pages
* Author pages
* Related posts

Follow the steps below to access the publish date setting:

{% stepper %}
{% step %}

### Access Ghost Admin

* Log in to your Ghost Admin at `yoursite.com/ghost`
  {% endstep %}

{% step %}

### Navigate to Design Settings

* Go to **Settings** > **Site** > **Design & branding** `yoursite.com/ghost/#/settings/design`
* Click the **"Customize"** button to open the theme editor.
  {% endstep %}

{% step %}

### Open Theme Settings

* Locate the **"Show publish date"** option under the **Homepage** section.
  {% endstep %}
  {% endstepper %}

Toggle this option to enable or hide the publish date on post cards.


---

# 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://docs.ektothemes.com/guides/sense/customization/homepage/publish-date.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.