faq.md (3540B)
1 ---
2 title: Frequently Asked Questions
3 linktitle: FAQ
4 description: Solutions to some common Hugo problems.
5 date: 2018-02-10
6 categories: [troubleshooting]
7 menu:
8 docs:
9 parent: "troubleshooting"
10 keywords: [faqs]
11 weight: 2
12 toc: true
13 aliases: [/faq/]
14 ---
15
16 {{% note %}}
17 **Note:** The answers/solutions presented below are short, and may not be enough to solve your problem. Visit [Hugo Discourse](https://discourse.gohugo.io/) and use the search. It that does not help, start a new topic and ask your questions.
18 {{% /note %}}
19
20 ## I can't see my content!
21
22 Is your markdown file [in draft mode](https://gohugo.io/content-management/front-matter/#front-matter-variables)? When testing, run `hugo server` with the `-D` or `--buildDrafts` [switch](https://gohugo.io/getting-started/usage/#draft-future-and-expired-content).
23
24 ## Can I set configuration variables via OS environment?
25
26 Yes you can! See [Configure with Environment Variables](/getting-started/configuration/#configure-with-environment-variables).
27
28 ## How do I schedule posts?
29
30 1. Set `publishDate` in the page [Front Matter](/content-management/front-matter/) to a datetime in the future. If you want the creation and publication datetime to be the same, it's also sufficient to only set `date`[^date-hierarchy].
31 2. Build and publish at intervals.
32
33 How to automate the "publish at intervals" part depends on your situation:
34
35 * If you deploy from your own PC/server, you can automate with [Cron](https://en.wikipedia.org/wiki/Cron) or similar.
36 * If your site is hosted on a service similar to [Netlify](https://www.netlify.com/) you can use a service such as [ifttt](https://ifttt.com/date_and_time) to schedule the updates.
37
38 Also see this Twitter thread:
39
40 {{< tweet user="ChrisShort" id="962380712027590657" >}}
41
42 [^date-hierarchy]: See [Configure Dates](https://gohugo.io/getting-started/configuration/#configure-dates) for the order in which the different date variables are complemented by each other when not explicitly set.
43
44 ## Can I use the latest Hugo version on Netlify?
45
46 Yes you can! Read [this](/hosting-and-deployment/hosting-on-netlify/#configure-hugo-version-in-netlify).
47
48 ## I get "... this feature is not available in your current Hugo version"
49
50 If you process `SCSS` or `SASS` to `CSS` in your Hugo project with `libsass` as the transpiler or if you convert images to the `webp` format, you need the Hugo `extended` version, or else you may see an error message similar to the below:
51
52 ```bash
53 error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
54 ```
55
56 We release two set of binaries for technical reasons. The extended version is not what you get by default for some installation methods. On the [release page](https://github.com/gohugoio/hugo/releases), look for archives with `extended` in the name. To build `hugo-extended`, use `go install --tags extended`
57
58 To confirm, run `hugo version` and look for the word `extended`.
59
60 ## Do I need to install Git to create, deploy, and maintain a website with Hugo?
61
62 >Technically, no.
63 >
64 >Practically, yes.
65
66 * The primary installation method documented by most (perhaps all) themes is via Git or the Hugo Modules feature.
67 * The Hugo Modules feature requires Go, and Go “gets” with Git.
68 * A Git repository is required by CI/CD hosting (Bitbucket, Cloudflare, GitHub Pages, GitLab Pages, Netlify, et. al.).
69 * The canonical “last modified” date for content is its Git committer date; using anything else is error-prone.