From 0b4c1af04b01cd03d453b7bb59dfd0b845d210a0 Mon Sep 17 00:00:00 2001 From: digitalcraftsman Date: Fri, 7 Apr 2017 19:31:12 +0200 Subject: [PATCH] Add some improvements to getting-started/usage.md - use HTTPS links when possible - correct/add link to deployment section - add data/ as watched folder See PR rdwatters/hugo-docs-concept#72 --- content/getting-started/usage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/getting-started/usage.md b/content/getting-started/usage.md index 4dbddc0c1..97ec8c739 100644 --- a/content/getting-started/usage.md +++ b/content/getting-started/usage.md @@ -151,6 +151,7 @@ This will run a fully functioning web server while simultaneously watching your * `/static/*` * `/content/*` * `/data/*` +* `/i18n/*` * `/layouts/*` * `/themes//*` * `config` @@ -193,7 +194,7 @@ disableLiveReload: true After running `hugo server` for local web development, you need to do a final `hugo` run *without the `server` part of the command* to rebuild your site. You may then deploy your site by copying the `public/` directory to your production web server. -Since Hugo generates a static website, your site can be hosted *anywhere* using any web server. See [Hosting and Deployments][] for methods for hosting and automating deployments contributed by the Hugo community. +Since Hugo generates a static website, your site can be hosted *anywhere* using any web server. See [Hosting and Deployment][hosting] for methods for hosting and automating deployments contributed by the Hugo community. {{% warning "Generated Files are **NOT** Removed on Site Build" %}} Running `hugo` *does not* remove generated files before building. This means that you should delete your `public/` directory (or the publish directory you specified via flag or configuration file) before running the `hugo` command. If you do not remove these files, you run the risk of the wrong files (e.g., drafts or future posts) being left in the generated site. @@ -236,10 +237,9 @@ Note the `bind` option, which is the interface to which the server will bind (de By using Hugo's server in production, you are able to deploy just the source files. Hugo, running on your server, will generate the resulting website on the fly and serve them at the same time. - [commands]: /commands/ [config]: /getting-started/configuration/ [dirs]: /getting-started/directory-structure/ [front matter]: /content-management/front-matter/ -[hosting]: /hosting-and-deployments/ +[hosting]: /hosting-and-deployment/ [install]: /getting-started/installing/ \ No newline at end of file