The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
ProductPricingLog inSign up
  • Documentation
  • Developers
  • Guides
  • Changelog
  • Help Center
  • Getting Started
    • GitBook Documentation
    • Quickstart
    • Importing content
    • GitHub & GitLab Sync
      • Enabling GitHub Sync
      • Enabling GitLab Sync
      • Content configuration
      • GitHub pull request preview
      • Commit messages & Autolink
      • Monorepos
      • Troubleshooting
  • Creating Content
    • Formatting your content
      • Inline content
      • Markdown
    • Content structure
      • Spaces
      • Pages
      • Collections
    • Blocks
      • Paragraphs
      • Headings
      • Unordered lists
      • Ordered lists
      • Task lists
      • Hints
      • Quotes
      • Code blocks
      • Files
      • Images
      • Embedded URLs
      • Tables
      • Cards
      • Tabs
      • Expandable
      • Stepper
      • Drawings
      • Math & TeX
      • Page links
    • Reusable content
    • Broken links
    • Searching content
      • Search & Quick find
      • GitBook AI
    • Writing with GitBook AI
    • Version control
  • API References
    • OpenAPI
      • Add an OpenAPI specification
      • Insert API reference in your docs
    • Guides
      • Structuring your API reference
      • Adding custom code samples
      • Managing API operations
      • Describing enums
      • Integrating with CI/CD
  • Extensions reference
  • Publishing Documentation
    • Publish a docs site
      • Public publishing
      • Private publishing with share links
    • Site structure
      • Content variants
      • Site sections
    • Site customization
      • Icons, colors, and themes
      • Layout and structure
      • Extra configuration
    • Set a custom domain
    • Setting a custom subdirectory
      • Configuring a subdirectory with Cloudflare
      • Configuring a subdirectory with Vercel
    • Site settings
    • Site insights
    • Site redirects
    • Visitor authentication
      • Enabling visitor authentication
      • Setting up Auth0
      • Setting up Azure AD
      • Setting up AWS Cognito
      • Setting up Okta
      • Setting up OIDC
      • Setting up a custom backend
  • LLM-ready docs
  • Collaboration
    • Live edits
    • Change requests
    • PDF export
    • Inviting your team
    • Comments
    • Notifications
  • Integrations
    • Install and manage integrations
    • GitHub Copilot
  • Account management
    • Plans
      • Legacy pricing
      • Sponsored site plan
      • Non-profit plan
      • Billing policy
    • Subscription cancellations
    • Personal settings
    • Organization settings
    • Member management
      • Invite or remove members
      • Roles
      • Teams
      • Permissions and inheritance
    • SSO & SAML
      • SSO Members vs non-SSO
  • Resources
    • GitBook UI
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
LogoLogo

Resources

  • Showcase
  • Enterprise
  • Status

Company

  • Careers
  • Blog
  • Community

Policies

  • Subprocessors
  • Terms of Service
On this page
  • Getting started
  • Create a docs site
  • Edit your content
  • Customize your site
  • Publish your documentation

Was this helpful?

Edit on GitHub
  1. Getting Started

Quickstart

Get up and running in GitBook and publish your first docs site in minutes

Last updated 6 days ago

Was this helpful?

Getting started

You’ll need a GitBook account to start publishing documentation.

Sign up

Create a docs site

When you first sign up, you’ll have a chance to create a docs site from the docs site wizard. You can launch the wizard again to create a new site at any point by clicking the + button next to the Docs sites header in the sidebar.

The docs site wizard will take you through the flow of creating your first site. You’ll need to give your site a name, choose if you want to start from scratch with an empty site or add our sample content, and whether or not you want to publish your docs right away.

Edit your content

Check out these resources if you’d like to learn more about the editing experience in GitBook:

Customize your site

Not only can you edit the content of your site, you can also customize many settings related to the look and feel of your site when it’s published.

You can read more about customizing your docs in the resources below:

Publish your documentation

Finally, you’re ready to publish your site into the world. If you haven’t already published your site from the wizard, you can publish your site from your site’s dashboard at any time.

After publishing your site, you’ll get a link that you’re able to share with anyone!

Now that you’ve created a site, you can edit or import your content. If you have an existing repository on GitHub or GitLab with your documentation, you can easily migrate and sync your content to GitBook using . Find out more in .

After importing your content, you can edit your pages using GitBook’s built-in editor and do things like , customize the and more.

You can change things like the , add more structure through and , or update your settings.

If you’re running into problems or have any questions, we’re here to help. or and we’ll help you from there.

Want to explore publishing in more details? Check out .

add interactive blocks
layout of your pages
Join our community
send our support team a message
Git Sync
logo, colors & fonts
site sections
variants
Publish your first site in just a few minutes using the docs site wizard.
Cover

Start a change request

Collaborate on content with your team.

Cover

Install an integration

Integrate your favorite tools with your published site.

Cover

Add an OpenAPI spec

Add API methods directly into your docs.

Cover

Customize your site

Customize the look and feel of your site.

Cover

Add a custom domain

Set up a custom domain for your site.

Cover

Update your site's settings

Update settings related to your published site.

site’s visibility
our guide to migrating content using Git Sync
our complete guide to creating and publishing content in GitBook