Skip to main content

GitBook docs sites

GitBook Docs Testimonials and Their Limits

GitBook’s customization docs are direct about it: you cannot insert custom CSS, HTML or JavaScript into a GitBook site, and its embed page adds that raw iframe tags are refused under its content security policy. So a script based testimonial widget, StoryProof’s included, will not run inside GitBook. Two native pieces still work well together: a quote block holding one approved testimonial, and a link button to the full set.

  • Why no widget can be embedded in GitBook
  • A quote block with one approved testimonial
  • A button to your hosted Wall of Love

No code to paste

What to put in GitBook instead

GitBook takes no embed code, so the widget id field above has no effect here. Copy each card into the GitBook block it names and replace the bracketed parts with your approved text and your StoryProof links.

Shown in StoryProof when you copy a widget’s embed code.

Part 1 · A quote block

GitBook editor › empty line › > then Space

Quote block (type > then a space on an empty line)

[the approved testimonial, copied word for word from StoryProof]

[customer name], [role and company, only if they agreed]

Part 2 · A link button in the editor

GitBook editor › / › Button › link action

Button (type / and choose Button, then set its action to a link)

Label:   See what teams say about us
Link:    [your StoryProof Wall of Love link]
Style:   primary

Part 3 · The buttons in Git Sync

docs/README.md (or any synced page)

<!-- Same button in a Git Synced Markdown file -->
<a href="[your Wall of Love link]" class="button primary">See what teams say about us</a>

<a href="[your StoryProof collection link]" class="button secondary">Share your experience</a>

Publish the change, open the live docs site, and click each button. GitBook notes that external links open in the same tab, so check the Wall of Love loads and the back button returns readers to the docs.

Plain text templates. Nothing you type here is stored.

The problem, solved

GitBook and testimonials: what is possible

StoryProof normally installs as a div and a script. GitBook allows neither, so each fix here uses GitBook’s own blocks.

  • Problem 1

    Nowhere to paste a widget snippet

    GitBook says custom CSS, HTML and JS cannot be inserted into a site, and the StoryProof embed is a div plus a script.

  • Problem 2

    Tried an iframe and it vanished

    GitBook’s embed page says it cannot embed external iframe tags because of its content security policy, and only embeds URLs that Iframely supports.

  • Problem 3

    A docs page with no human voice

    Reference pages are dry by design, so a single real quote on the landing page does a lot of work.

  • Problem 4

    The strongest praise came on a call

    GitBook embeds videos from supported providers, but a customer’s recorded clip or voice note has no natural home in the docs.

  • Problem 5

    Developers praise you in Slack, not on record

    Kind words in a community channel cannot be quoted without consent, so the docs stay empty.

In StoryProof

Add testimonials to a GitBook site

Step 1 of 5

Pick one short quote

Choose an approved testimonial that names a concrete result. Long quotes swamp a docs landing page.

If your docs need a live widget

OptionReader seesTrade off
Quote block plus Wall of Love buttonOne quote in the docs, the full set a click awayManual edit to change the featured quote
Widget on your marketing site, linked from GitBookAn embedded widget on a page you controlReaders leave the docs for it
Docs on a platform that accepts scriptsWidgets inside documentation pagesA migration, worth it only for other reasons too

Before you start

Limits on GitBook

  • No embedded widget

    GitBook’s customization docs say custom CSS, HTML and JS cannot be inserted. No StoryProof widget can render inside a GitBook page.

  • Iframely only

    GitBook embeds URLs through Iframely and refuses iframe tags. StoryProof does not claim its Wall of Love appears as a GitBook embed.

  • Quotes are static

    Text in a quote block stays as typed. It does not change when you approve new testimonials in StoryProof.

  • Same tab links

    GitBook opens external links in the same tab, so readers leave the docs when they click. Label the button so that is expected.

  • GitBook docs as of 2026-11-14

    The custom code rule, embed behaviour, quote block and button details follow gitbook.com/docs as read on 2026-11-14. These steps have not been tried on a live GitBook site.

FAQ

Questions people ask

Short answers to what usually comes up next.

Is there a GitBook integration that injects scripts?

GitBook’s customization docs say custom code cannot be inserted into a site. We have not found an official route for third party scripts and do not suggest one.

Could I embed the Wall of Love as an Embed block?

GitBook embeds only URLs that Iframely supports. StoryProof has not confirmed its pages render that way, so a button is the dependable option.

Does a higher GitBook plan unlock custom HTML?

GitBook lists advanced customization on its Essential and Ultimate plans, such as fonts, logo and themes. The same page says custom CSS, HTML and JS still cannot be inserted.

Does the Wall of Love cost extra?

No. Every StoryProof plan includes a Wall of Love with its own link.

Still have a question? Ask the StoryProof team or book a demo.

Give your GitBook readers somewhere to see proof

Collect and approve testimonials, then link a GitBook button to your Wall of Love.

Sources

  1. Site customization, GitBook Documentation. Checked 2026-11-14.
  2. Embedded URLs, GitBook Documentation. Checked 2026-11-14.
  3. Quotes, GitBook Documentation. Checked 2026-11-14.
  4. Inline content (buttons and links), GitBook Documentation. Checked 2026-11-14.

Last updated 2026-11-14.