# GitBook

After trying a couple hosted and self-hosted blogging solutions, I've settled on GitBook.com. [GitBook itself is opensource](https://github.com/GitbookIO/gitbook) software and [gitbook.com](https://gitbook.com/) provides a free or paid GitBook hosting service.

{% embed url="<https://gitbook.com/#PersonalNotes>" %}

The thing that's best about GitBook is the way you can organize a structured outline of the site's contents. The other killer feature is it's ability to do code-related formatting, including:

* an editor almost as nice as Medium (and more featured)
* contents/outline with nesting and collapsing
* code blocks with language-specific highlighting
* tabs (e.g. to provide examples in different languages, platforms, etc.)

{% tabs %}
{% tab title="Case #1" %}

```
This is an example in case one.
```

{% endtab %}

{% tab title="Case #2" %}

```
This is an example for another case.
```

{% endtab %}
{% endtabs %}

* API documentation form

## /v1/cakes/:id

<mark style="color:blue;">`GET`</mark> `https://api.acme.com/v1/cakes/:id`

Retrieves the details for a single cake by its id.

#### Path Parameters

| Name              | Type    | Description                         |
| ----------------- | ------- | ----------------------------------- |
| include\_customer | boolean | Include customer details when true. |

{% tabs %}
{% tab title="200 " %}

```
```

{% endtab %}
{% endtabs %}

* variants (e.g. different spoken language versions of a page)
* integrations: Slack, GitHub, Google Analytics, Intercom
* versioning of edits (as in why it's called 'git'book)
* the free gitbook.com service also allows using a custom domain name


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.keithkim.org/other-software/gitbook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.