Transition to GitBook.com

[SamyPesse]

Summary

Hello 👋 I'm the founder and CEO of GitBook. I've noticed that this repository is still using the deprecated GitBook CLI. I wanted to show you a quick demo of what it could look like using the free version of GitBook.com.

👉 You can see a demo published at https://samypesse.gitbook.io/commercetools-demo/ It took me 2min to get it live.

• Much better search
• Improved layout (and we have a bunch of great improvements coming soon)
• Automatically updated when a commit is pushed to master
• Preview for PRs with a unique link to see the content

If you are interested, the next steps are:

1. One of your team members creates an account on GitBook.com
2. You create a space and synchronize it with this repository (it'll work even before merging this PR)
3. You can customize the look and feel of the content
4. You click "Publish" to get it online :)

Happy to jump on a quick call to demo GitBook and help you go through these steps.

Description

This PR slightly simplifies the configuration to work with the new GitBook. It's not needed to make it work with GitBook.com, but it'll simplify the repository setup.

Todo

• Tests
  • [x] Unit
  • [x] Integration
  • [x] Acceptance
• [x] Documentation
• [ ] Type label for the PR

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 431881bbd85f7050d5a0fd3142aaba2b3f124701

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[emmenko]

Hi @SamyPesse ,

apologies for the late reply and many thanks for looking into it and offering your contribution!

We actually have our own company docs kit that we generally use for documentation and it might be that we will migrate these docs to that at some point. We'll discuss internally how to proceed.

In any case, thanks again for offering your help! 🤗