e425226a28
* extras/permalinks.md added, weighted to third in the extras menu * examples added to layout/go-templates.md, using `.Site.Params` * mention `.Site.Params` in layout/variables.md * update meta/release-notes.md to mention `first` and the permalinks * update overview/configuration.md to use reserved-for-documentation domains and with another example, nudging towards permalinks and site parameters, with three different data-types shown for the latter Signed-off-by: Noah Campbell <noahcampbell@gmail.com>
1.1 KiB
| title | date | aliases | groups | groups_weight | ||
|---|---|---|---|---|---|---|
| Permalinks | 2013-11-18 |
|
|
30 |
By default, content is laid out into the target publishdir (public)
namespace matching its layout within the contentdir hierarchy.
The permalinks site configuration option allows you to adjust this on a
per-section basis.
This will change where the files are written to and will change the page's
internal "canonical" location, such that template references to
.RelPermalink will honour the adjustments made as a result of the mappings
in this option.
For instance, if one of your sections is called post and you want to adjust
the canonical path to be hierarchical based on the year and month, then you
might use:
permalinks:
post: /:year/:month/:title/
Only the content under post/ will be so rewritten.
A file named content/post/sample-entry which contains a line
date: 2013-11-18T19:20:00-05:00 might end up with the rendered page
appearing at public/2013/11/sample-entry/index.html and be reachable via
the URL http://yoursite.example.com/2013/11/sample-entry/.