github/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-12-02 00:32:04 -05:00
Code Issues Projects Releases Packages Wiki Activity
hugo/docs/content/extras/aliases.md
Anthony Fok b59dd163ec [Docs] More copyediting 
* Add link to https://travis-ci.org/spf13/hugo
* Correct heading levels in docs/content/community/mailing-list.md
* Mention RFC 3339 as the `date` format set by `hugo new`
* Mention that `hugo new` does not add `draft = true` when the user
  provides an archetype
* List short examples of TOML and YAML side by side
* Compact the Math template functions into a table
* Put some notes into a blockquote
2015-01-17 00:45:53 -07:00

1.1 KiB
Raw Blame History

aliases date menu next prev title weight
/doc/redirects/
/doc/alias/
/doc/aliases/
2013-07-09
main
parent
extras
/extras/builders /taxonomies/ordering Aliases 10

For people migrating existing published content to Hugo, there's a good chance you need a mechanism to handle redirecting old URLs.

Luckily, this can be handled easily with aliases in Hugo.

Example

content/posts/my-awesome-blog-post.md

TOMLYAML 
---
aliases:
    - /posts/my-original-url/
    - /2010/even-earlier-url.html
---

+++
aliases = [
    "/posts/my-original-url/",
    "/2010/even-earlier-url.html"
]
+++

Now when you go to any of the aliases locations, they will redirect to the page.

Important Behaviors

  1. Hugo makes no assumptions about aliases. They also don't change based on your UglyUrls setting. You need to provide absolute path to your webroot and the complete filename or directory.

  2. Aliases are rendered prior to any content and will be overwritten by any content with the same location.