-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Update Gitbook version #1891
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Gitbook version #1891
Conversation
OK, that was simple. It's a little bit wonky, but it works and now also provides a nice Github-style hover link for each heading in the document. Makes finding those anchors even easier. |
FYI, when I wrote the FAQ, I manually inserted anchor tags into the Markdown contents to give shorter hash links, since the auto-generated links for each heading are slugified version of the entire heading text (and those read horribly). The TOC at the top of the FAQ then links to to those short-hash-tag anchors. |
Highly scientific Twitter poll: https://twitter.com/timdorr/status/763918833987923969 |
Updated and republished! |
Hey, @timdorr . I'm having trouble getting the docs to build properly atm, even off master. It's only finding the README, none of the rest of the pages. Tried clearing out Any ideas? |
Does |
Seems to run cleanly, no errors. Output:
When you say "symlink", do you mean actual symlink, like filesystem-level? What I've got for SUMMARY.md is a text file with the content The generated HTML currently has the main README content in the right pane, and the TOC in the left pane only has "1.1 Introduction" listed. Did the recent changes add some *nix-only config so that it can't be built on Windows any more? |
Went down this rabbit hole because I was sick of the
graceful-fs
warnings on Node 6. So, this fixes that.Retained everything from the original Gitbook theme, as far as I can tell. The only thing missing is the read-tracking checkmarks, but honestly I didn't find much value in them. Maybe others do, though? I can look into a replacement if it's a big deal.
Also, I'm going to go check into #1865 so the next build works for hash links.