> For the complete documentation index, see [llms.txt](https://bify.gitbook.io/rwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bify.gitbook.io/rwa-docs/reference/gitbook-theme.md).

# GitBook Theme

Use GitBook Cloud’s native design system for production docs. Do not use HonKit as the final visual reference. HonKit is only a rough Markdown preview; it cannot reproduce GitBook's hosted header, search, cards, responsive layout, or theme system.

## Space Settings

Configure these directly in GitBook:

| Setting        | Value                                                    |
| -------------- | -------------------------------------------------------- |
| Space title    | BIFY Developer Documentation                             |
| Description    | BIFY SDK, stablecoin checkout, certificates, and rewards |
| Logo           | BIFY mark                                                |
| Primary accent | BIFY blue                                                |
| Theme          | GitBook native light/dark                                |
| Search         | Enabled                                                  |
| Git Sync       | Enabled                                                  |

## Developer Portal Button

GitBook header actions are configured in GitBook Cloud rather than in a Markdown file. In the space customization settings, add a header link with:

| Setting         | Value                        |
| --------------- | ---------------------------- |
| Label           | Developer Portal             |
| URL             | `https://developers.bify.io` |
| Open in new tab | Enabled                      |
| Placement       | Header right side            |

This gives the docs an enterprise-style top-right portal action. The target domain should resolve to the BIFY Developer Portal before the header action is enabled for public readers.

## Visual Direction

Use a clean developer-documentation look:

* White/light-first layout.
* GitBook-native dark mode.
* Neutral sidebar.
* Minimal color.
* Strong code blocks.
* Short pages with clear headings.
* SDK-first examples.
* Homepage organized as product groups, capability groups, and resource links.
* Use tables and cards for navigation; avoid long introductory paragraphs.

## Content Direction

The docs should feel like enterprise SDK documentation:

* Clear setup steps.
* Copyable snippets.
* Strong API boundaries.
* Clear security guidance where required.
* Business-friendly language.
* No internal dashboard styling.
* No crypto jargon unless required.
* Keep BIFY SDK documentation separate from the regulated RWA integration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://bify.gitbook.io/rwa-docs/reference/gitbook-theme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.