> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/broadcast-v4/blog-posts/article-page.md).

# Article page

Configure your blog post pages

To customize your blog posts (also known as article pages), click on the ***Article page*** when on any blog post page.

You can also access article pages from the 'Default blog post' template in the top drop-down menu:

![](https://content.gitbook.com/content/Rsx9yqijvDkkcmGBKHkk/blobs/Odaq8hKmnjXRLq5CgL9v/Aug-20-2021%2020-07-32.gif)

### Hero image options

Broadcast includes controls to position your featured image and select an image height that works best for all your blog posts.

The hero image is derived from your blog post featured image:

![Shopify Admin - Blog posts](https://content.gitbook.com/content/Rsx9yqijvDkkcmGBKHkk/blobs/t7ZMTjSrbryldocwc5g8/Screen%20Shot%202021-08-20%20at%208.19.05%20PM.png)

### Article toggles

Enable or disable elements of your blog posts:

* Show date (appear below title)
* Show author (appear below title)
* Show article tags (appear after the article)
* Show social sharing buttons (appear on the side of each article)
* Show navigation arrows (appear after the article and below tags)


---

# 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://broadcast.presidiocreative.com/broadcast-v4/blog-posts/article-page.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.