You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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:
One of your team members creates an account on GitBook.com
You create a space and synchronize it with this repository (it'll work even before merging this PR)
You can customize the look and feel of the content
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.
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
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! 馃
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
masterIf you are interested, the next steps are:
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
Typelabel for the PR