Skip to content
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

Migrate to new version of Gitbook? #187

Open
Frijol opened this issue May 22, 2018 · 2 comments
Open

Migrate to new version of Gitbook? #187

Frijol opened this issue May 22, 2018 · 2 comments

Comments

@Frijol
Copy link
Member

Frijol commented May 22, 2018

Gitbook upgraded. Need to investigate differences/implications but probably will migrate to new version.

Research to do:
https://docs.gitbook.com/what-is-new/important-differences
https://docs.gitbook.com/what-is-new/feature-highlights

@Frijol
Copy link
Member Author

Frijol commented Jun 11, 2018

Playing around with the new version on my personal repos. First impressions:

  • Much faster updates after push
  • Doesn't feel like a build tool– can no longer access logs from deploy to debug
  • So user-friendly oriented that it's hard to dig into anything. Run into shiny surface
  • Does continue to produce offline/book versions of content
  • Some weirdness with autogeneration of summary/titling of pages. Hard to specify with granularity because it's all done for you– so if you titled it something different from the file name, the title is removed in favor of the autogen file name. A folder got nested under one of its peer-level files rather than as itself.
  • Not syncing to local very well if you edit online– changed a filename and it didn't reflect when I pulled it down
  • There's a "was this page helpful" embedded at the bottom of each page– pretty strong assumption that this is docs, Gitbook! I don't get a setting to get rid of this? (I mean, I know it's docs in this case, but it's not on the personal repo where I'm testing it)

@Frijol
Copy link
Member Author

Frijol commented Jun 11, 2018

Overall I'm not really into it, but I'm not sure if they're going to keep supporting "legacy" and the new stuff is not outright offensive.

Much more of a corporation look than before, this kind of messaging:

screen shot 2018-06-11 at 9 13 28 am

My current inclination is to not change yet (key issue is making sure the github integration still works well with local, minor issue is making sure the autogenerated summary will serve us well) – let it settle out a little longer.

If interested in switching sooner, this is probably also fine, should just take some time to check over the new version and make sure there's nothing egregious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant