Hugo: Quick Start final step yields empty site

[freelon]

When following the Quick Start guide one creates a single content site that is marked as draft. While the guide says to start the server including drafts (-D option) this is not the case for the last step, which just says to run "hugo" to get the site generated. So one is left with basically an empty site and no hint where the post is gone to.

I think it would be good to tell users to either use -D as well or to remove the draft status from the post (or maybe give a warning or info when compiling that states which files are omitted because of the draft state).

[julia-r]

I followed the Quick Start Guide as well and also get an empty page as an result.
But changing the draft status does not fix it. Also I get this warning:
found no layout file for "HTML" for "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

I think it would be a better end of the Quick Start Guide to be able to actually see a page. Because right now I am just confused and don't know how to go on.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[raluca-san]

I have run in the same issues. Any solution @julia-r and @freelon ?

[freelon]

I haven't used the quick start since then - the -D option didn't help? Did you get any errors/warnings?

[raluca-san]

No errors and no warnings. the -D option didn't help. I am still getting a blank website.

[freelon]

I just reran the quickstart and have no problem with the output. The test server and also the build is working fine. I'm using version 0.60.1 /extended linux/amd64

[julia-r]

It worked for me with a newer version (v0.59.1) and a fairly up to date theme ("indigo").

[bus710]

Hi, I also ran to the same issue...

1. The output of getting started doc is fine.
2. Then I commit to keep that work and move to other computers
3. clone and try "hugo server -D" => blank page with below warning.

bus710@aw17:automation$ hugo server -D
Building sites … WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "page": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "page": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "taxonomyTerm": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/03/02 09:29:02 found no layout file for "HTML" for kind "taxonomyTerm": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

Update

I eventually refreshed the theme with git commands and it is working now:

$ cd ${BLOG_ROOT}
$ git rm -r themes/hugo-coder
$ git submodule add \
        https://github.com/luizdepra/hugo-coder.git \
        themes/hugo-coder

[emmaguy]

I ran into this too and found that the issue was that I missed this step in the quickstart guide:

Then, add the theme to the site configuration:
echo 'theme = "ananke"' >> config.toml

I skimmed past it because I thought it wasn't relevant - from the layout of the guide, it looked like it was under the 'for non-git users' section. I think this could be clearer, tbh.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.