-
Notifications
You must be signed in to change notification settings - Fork 39
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
Switch from NodeJS/Gitbook back to Ruby/Jekyll, using latest Ruby #315
Conversation
revert irrelevant commit
merged with conflicts, will be reverted
revert to mention rvm not nvm etc
…0-reverted-222 fix various places where this conflicted with reversion of 222 or caused errors
will fix ruby running shortly
and add it and its sibling to the parent
site_structure needs to supply a path for the cache; include_relative should be used instead of include, without quotes
as done for site
because assign now does a deep recursive size/score count which fails on looped structures; using it causes a stack too deep error
compared with old SUMMARY.md (gitbook way) to make sure things which previously would have had to be added there are added here under at least one parent
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I've tested locally and I can set up jekyll and build following the instructions. Pages seem to be generated correctly and internal links seem to work.
It's a shame that gitbook has moved away from OSS but Jekyll is being actively developed and is currently well supported so this is a sensible move.
This reverts the swtich to Gitbook, as nice as it was, it long ago stopped being nicely supported OSS so simplest thing to do is to go back to Ruby/Jekyll. Unfortunately it has moved on and a lot of things here got broken -- but we think this fixes them all.