GitBook's own version control: yay or nay?

[contraexemplo]

I merged the new organization again and GitBook didn't render it right again (don't worry, I reverted the merge!). So I have a new idea:

GitBook offers the following feature:

• We can sync as many branches as we want from GitHub
• We are also able to transform them into versions (doc version 1.0.0, etc) publicly accessible to anyone or delete a whole deprecated version easily

My meta GitBook showcases this. I set up the open-collectivebranch (https://github.com/contraexemplo/metadocumentation/tree/open-collective) as the main docs/most current documentation and there's a link to the redirect branch (https://github.com/contraexemplo/metadocumentation/tree/redirect) with the old version of said documentation. We could do the same for the new organization while keeping the old version live as well.

[contraexemplo]

cc: @jaskirat2000 and @alanna

[contraexemplo]

Follow up after the meeting I had with @alanna: I will try this tomorrow and see how it goes. We agreed that we are at a point of the project that moving on to other tasks will be more beneficial to the docs. We also agreed that talking to the developers about developing a strategy to document new versions of the app is much needed—and if we choose to stick with GitBook in the end, this feature may be handy.

Tasks for tomorrow:

• Check the Releases functionality page again to identify the best strategy for our documentation
• Perform some tests on my test GitBook
• Stage changes through GitBook
• Evaluation: did it work as expected?
• Write a blog post about all of this!

[contraexemplo]

@alanna I was able to successfully import and render the new organization using the Release functionality: https://docs.opencollective.com/help/v/v2/

[alanna]

Great! It looks good. So is the plan to continue editing the V2 release and then migrate it to be the main docs by the end of the project?

[contraexemplo]

@alanna Yes, we would mark it as the main branch and it would take the place from the current documentation.

[contraexemplo]

v2 is now the default docs for everyone on GitBook but I need to make a change here to make that branch the main one here. @alanna I don't have the access permissions to do this, would you be able to make that change?

[alanna]

I'm not sure how to do that, @contraexemplo - I think I succeeded in making you an admin of this repo just now so can you try again? If you need me to do it let me know how.

[contraexemplo]

Thanks @alanna! v2 is now the main branch on GitBook and GitHub. 🎉

[alanna]

@contraexemplo can you change "V2" to something more descriptive like "help" or "docs" so it shows up here?