Quickstart Guide broken at Step 8

[MarkDBlackwell]

The Quickstart Guide seems broken at Step 8. Customize robust theme. The Guide's recommended actions don't change the appearance of the browser, fully as the Guide claims.

The Guide is correct, through the point of code evolution where the browser tab appears as here (including the post title and text).

In particular (in the next step), the Guide says, "We have removed details of the book so that only image is shown" and says the results should be as here. However, in actuality, the post's title and text remain, just as before. (Other test alterations I tried to the new, overriding file bookshelf/layouts/_default/li.html did appear in the browser.)

To a Hugo novice, this seems mysterious.

Of course, this brokenness might lessen Hugo's uptake of new users. (It frustrates them at a critical, early moment: when they're following the Quickstart Guide.)

I speculate this breakage may be from:

1. Changes in the Hugo executable's functionality; or
2. Changes in the theme, hugo_theme_robust.

This kind of problem IMO would seem to diminish if somehow the spf13/hugo repository itself were to version control some Hugo theme for the Quickstart Guide to use (just as it version controls the guide itself). This isn't true already (supposedly).

Seemingly, another solution would lie in changing the Quickstart guide so that it specifies checking out the above theme from a particular commit known to work (rather than from its latest commit—assuming the theme is the problem.) For example:

    $ git clone https://github.com/dim0627/hugo_theme_robust.git
    $ cd hugo_theme_robust
    $ git checkout b8ce466

That approach might be explainable to new users.

As to my Hugo version, I built Hugo from pull request commit 689e7e19e56ae5bd0e50de1fdddaffaad4299013 forked at d7f364c (but IMO that seems unlikely to have caused the problem).

$ hugo version
Hugo Static Site Generator v0.17-DEV BuildDate: 2016-08-03T14:45:33-04:00

OS: Windows XP, Git for Windows

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.