breaking styles after change default theme

[ava57r]

After change
f01bf88
f01bf88#diff-9f0d373829e789d9a6923dd290c5b174L21

Missing button icons published on github.com version of the book

Book is here:
https://rurust.github.io/rust-by-example-ru/index.html

[mattico]

The problem is that rust-by-example's theme/index.hbs hasn't been updated for the latest mdbook changes. I think it would work with 0.1.5 or earlier. The changes I'd suggest:

• Update RBE to newest mdbook version
• Change RBE readme instructions to install specific mdbook version

[cauebs]

I've been having this problem as well. What really bugged me was that locally it works fine, but when I push it to Github pages the icons all disappear. I just noticed it's not only me: https://rust-lang-nursery.github.io/edition-guide/

[mattico]

@cauebs interesting. I believe the Rust by Example issue is related to the custom theme's index.hbs not being updated for the new mdbook version, but the edition guide doesn't use any custom themeing. Does your book? Perhaps there's some other issue at play.

Downloading a complete copy of the edition from the github pages site, the _FontAwesome directory is completely missing. I assume that, since it works locally, this is a problem related to pages?

[mattico]

Ah, okay: https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/

By default, Jekyll does not build any files or directories that

• are hidden or used for backup (indicated by names that start with . or #, or that end with ~);
• contain site content (indicated by names that start with _); or
• are excluded in the site configuration.

To me this doesn't indicate that the not-built files won't end up on the target site, but that is actually the case: https://stackoverflow.com/questions/6397780

I verified this by making a github pages site and renaming the _FontAwesome directory to FontAwesome.

You can work around this at the moment by adding a .nojekyll file to your built book's root. Since mdBook is often used for github pages, we should add a workaround for this.