Github book

[pricelessbrewing]

Link to github book doesn't work, looks like github book has changed versions and it links to the legacy version.

When I create an account and login, I don't see the brewtarget book at all.

Any particular reason github book is being used in the first place? Perhaps switch to github pages?

[malavv]

Gitbook is a great choice for book editing.

It has offline editing with a WYSIWYG, versioning, simplified management of collaboration, and localization. It's easy to see why this team is growing fast.

Github Pages is making exactly that, a webpage. You could implement a build system managing the book pages with hooks, but this is just a crude and prone to break way of getting to the same results (it's what we had before)

Now, I must say, it's been a while since the last time I went and looked at the manual. As you pointed out, everything seems broken since their move to the latest version. I applied their "automatic" conversion tool, but the results seems far from satisfactory.

Gitbook's flow used to be the same as Github, where you fork a book, edit it, and push a change request. Looking at their new UI, I'm not sure this is still the case. It looks like you need to be part of an organization, and have been added as a writer.

I'll take a look at it tonight, and try to fix this. I'll send you an invitation to be a writer after that. Then, we can discuss about what might be the process where we make someone a writer.

You can find Brewtarget's (currently broken) User Manual here.

[malavv]

Alright so after looking into this, here is my summary.

I suggest we keep using the legacy version of the Gitbook tool. From a practical perspective, it only means changing the URL to the following:

• [en] https://brewtarget.gitbooks.io/user-manual/content/en/
• [fr] https://brewtarget.gitbooks.io/user-manual/content/fr/

I do not believe changing version is imperative, as their documentation seem to indicate the change is very optional at the moment. While offering nearly nothing new, the new version of Gitbook looses (for the moment) the following features (as they are not yet implemented)

• Localization
• Exporting to PDF
• Having a desktop WYSIWYG editor

If anyone wants to edit the book, the process is still the same.

1. Going to Github and forking the manual.
2. Edit the book
   1. Either manually using traditional Markdown editors
   2. Or using the legacy editor by signin in to legacy.gitbook.com and creating a personal book linked with this Github content.
3. Make a normal pull request on Github for your changes to be merged.

[GBayliss]

This is still broken on http://www.brewtarget.org/

Can't say that I could figure out what was happening with gitbook, it tried to get me to create and organization and all sorts of nonsense only to find that the brewtarget information is nowhere to be found. Does anyone have rights to update the website and point users to the latest builds and documentation instead of going round in circles?

[mikfire]

I will see if I was ever granted that level of access. Otherwise, I will try if I can find @rocketman768 and ask him to either grant me access or put in a redirect or something.

[malavv]

I'm the one to blame. When Gitbook was created the writing experience and free tier for communities were out of this world, especially with regards to Localization. Shortly after their commercial and community offering changed drastically, and the initial format was no longer supported requiring a good rewrite. Let me take a look and help resolve this. (Plus Mikfire, I'll make sure I give you access to everything)

…

On Mon, 14 Nov 2022 at 13:54, mikfire ***@***.***> wrote: I will see if I was ever granted that level of access. Otherwise, I will try if I can find @rocketman768 <https://github.com/rocketman768> and ask him to either grant me access or put in a redirect or something. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFMMQCW4Y7TMA3SDX4VT3LWIKDERANCNFSM4FPMY5UA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>