---
title: "Partial Templates"
date: "2013-07-01"
weight: 80
menu:
main:
parent: 'layout'
aliases: ["/layout/chrome/"]
prev: "/templates/views"
next: "/templates/rss"
---
It's not a requirement to have this, but in practice it's very
convenient to split out common template portions into a partial template
that can be included anywhere. As you create the rest of your templates
you will include templates from the /layout/partials directory. Hugo
doesn't know anything about partials, it's simply a convention that you
may likely find beneficial.
I've found it helpful to include a header and footer template in
partials so I can include those in all the full page layouts. There is
nothing special about header.html and footer.html other than they seem
like good names to use for inclusion in your other templates.
▾ layouts/
▾ partials/
header.html
footer.html
By ensuring that we only reference [variables](/layout/variables/)
used for both nodes and pages we can use the same partials for both.
## example header.html
This header template is used for [spf13.com](http://spf13.com).
{{ template "partials/meta.html" . }}
{{ .Title }} : spf13.com
{{ if .RSSlink }}{{ end }}
{{ template "partials/head_includes.html" . }}
## example footer.html
This header template is used for [spf13.com](http://spf13.com).
**For examples of referencing these templates, see [single content
templates](/templates/content), [list templates](/templates/list) and [homepage templates](/templates/homepage)**