Skip to content

Commit 0b41c3b

Browse files
Steve Ashbygitbook-bot
Steve Ashby
authored andcommitted
GITBOOK-541: Small tweaks to import page
1 parent 38e45e0 commit 0b41c3b

File tree

1 file changed

+20
-14
lines changed

1 file changed

+20
-14
lines changed

getting-started/import.md

Lines changed: 20 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ description: >-
77

88
# Importing content
99

10-
You can migrate and unify existing documentation in GitBook using the import tool. You have the option to import single or multiple pages — or an entire Git repository.
10+
You can migrate and unify existing documentation in GitBook using the import tool. 
11+
12+
You have the option to import single or multiple pages using our built-in import tool — or [an entire Git repository using Git Sync](import.md#import-using-git-sync).
1113

1214
## Using the Import Panel
1315

@@ -34,8 +36,6 @@ If you want to **import multiple pages**, you can upload a ZIP file containing H
3436
GitBook is Markdown-based, so importing content in Markdown format will yield the best results. If your current tools support exporting in Markdown, we recommend using that format for a smoother import process.
3537
{% endhint %}
3638

37-
38-
3939
### The Import panel
4040

4141
<figure><img src="../.gitbook/assets/10_01_25_import_modal.svg" alt=""><figcaption><p>The import panel in GitBook.</p></figcaption></figure>
@@ -57,36 +57,42 @@ GitBook currently has the following limits for imported content:
5757
* The maximum number of pages that can be uploaded in a single import is **20**.
5858
* The maximum number of files (images etc.) that can be uploaded in a single import is **20**.
5959

60+
***
6061

62+
## Import using Git Sync
6163

62-
## Importing using Git Sync
64+
For importing large volumes of content into GitBook, we recommend using [Git Sync](git-sync/). Unlike our integrated import tool, Git Sync is better suited for handling larger migrations efficiently.
6365

64-
For importing large volumes of content into GitBook, we recommend using Git Sync. Unlike our default import tool, Git Sync is better suited for handling larger migrations efficiently.
66+
{% hint style="info" %}
67+
You’ll find the essential steps to import your content below. For more detailed steps and a video demo, head over to our dedicated guide to [importing content into GitBook using Git Sync](https://app.gitbook.com/s/LBGJKQic7BQYBXmVSjy0/product-guides/import-or-migrate-your-content-to-gitbook-with-git-sync).
68+
{% endhint %}
6569

66-
Here are the steps:
70+
Here’s how to do it:
6771

6872
{% stepper %}
6973
{% step %}
70-
### Get your content into markdown
74+
### Convert your content into Markdown
75+
76+
GitBook is Markdown-based, so importing content in Markdown format will yield the best results. If your current tools support exporting in Markdown, we recommend using that format for a smoother import process.
7177

72-
If your content isn't already in markdown files, we recommend using some scripting or online tools to translate the content.
78+
If your content isnt already in Markdown files, we recommend using a script or an online tool to convert your content.
7379
{% endstep %}
7480

7581
{% step %}
76-
### Organise your content in GitHub or Gitlab
82+
### Organize your content in GitHub or GitLab
7783

78-
When setting up your GitBook site, it's crucial to organize your content in git efficiently. Since git sync occurs at the space level, carefully plan how to group content. Create multiple repositories or folders, ensuring the necessary markdown files are in the correct locations.
84+
When setting up your GitBook site, its crucial to organize your content in your GitHub or GitLab repository efficiently. Since Git Sync occurs at the space level, carefully plan how to group your content. Create multiple repositories or folders, ensuring the necessary Markdown files are in the correct locations.
7985
{% endstep %}
8086

8187
{% step %}
82-
### Set up spaces and git sync
88+
### Set up spaces and Git Sync
8389

84-
To organize your content, create one or more spaces in GitBook as needed. Install Git sync on these spaces and configure it to synchronize with the appropriate folder or repository set up in step 2.&#x20;
90+
To organize your content, create one or more spaces in GitBook as needed. Install the [GitHub Sync](https://www.gitbook.com/integrations/github-sync) or [GitLab Sync](https://www.gitbook.com/integrations/gitlab-sync) integrations in your organization and configure it for those spaces. You’ll need to synchronize your space with the folder or repository you set up in the previous step.&#x20;
8591
{% endstep %}
8692

8793
{% step %}
88-
### Run git sync with direction GitHub -> GitBook
94+
### Run Git Sync in the direction GitHub GitBook
8995

90-
When finishing the configuration ensure you select the direction of GitHub -> GitBook. Run the sync.
96+
When following the configuration process, make sure you select the direction of GitHub GitBook. This will result in the contents of your folder or repository being pulled from GitHub or GitLab into GitBook.
9197
{% endstep %}
9298
{% endstepper %}

0 commit comments

Comments
 (0)