content: Differentiate content view templates from other templates

This commit is contained in:
Joe Mooring 2025-07-22 13:07:47 -07:00 committed by GitHub
parent 978770fc8d
commit 172bfbc4b4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -38,7 +38,8 @@ layouts/
│ ├── page.html
│ └── section.html
├── films/
│ ├── card.html <-- content view
│ ├── view_card.html <-- content view
│ ├── view_li.html <-- content view
│ ├── page.html
│ └── section.html
├── baseof.html
@ -325,19 +326,21 @@ For example, Hugo applies a _base_ template to the _home_ template below, then r
{{ .Content }}
<ul>
{{ range where site.RegularPages "Section" "films" }}
{{ .Render "card" }}
{{ .Render "view_card" }}
{{ end }}
</ul>
{{ end }}
```
```go-html-template {file="layouts/films/card.html"}
```go-html-template {file="layouts/films/view_card.html"}
<div class="card">
<h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
{{ .Summary }}
</div>
```
In the example above, the content view template's name starts with `view_`. While not strictly required, this naming convention helps distinguish content view templates from other templates within the same directory, improving organization and clarity.
## Render hook
A _render hook_ template overrides the conversion of Markdown to HTML.