The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
Product
HomepageBook a demoCommunityBlog
PricingLog inSign up

Product
HomepageBook a demoCommunityBlogPricingLog 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
  • Inserting a new content block
  • Exiting a block
  • Selecting blocks and interacting with selected blocks
  • Full-width blocks

Was this helpful?

Edit on GitHub
  1. Creating Content

Blocks

Add and edit blocks within your content.

Last updated 4 months ago

Was this helpful?

GitBook is a block-based editor, meaning you can add different kinds of blocks to your content — from standard text and images to interactive blocks. Your pages can include any combination of blocks you want, and there’s no limit to the number of blocks you can have on a page.

Inserting a new content block

You can insert a new content block below an existing block using your mouse:

  1. Hover over the block above the place you need the new content block.

  2. Click on the + icon that appears on the left to open the insert palette.

  3. Select the block you want from the drop-down menu to insert it.

Alternatively, on a new line, you can press / to launch the insert palette, which lists all the available blocks. You can scroll through the list to find the one you want, or use your keyboard to search for the block you want, navigate up and down the list, and insert it with Enter.

Exiting a block

Some content blocks capture the editing cursor to allow you to add content in the context of that block. For example, when you’re writing in a hint block, hitting Enter will add a new line within the hint block, rather than a new paragraph below.

When you are done, you can continue adding new content to the page either by inserting a new block using the + button to the left of your content, or by hitting ⌘ + Enter on a Mac or Ctrl + Enter on a PC.

Selecting blocks and interacting with selected blocks

You can select a single block by pressing the Esc key with the cursor in the block. You can also select multiple blocks by highlighting content within them and hitting Esc.

Once selected, you can:

  • Select more blocks by clicking on them while keeping the Shift ⇧ key pressed.

  • Moving up and down to select the block above or below, using the ↑ and ↓ keys

  • Copy the entire block using ⌘ + C (Mac) or Ctrl + C (Windows)

  • Cut the entire block using ⌘ + X (Mac) or Ctrl + X (Windows)

  • Delete the selected block or blocks using ⌫ or Del.

Full-width blocks

By making your blocks full width, you can create a clear visual hierarchy in your content, or simply give more space to content that needs it.

  • Code Blocks

  • Image blocks

  • Tables

  • Cards

  • API Blocks

  • Integration blocks

To make a block full width, click on the Options menu next to your block and select Full width. This feature is available for the following block types:

GitBook's built in content blocks.