> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/sandbox/readme.md).

# Sandbox

A showcase of the custom integrations built for the Harness Developer Hub, and a test bed for the ones still in progress.

Two things live in this space, side by side, on purpose.

## A showcase

The Harness Developer Hub is not just written on GitBook, it is built on it. GitBook's block model covers most of what a docs site needs, but not all of it, so our documentation engineering team builds small custom integrations to close the gaps: routing a reader to the right install command for their platform, or letting them request access to a feature without ever seeing the internal flag name.

Each integration below has its own page explaining what it does, why it exists, and how it is built, in enough depth to be useful to another documentation team facing the same problem, and safe enough for anyone to read. A customer or a fellow GitBook user can treat this as a look under the hood at how we approach documentation as a product, not just a repository of pages.

| Integration                                                                                  | What it does                                                                                | Status                                     |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------ |
| [Package Selector](/sandbox/custom-integration-showcase/ar-quickstart.md)                    | Format and platform cards that route a reader straight to the install steps for their stack | Live, in use across Artifact Registry docs |
| [HSU Calculator](/sandbox/custom-integration-showcase/hsu-calculator.md)                     | Estimates monthly Harness Service Unit consumption by module and tier                       | Live, on the pricing page                  |
| [Feature Flag Access](/sandbox/custom-integration-showcase/feature-flag-access.md)           | Lets a reader request access to a gated feature without the page ever naming the flag       | Live                                       |
| [Feedback and Ticket Triage](/sandbox/custom-integration-showcase/feedback-ticket-triage.md) | Collects reader feedback on a page and routes it into the support triage queue              | Live                                       |
| [Release Notes Summary](/sandbox/custom-integration-showcase/release-notes-summary.md)       | Regenerates an AI-summarised rollup of the last 30 days of release notes                    | Live, headless, manually triggered for now |

A sixth integration, `harness-relyance-consent`, injects the cookie-consent agent site-wide. It has no reader-facing surface, so it does not get a page of its own here — it is infrastructure, not a tool a reader interacts with.

## A test bed

This space is also where we prove things work before they reach production documentation: whether a card's link resolves correctly, whether an icon falls back gracefully when a logo is missing, whether a staged build behaves the same as the version readers currently see. Some pages here are exactly that, raw, mid-test, and not meant to be polished. They stay that way on purpose; tidying them would defeat the point of having somewhere safe to break things.

A page below that reads as unfinished probably is, and that is fine, it is doing its job.

## Why this is written down

Every integration here solves a problem that is not unique to Harness. Any GitBook customer publishing multi-platform docs, gating a feature behind access, or wanting reader feedback wired into their support queue is likely to hit the same wall. Documenting the reasoning honestly, as we build, is worth doing on its own merits. It also means that if any of this turns out to be generic enough for GitBook to point other customers at, the case has already been made in writing, not reconstructed after the fact.