> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/customize-your-pages/blog-page.md).

# Blog page

The **Blog page** lists the articles of one blog, newest first, and is where visitors land when they click a Blog or Journal link in your menu. It is the entry point to your written content: guides, launches, and brand stories that bring in search traffic and give returning shoppers a reason to come back between orders.

The list itself is filled by Shopify. You create the blog and write the posts in the admin, and the theme decides how the list looks.

<figure><img src="/files/3tOLBt7RvV9ic7TY8SIU" alt=""><figcaption></figcaption></figure>

### Step 1: Create the blog and its posts <a href="#step-1-create-the-blog" id="step-1-create-the-blog"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Shopify admin > Online Store > Blog posts**.
2. Click **Manage blogs**, then **Add blog** if you do not have one yet.
3. Give the blog a title, for example `The Journal`, then click **Save**.
4. Go back to **Blog posts** and click **Add blog post** to write your first article.
   {% endhint %}

*Result:* the blog is reachable at an address such as `/blogs/the-journal`, and every post you publish appears in the list.

### Step 2: Assign the template and style the list <a href="#step-2-assign-the-template" id="step-2-assign-the-template"></a>

{% hint style="success" %}
**Steps:**

1. In **Manage blogs**, open your blog and choose the theme template you want in **Theme template**.
2. Go to **Online Store > Themes > Customize**.
3. Open the template selector and choose **Blogs**, then the blog template you just assigned.
4. Adjust the sections in the left sidebar, then click **Save**.
   {% endhint %}

*Result:* the preview shows the article list with your layout, and every post in that blog uses it.

{% hint style="info" %}
A blog is not linked from anywhere until you add it to a menu. Add it in **Online Store > Navigation** so visitors can find it from the header or the footer.
{% endhint %}

### What is on this page <a href="#what-is-on-this-page" id="what-is-on-this-page"></a>

* [Page template sections](/velare/customize-your-pages/blog-page/page-template-sections.md): the sections this template is built from, and where each one is documented.

### What changes on the storefront <a href="#what-changes" id="what-changes"></a>

* Visitors get a browsable list of articles instead of having to reach each post through a direct link.
* Search engines have a single page to crawl that links to every article, which helps new posts get found.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Blog post page](/velare/customize-your-pages/blog-post-page.md): the layout of a single article opened from this list
* [Breadcrumb](/velare/customize-your-pages/breadcrumb.md): the trail that lets readers step back from an article to this list


---

# 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://uxsmart.gitbook.io/velare/customize-your-pages/blog-page.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.
