hugo/docs/content/extras/aliases.md at 8557e2cbb821663a5a482d904b031dff831b06cc

blogs/hugo

mirror of https://github.com/gohugoio/hugo.git synced 2026-09-02 11:42:37 +00:00

Files

T

Anthony Fok ba44e860a3 [Docs] Copyediting

* Add meta author, description and generator tags
 * Add Hugo version beside the logo and in the footer
 * Suggest the user to run `go get -u -v` to update dependencies
 * Requires Go 1.3+ rather than Go 1.1+
 * Improve rendering/formatting in some places
 * Add trailing slash to URLs where appropriate
 * GitHub redirects all http requests to https, update accordingly

2015-01-28 18:02:40 -07:00

1.2 KiB

Raw Blame History

aliases, date, menu, next, prev, title, weight

aliases

date

title

weight

/doc/redirects/

/doc/alias/

/doc/aliases/

2013-07-09

main

parent
extras

/extras/builders

/taxonomies/ordering

Aliases

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

TOML	YAML
`+++ 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

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.
Aliases are rendered prior to any content and will be overwritten by any content with the same location.

1.2 KiB Raw Blame History

Example

Important Behaviors

1.2 KiB

Raw Blame History