GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Pricing
  • Book a demo
  • Log in
  • Documentation
  • Developers
  • Build a custom component
  • Showcase
  • Status
  • Careers
  • Blog
  • Community
  • Subprocessors
  • Terms of Service

This view

  • Original page
  • New address

GeezerVison is showing gitbook.com — Develop | Developers | GitBook Documentation

For the complete documentation index, see llms.txt. This page is also available as Markdown.

After bootstrapping your integration with the GitBook CLI, you can continue using the CLI to develop and test your app.

1

Publish your integration

Before you're able to develop your integration, you will first need to publish it. You can do this by running the following command in the root directory for your integration:

gitbook publish

By default (defined in the CLI-generated gitbook-manifest.yaml), your integration will be published privately, and owned by the organization specified in the manifest.

After publishing your integration, the CLI will give you a link to install your integration into the organization you’ve set.

You need to install your app into at least 1 space or site in order to develop it locally.

2

Start your integration’s development server

While inside the root directory of your integration, run:

gitbook dev

This will start a development server tied to your organization.

Running this command will start a development server for use by the integration only. You do not need to navigate to the port the server is running on. All integration traffic will automatically be served from your local server instead of the published version.

3

Develop your integration

If you use an AI coding assistant, add GitBook’s build-integration skill. It gives your assistant integration-specific guidance.

  1. In your integration repository’s root directory, run:

npx skills add GitBookIO/gitbook-skills

  1. Start a new agent session after the installation completes.

  2. Ask your assistant to read the build-integration skill before building your integration.

It's recommended that you disable browser caching for the most optimal experience when developing your app.

Any logs sent to the console or made through your integration's RuntimeContext will be surfaced in your browser's console.

Any UI changes made to your integration will need a browser refresh in order to be visible.

FAQ

Why don't I see any logs in my console?

Depending on where your console log is run in your integration, you may see it in your machine's console or your browser's console. Please check both to ensure your logs are working correctly.

I'm getting an error when visiting the URL listed in the console.

The URL provided in the console is used as a server for your integration. You do not need to visit this URL.

Instead, visit the GitBook space you provided in the dev command when starting your development server (i.e. app.gitbook.com/o/org_id/s/space_id).

Last updated 3 months ago

Was this helpful?

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.