# Dedicated page summary instead of "more" trickery

**URL:** https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505
**Category:** Feature requests
**Created:** [October 5, 2022, 9:11pm UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505 "2022-10-05T21:11:01Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![glhrmv](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/glhrmv/32/839_2.png) [@glhrmv](https://zola.discourse.group/u/glhrmv)
#### Post date: [October 5, 2022, 9:11pm UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/1 "2022-10-05T21:11:01Z")

</div>

Common in online publications is to have a short sentence or thesis conveyed in the article listing so as to draw attention to the main arguments presented in each, enticing the reader to click.

This is not currently possible with Zola out of the box, as the only way to achieve this “external summary” is through the use of the HTML tag directly in the text. That is to say, the summary that is presented in the listing is always going to be a fraction of the text itself.

Ideally, one should be able to override the `summary` property of a page and directly insert this summary in the frontmatter. An alternative approach might be custom markup in the text itself which allows the writer to designate what this summary should be, and have it omitted from the `content` of the page.

In any case, is this an idea worth exploring? Thanks

---

<div class="post-metadata">

### Author: ![dustinknopoff](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@dustinknopoff](https://zola.discourse.group/u/dustinknopoff)
#### Post date: [October 6, 2022, 7:08am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/2 "2022-10-06T07:08:12Z")

</div>

For my purposes, {{page.content | truncate | safe}} has been sufficient

---

<div class="post-metadata">

### Author: ![glhrmv](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/glhrmv/32/839_2.png) [@glhrmv](https://zola.discourse.group/u/glhrmv)
#### Post date: [October 6, 2022, 10:59am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/3 "2022-10-06T10:59:46Z")

</div>

Not sure what you mean, exactly.

However, I since found that each page has a “description” property, which suits my needs perfectly. Consider this request closed.

---

<div class="post-metadata">

### Author: ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)
#### Post date: [October 6, 2022, 8:29pm UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/4 "2022-10-06T20:29:11Z")

</div>

> [@glhrmv](#):
>
> Ideally, one should be able to override the `summary` property of a page and directly insert this summary in the frontmatter.

You can write whatever you want in the `extra` section and use that rather than the summary.

---

<div class="post-metadata">

### Author: ![glhrmv](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/glhrmv/32/839_2.png) [@glhrmv](https://zola.discourse.group/u/glhrmv)
#### Post date: [October 7, 2022, 2:59pm UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/5 "2022-10-07T14:59:44Z")

</div>

I overlooked that completely. My bad.

I went go with the “description” property instead. It doesn’t seem to be used for metadata, which actually prompts another question: how can I ensure my pages have metadata that is crawler-friendly for previews in apps like Instagram or Telegram?

---

<div class="post-metadata">

### Author: ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)
#### Post date: [October 7, 2022, 4:41pm UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/6 "2022-10-07T16:41:38Z")

</div>

> [@glhrmv](#):
>
> how can I ensure my pages have metadata that is crawler-friendly for previews in apps like Instagram or Telegram?

Up to your templates to be written correctly according to their docs.

---

<div class="post-metadata">

### Author: ![jack999](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jack999](https://zola.discourse.group/u/jack999)
#### Post date: [October 8, 2022, 7:45am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/7 "2022-10-08T07:45:49Z")

</div>

I ran into a related issue in the blog I am porting, and it is what I dislike most about zola. I want to format all that appears above `<!-- more -->` i.e. the summary differently on the blog page than the rest of the text. Doable, can put it in the `extra` section or what I did, wrapping it in a short code. Not elegant.

I tried to solve it with

```auto
{{ page.content | replace(from=page.summary, to="") }}

```

and that does not work (even if it should work if I understand Tera correctly)

besides that and a few small issues, I think Zola is wonderful.

best, j

---

<div class="post-metadata">

### Author: ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)
#### Post date: [October 9, 2022, 7:27am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/8 "2022-10-09T07:27:11Z")

</div>

The summary is mostly intended if you want an excerpt from the text for other pages. If you want to style it differently, using a shortcode is probably better.

---

<div class="post-metadata">

### Author: ![jack999](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jack999](https://zola.discourse.group/u/jack999)
#### Post date: [October 9, 2022, 8:44am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/9 "2022-10-09T08:44:09Z")

</div>

Yes, so have summary on the main index page. On the site I am porting from Jekyll, it had its equivalent to

```auto
{{ page.content | replace(from=page.summary, to="") }}

```

which was very useful, as one can choose to omit the summary from the blog page, or format it differently. (and this should work in Tera, I think but it doesn’t ?)

I havent checked if I can do same (omit summary) with shortcodes.

but what bugs me is that by either using extra section or shortcodes, one is introducing zola specific code into the blog md files.

related is blockquotes. I wish I did not have to use shortcode instead of just \>, and wish I could somehow tell Zola to map \> to a shortcode

These are the only issue that I have not been able to do properly in zola. everything else has been a dream. and these are minor. Thanks for such a wonderful ssg.

---

<div class="post-metadata">

### Author: ![jieiku](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/jieiku/32/741_2.png) [@jieiku](https://zola.discourse.group/u/jieiku)
#### Post date: [October 11, 2022, 1:29am UTC](https://zola.discourse.group/t/dedicated-page-summary-instead-of-more-trickery/1505/10 "2022-10-11T01:29:52Z")

</div>

In the abridge theme I try to cover all possibilities for a summary:

```auto
        {%- if page.summary %}
          {{ page.summary | markdown(inline=true) | safe }}
        {%- elif page.description %}
          {{ page.description | safe }}
        {%- elif page.content %}
          {{ page.content | striptags | truncate(length=150) | safe }}
        {%- endif %}

```
